"Tran Van Hoc" <tv...@vn.isb.co.jp> schrieb im
Newsbeitrag news:43a0ef604a674b3fb80d1447b41f8...@isbvietnam.com...

[Stored procedures in SQLite]

IMO stored procedure-support only makes
sense in "Server-Instances" which run
on their own (and communicate over
different IPC-mechanisms, mainly sockets,
with their "Clients").

But SQLite is not such "a Server" - it's a
*library* and as such it offers its API
directly to the hosting Process.

If you choose, to implement a small Server-
Host (talking over sockets with "DB-Clients"),
then you can write your stored Procedures
in any language you want - either "in a static way"
which would be implemented in the language you
choose to write the Server-Host-Application with
(in case this language has no scripting-capabilities).
But if you choose TCL/Perl/Ruby/Lua/Python/etc.
as your scripting-language, you're free to do
so too - then your scripts could even be stored
within "normal DB-Tables" in your serverside
SQLite-DB and executed dynamically on request.
No need to learn "special Stored-Procedure-syntax" -
just talk in your scripting-language of choice with
SQLite - using everything the SQLite-API has
to offer (depending a bit on the wrapper-bindings
of the scripting-language in question).

If you do not want to implement such a hosting
Server-instance yourself, you could always choose
a WebServer-environment as "the Server-layer".
These Hosts can "talk http" - and on the serverside
you have support for all sorts of scripting-languages,
as the ones just listed above.

Olaf



_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Reply via email to