On Sun, 19 Jul 2009, Roger Binns wrote: > Bringing things full circle, that is exactly what the genfkey > functionality does. It parses the foreign key constraints and generates a > set of triggers to ensure they are enforced. It used to be a separate > program until it was moved into the shell and exposed as a command (in > February of this year). You can rerun the command as often as you want > - it will delete the existing triggers (their name has a predictable > prefix) and generate a new set. > > Unfortunately because it is part of the shell, that is the only way to > access it. For many it is sufficient as you can load your database with > the shell, run genfkey and then quit.
Roger, I had not realized this. The way you explain it, it would make sense to be able to access the genfkey functionality programatically, testing to see if it has already been run on the database. When I can make the time I'll have to look at this capability. Thanks, RIch -- Richard B. Shepard, Ph.D. | Integrity Credibility Applied Ecosystem Services, Inc. | Innovation <http://www.appl-ecosys.com> Voice: 503-667-4517 Fax: 503-667-8863 _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
