[sqlite] Unexpected SELECT results

, this has its drawbacks, as shown in the submitted case where I landed unintentionally into uncharted territory. The alternatives pointed out by your query examples will be very useful in bringing my schema corpus back on track. Louis Jean-Richard

[sqlite] Unexpected SELECT results

ONG sqlite> For me the view 'oldest_among_recent_stamp' is for all purposes a table, albeit a volatile one that last only until the query process is completed and its content as shown by SELECT * is correct. The query "select project from oldest_among_recent_stamp;" should return 'lj' and not 'ws'. It is quite odd that the content of a table should depend on which of its columns are selected or not further down. There must certainly be a bug, either in my brain or in the sqlite engine. ;) Any clarifications are thankfully welcome. Louis Jean-Richard ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] Trigger with WHEN clause error

Thank you very much for the help, it has solved my issue and now I know what for 'old' and 'new' stand in triggers .... Sincerely Louis Jean-Richard s my problem On 25. 10. 13 20:19, Richard Hipp wrote: On Fri, Oct 25, 2013 at 2:10 PM, Louis Jean-Richard < l_jean_ri

[sqlite] Trigger with WHEN clause error

column: last_update 2013-10-19|2013-10-11 sqlite> I have based it on the Trigger doc. found at: http://sqlite.org/lang_createtrigger.html My question: is this a bug or am I completely misunderstanding the purpose of the WHEN clause in the trigger syntax? Thank you for the attention. Lou