I am not sure how this would work. in order for a trigger to "See" another database, somebody (obviously not the trigger) must ATTACH the database first. is there an automatic ATTACH capability that I am not aware of ? if not, specifying triggers than span databases is looking for trouble IMHO. as for allowing it, well, guns are allowed also, so you can shoot yourself in the foot, if you really want to.
> -----Original Message----- > From: Brad [mailto:[EMAIL PROTECTED] > Sent: Tuesday, February 28, 2006 3:28 PM > To: sqlite-users@sqlite.org > Subject: Re: [sqlite] Triggers and TEMP tables: ticket #1689 > > > Should I remove the tests from SQLite that prevent triggers in one > > database from referring to tables in a different database? > > Well, I have a couple of triggers in my SQL Server database > that refer to tables in another database, though they are on > the same server. > Obviously, I can see some utility in that. I will admit, > however, that if I had to implement the system that uses that > scheme in SQLite, then I'd probably have the tables in the > same database file, rather than different ones. > > > >
