RE: SQL support

"Julien Chavanton" <[email protected]>
Newsgroups gmane.comp.gnu.bayonne.devel
Message-ID <[email protected]>
I guess it would be more clean and simple for bayonne to let the scripting engine provide the database connection !
 
 
-----Original Message----- 

	From: bayonne-devel-bounces+j.chavanton=oneworldinteractive.com@gnu.org on behalf of David Sugar 
	Sent: Wed 4/6/2005 09:49 AM 
	To: Dmitry Agafonov 
	Cc: [email protected] 
	Subject: Re: [Bayonne-devel] SQL support
	
	

	-----BEGIN PGP SIGNED MESSAGE-----
	Hash: SHA1
	
	In ccscript3 what I did was create a connection to an associated
	database as each script is compiled.  The
	use statement was extended to pass the name of the database for the
	script that expects to connect.  Hence,
	each script can have it's own private database reference, and different
	scripts can have different database
	connections associated with them.  When old scripts are purged, old
	connections are torn down.  The only
	database operations that occur during execution are now the actual
	queries, in an async thread.
	
	Dmitry Agafonov wrote:
	> Hello!
	>
	> I just get myself to the idea of SQL usage in bayonne (ccscript).
	>
	> Imagine a pool of SQL connections, ready to answer any query.
	> One connection per SQL gateway thread (like TGI).
	>
	> Just ping() connection on script startup and cleanup result sets on
	> script ending.
	>
	> Simple schema, isn't it?
	>
	-----BEGIN PGP SIGNATURE-----
	Version: GnuPG v1.4.1 (GNU/Linux)
	Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
	
	iD8DBQFCU+jSJlWtSTiTVsYRAl/eAJkBxsEaOXY2kr9xDzdviw0hhc7QFACfQMgW
	BNSLEFiwDAkbOlwvytLQCS8=
	=bVYw
	-----END PGP SIGNATURE-----

_______________________________________________
Bayonne-devel mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/bayonne-devel
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.