All, I have done exactly like BareFeetWare suggested. The referential integrity "feature" is a no brainer for "serious" systems, where you do care about your data consistency. SQL doesn't have clauses where you declare where do you want Erroneous records to go. This is usually mandated to tools like sqlite3.
Or special purpose C++ hacks. Thanks, guys. Shalom On Thu, Mar 24, 2011 at 1:48 AM, BareFeetWare <list....@barefeetware.com>wrote: > On 24/03/2011, at 2:50 AM, Shalom Elkin wrote: > > > I appreciate the input. Some of the advice comes obviously from very good > > and talented people who find a challenge at doing things WITHOUT > reverting > > to code writing. > > Doing as much (or most often, all) of the logic in SQL (instead of > application code) removes a level of complexity, but is also generally > faster and internally consistent. > > > I did a small program. Current show -stopper : > > > > what is the API equivalent of > > > > PRAGMA foreign_keys = ON; > > You can just send each of the SQL commands, including the pragma statement, > in sqlite_exec (or you can get fancy with sqlite_prepare etc where it makes > sense). > > Tom > BareFeetWare > > -- > iPhone/iPad/iPod and Mac software development, specialising in databases > develo...@barefeetware.com > -- > Comparison of SQLite GUI tools: > http://www.barefeetware.com/sqlite/compare/?ml > > _______________________________________________ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > -- Shalom Elkin +972-544-704994 _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
