I looked at some code. The CLI has comments about a feature where you can access a nonexistent database file without creating it but I doubt that actually works, as it seems to create the database file before processing commands. And I wonder if multi database actually works because it handles prefixes like "SELECT * FROM db.foo" by splitting it into db selector "db" and unprefixed statement "SELECT * FROM foo" which obviously wouldn't work if the statement accessed more than one database.
I also found comments about replacing identifiers in SQL (used to implement ALTER statements probably?) which say that it won't work right if two things in the database have the same name and it'll get caught by a sanity check later.
Comments
I looked at some code. The CLI has comments about a feature where you can access a nonexistent database file without creating it but I doubt that actually works, as it seems to create the database file before processing commands. And I wonder if multi database actually works because it handles prefixes like "SELECT * FROM db.foo" by splitting it into db selector "db" and unprefixed statement "SELECT * FROM foo" which obviously wouldn't work if the statement accessed more than one database.
I also found comments about replacing identifiers in SQL (used to implement ALTER statements probably?) which say that it won't work right if two things in the database have the same name and it'll get caught by a sanity check later.
That's just the parts I looked at.