On Fri, Dec 14, 2007 at 04:28:07PM -0600, John Stanton wrote: > Samuel R. Neff wrote: > >I'm not sure I see added value in incorporating procedural SQL in an > >embedded database like SQLite or DeviceSQL. Isn't the easily extensible > >mechanism that SQLite has for creating custom functions in the host > >language [...] > > The difference is if you are pursuing the DeviceSQL approach and > compiling a library of data manipulation functions. The partitioning is > cleaner if procedural logic can be included in those functions. > > In our Sqlite applications we have implemented Javascript as a DB > procedural language by adding an Sqlite class. You can store it in the > DB and execute it. You can also run Javascript scripts which manipulate > an Sqlite DB. When using Sqlite we see the value of a DB procedural > language in the dynamic storage of rules rather than having rules > chiselled in stone in the application code. Multiple rules in > Javascript can be integrated and compiled into one executable procedure, > giving great flexibility in building systems in the "expert" style. > > We chose Javascript for practical reasons. It is universally used in > WWW pages so the developers do not have any new language to learn.
SQL is very expressive, and procedural SQL is too. Much more so that C. So if you're writing an embedded app in C then procedural SQL might come in handy (also, the VDBE code will probably be smaller than the corresponding object code). ----------------------------------------------------------------------------- To unsubscribe, send email to [EMAIL PROTECTED] -----------------------------------------------------------------------------
