-----Original Message----- From: John Stanton [mailto:[EMAIL PROTECTED] Sent: Friday, December 14, 2007 3:55 PM To: sqlite-users@sqlite.org Subject: Re: [sqlite] DeviceSQL
... is it not directly comparable to DeviceSQL unless the external compiler handles not only SQL but also PL/SQL. The addition of the command language allows for creating a library of data manipulation functions rather than just embedded SQL. ... John, 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 (C, C#, ActionScript, whatever) a fully valid replacement for whatever procedure language could be provided through VDBE? Also doesn't the fact that SQLite (and any embedded db) runs in-process negate the importance of SQL procedural code? In my experience, stored procedures are usually used to offload more work to the DB server and thus perform DB intensive code closer to where the DB data is, which is not necessary when the DB is already in-process? After moving from MSSQL to SQLite for our application, which previously used stored procedures, we've never missed the functionality of TSQL and found creating UDFs in C# for SQLite much easier and more powerful that using TSQL UDFs, especially 'cause they run in-process and thus have full access to the host application's objects and code. Sam ------------------------------------------- We're Hiring! Seeking a passionate developer to join our team building Flex based products. Position is in the Washington D.C. metro area. If interested contact [EMAIL PROTECTED] ----------------------------------------------------------------------------- To unsubscribe, send email to [EMAIL PROTECTED] -----------------------------------------------------------------------------
