On 8 May 2014, at 9:00am, Constantine Yannakopoulos <alfasud...@gmail.com> wrote:
> When the fk violation occurs inside a large transaction, > e.g. during a bulk data import it is essential that the user is given any > possible help to be able to locate the data that violates ref integrity and > fix it. That's your job. You're the programmer. SQLite does not talk to users and its result values should never be shown to a user. > Without this, prechecking the fks is the only option. No need. You execute the command as expected. Only if it returns SQLITE_CONSTRAINT does your software need to start doing complicated things to figure out what caused the problem. > And I would > argue in favor of a compiler switch to enable instead of a pragma. I would argue that consideration of this should go into the design of SQLite4. I don't think it's worth doing it for SQLite3. Simon. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
