Re: [sqlite] May I ask why the source distribution mechanism was changed starting with 3.3.14?

amalgamation distribution, as we have now, for those users who treat the database as a black-box and never wish to know any more than that it compiled and works. -- Justin Fletcher, Senior Software Engineer Picsel Technologies Ltd Tel: +44 141 8855588 Titanium Hou

[sqlite] changes() function discrepancy

gt; insert into t0 values (1); sqlite> insert into t0 values (1); sqlite> insert into t0 values (2); sqlite> sqlite> update t0 set x=9 where x=1; select changes(), total_changes(); 10|13 8< Is there a reason for this seeming discrepancy in the exec

Re: [sqlite] Problem with understanding the test suite

[EMAIL PROTECTED] wrote: Justin Fletcher <[EMAIL PROTECTED]> wrote: do_test select1-11.2.2 { execsql2 { SELECT * FROM t3, t4; } } {a 3 b 4 a 3 b 4} Can someone explain how the test can be correct ? This comes about because of duplicate column names. The execsql2 procedure

[sqlite] Problem with understanding the test suite

over every column name and prepends the column name to those values in the result string. As the column names match in the results, I think that gives the strange results. -- Justin Fletcher, Senior Software Engineer Picsel Technologies Ltd Tel: +44 141 8855588 Titaniu