On Mon, Aug 22, 2011 at 12:54 PM, Boris Kolpackov <bo...@codesynthesis.com>wrote:
> Hi Dan, > > Dan Kennedy <danielk1...@gmail.com> writes: > > > It is. Now fixed in the trunk. > > Thanks for the fix. I patched 3.7.7.1 with it and indeed this now > works: > > BEGIN TRANSACTION; > DROP TABLE employer; > DROP TABLE employee; > COMMIT; > > > However, this transaction: > > BEGIN TRANSACTION; > DELETE FROM employer; > DROP TABLE employer; > > DELETE FROM employee; > Dan has convinced me that the SQLite code is correct as documented. The documentation states: "Foreign key DML errors are may be reported if: (1) The parent table does not exist..." And for the DELETE statement above, the parent table does not exist. So it is appropriate to rais an error. > DROP TABLE employee; > COMMIT; > > Still issues "Error: no such table: main.employer" after the second > DELETE. I don't think this should happen either. What do you think? > > Boris > -- > Boris Kolpackov, Code Synthesis > http://codesynthesis.com/~boris/blog > Compiler-based <http://codesynthesis.com/%7Eboris/blog%0ACompiler-based>ORM > system for C++ > http://codesynthesis.com/products/odb > Open-source <http://codesynthesis.com/products/odb%0AOpen-source> XML data > binding for C++ http://codesynthesis.com/products/xsd > XML data binding for embedded systems > http://codesynthesis.com/products/xsde > > _______________________________________________ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > -- D. Richard Hipp d...@sqlite.org _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
