Joe Mistachkin wrote:
[regarding foreign key enforcement when user does not directly open
connections]
> If anybody knows how to solve this more easily than suggested above, I
> would appreciate your input.
>
There are two ways to solve this:
1. The 1.0.83.0 release of System.Data.SQLite, due out before the end of
the year, adds a static Changed event to the SQLiteConnection class.
This allows external components to be notified when a connection is
opened, closed, etc.
2. Alternatively, you can make sure the "Foreign Keys" property is set to
true in the connection string.
Prior to the [pending] 1.0.83.0 release, only option #2 is available.
Thanks, Joe, for your quick and apt response.
Please do not take this as a gripe, but earlier, when I suspected that
there might be a connection string solution, I did a search to see what
the option name might be. I saw nothing at www.connectionstrings.com,
http://system.data.sqlite.org in the doc, FAQ or feature sections, and
nothing at http://www.sqlite.org/c3ref/open.html (where I had hoped that
'URI Filenames' might permit such an option). If not for your providing
it, I would be at a loss even if I knew there was such an option.
That event is a nice feature, and I look forward to seeing 1.0.83.0 . I
really appreciate the fine work that has been done on System.Data.SQLite.
Best regards,
--
Larry Brasfield
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
