I wonder if anyone has ever written an embedded #RDBMS in which there is no run-time #SQL interpreter, and all SQL queries are translated into machine code at compile time.
Kinda like #Rust sqlx, except queries are fully compiled at compile time, not just checked for correct syntax and types.
I'm guessing this would be extremely specific to one #programming language, and outright impossible in most programming languages.
Firebird Project is happy to announce general availability of Firebird 5.0 — the latest major release of the Firebird relational database for Windows, Linux, MacOS and Android platforms.
This release introduces improvements in areas of performance, multithreaded processing (including backup, restore, sweep), SQL queries profiling, with better scalability and numerous enhancements in SQL language.
Firebird Project announces the second Release Candidate of Firebird 5.0, the next major version of the Firebird relational database, which is now available for testing on all supported platforms (Windows, Linux, MacOS, Android).
I want to write a review document about a relational database. Are there any tool / language / format to help with not only describing tables and relationships, but also commenting and adding suggestions?
So far the only things I found only renders something about the current state of the database (like a UML diagram), but I can't add manual or programmatic comments.
Within a (few) days I'm gonna do a full database clean to remove all deleted posts, banned accounts etc. Basically all garbage that's been collected overtime
Unfort for that the instance will be offline since I currently cannot affort to upgrade the server for this.. :flan_worried:
It'll take a few hours max and I will be giving a warning a few times before!
So not now but within a few days, first I'm gonna wait until the media clean is finished
@Tedgarrison3@stux@gizmo Normally, a database engine should be able to lock fairly small chunks of storage to delete individual rows in a table. My guess would be that since such a cleanup presumably touches a rather large fraction of the rows in the table, the #database#RDBMS engine at some point, rather than locking individual chunks, just throws its hands in the air with a "I'm through with this piecemeal stuff, I'll just lock the whole thing instead so I can get this over with".