Kenneth,
On Tue, May 19, 2009 at 5:56 PM, Kenneth Gonsalves lawgon@au-kbc.org wrote:
On Tuesday 19 May 2009 17:38:38 Rajen M. Parekh wrote:
Or you want the programmer to write zillions of lines of code to enforce foreign key constraints?
Foreign key constraints can be easily achieved with sqlite using triggers. I have personally implemented 3 desktop projects using sqlite + Qt and in all cases I have used triggers to enforce foreign key constraints. And you won't need zillions of lines of code. Only a few triggers for each constraint. And even that can be automated. In fact, there already is a web script which automatically generates triggers to implement foreign key constraints by parsing the original "CREATE TABLE" statement. Sqlite allows you to mention foreign key constraints in your "create table" statement even though it does not currently implement it.
there is one fundamental principle one follows in criticising/commenting on open source applications:
No one, so far, has questioned/criticized the developers' right to use/choose whichever tools he/she/they can use.
the developer gets to choose his platform and his tools. It is counter productive to give long arguments about his choice. He is not going to change especially after putting in a hell of a lot of hard work. Criticise the application - tear it to pieces, but respect his choice of the colour he uses to paint his bike shed.
The whole debate started about the appropriateness of selecting certain DB in desktop class app based on your "security hole" related post and subsequently removing possible/perceived deployment difficulty in a desktop application.
Even original developer(s) have taken the feedback in right spirit and explained his/their position in the selection process of the back-end DB.
This debate could be useful to FOSS developers in future to select right tools for solving a problem.
-- regards Kenneth Gonsalves
Let us keep the debate healthy without any personal acrimony. With regards,