On Tue, Oct 28, 2014 at 8:24 AM, Hick Gunter <h...@scigames.at> wrote:
> Indices, foreign keys, ... all work only within a single DB file, so > allowing a qualifier would suggest functionality that is not present and > probably quite hard to provide. > We've got no intention of trying to rely on such a thing, it just struck me as odd (while trying to port a schema file) that some places didn't allow it. We don't have any table name collisions across the DBs, so we're really never expecting any ambiguity problems. (This whole effort to support/standardize on fully qualified DB names in our SQL is largely just me being overly pedantic.) How would one keep an index residing in one DB file consistent with a table > in a different file if only one of the files is attached? > No idea - those details (if any!) are left to sqlite ;). Eg. > > CREATE INDEX db.index_name ON [=>db.]table_name ... > > CREATE TABLE db.table_name (...) FOREIGN KEY (...) REFERENCES > [=>db.]referenced_table > > CREATE TRIGGER db.trigger_name ... ON [=>db.]table_name ... > > CREATE VIEW db.view_name AS SELECT ... FROM [=>db.]table_name ... > Thanks for the details :). -- ----- stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal "Freedom is sloppy. But since tyranny's the only guaranteed byproduct of those who insist on a perfect world, freedom will have to do." -- Bigby Wolf _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
