Re: [sqlite] ambiguous temporary trigger metadata

2013-10-20 Thread Simon Slavin
On 20 Oct 2013, at 6:11pm, Bogdan Ureche wrote: > Sorry, I misread your reply In your defence, my writing was ambiguous. > You are correct. In your scenario, after step > 3 the trigger references a table that no longer exists. As an alternative one could ALTER TABLE

Re: [sqlite] ambiguous temporary trigger metadata

2013-10-20 Thread Bogdan Ureche
Sorry, I misread your reply. You are correct. In your scenario, after step 3 the trigger references a table that no longer exists. A similar issue exists with foreign keys. Bogdan On Sun, Oct 20, 2013 at 10:11 AM, Simon Slavin wrote: > > On 20 Oct 2013, at 4:09pm,

Re: [sqlite] ambiguous temporary trigger metadata

2013-10-20 Thread Simon Slavin
On 20 Oct 2013, at 4:09pm, Bogdan Ureche wrote: > I tried without success to reproduce this scenario. > > create table t1(c); > create temporary trigger tr1 after insert on t1 begin select raise(abort, > 'error'); end; > insert into t1(c) values(1); -- error is raised here

Re: [sqlite] ambiguous temporary trigger metadata

2013-10-20 Thread Bogdan Ureche
> The problem is not that table names aren't qualified. The problem is that > information for setting up the schema (structural components) of a SQLite > database are stored in the database as the SQL commands rather than a > complicated internal format. This makes it permissable to do this: > >

Re: [sqlite] ambiguous temporary trigger metadata

2013-10-20 Thread Simon Slavin
On 20 Oct 2013, at 3:34am, Bogdan Ureche wrote: > Thank you for replying and for updating the documentation. I didn't realize > that the trigger may be unexpectedly reattached to a different table when > the schema changes. If this is the case then perhaps the creation of

Re: [sqlite] ambiguous temporary trigger metadata

2013-10-19 Thread Bogdan Ureche
Hi Richard, Thank you for replying and for updating the documentation. I didn't realize that the trigger may be unexpectedly reattached to a different table when the schema changes. If this is the case then perhaps the creation of temp triggers on non-temp tables using non-qualified table names

Re: [sqlite] ambiguous temporary trigger metadata

2013-10-19 Thread Richard Hipp
On Sat, Oct 19, 2013 at 9:17 PM, Bogdan Ureche wrote: > What would be a good way to extract metadata information about temporary > triggers? If there are multiple tables with the same name in main and temp > databases (or even attached databases), I could not find a way to

[sqlite] ambiguous temporary trigger metadata

2013-10-19 Thread Bogdan Ureche
What would be a good way to extract metadata information about temporary triggers? If there are multiple tables with the same name in main and temp databases (or even attached databases), I could not find a way to determine on which table a temporary trigger was created by examining the available