Hi Pavel, I think I guess that I understand what your point is.
On 2010-08-18 21:18, Pavel Ivanov wrote: > This is exactly the reason why it's not logical action: SQLite will > check constraint only in those places where it knows that something is > changed and constraint can be violated. And it shouldn't re-check it > in million other places where nothing seems to be changed... > To catch up with reason of "why" consider these scenarios: > 1) You connected to main, attached texts, made foreign constraint and > inserted some records. Then you created other connection to texts > directly and deleted all referenced records. How should SQLite know > that they cannot be deleted? > 2) You made another connection to main and connected another database > as "texts". How foreign keys should be enforced in this situation? I see, so the guarantees made by constraints are somehow just don't fit with the feature of using more than one database at a time. Thanks for pointing it out, // Oliver _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
