Il giorno mar, 17/04/2007 alle 13.53 -0400, Michael Bayer ha scritto: > However i might suggest that this whole thread, "controlling return > types", perhaps be expanded to include "controlling *input* types and > return types", since to me (as well as to SQLAlchemy) being able to > send an arbitrarily-typed python object into a bind parameter is just > the mirror image of receiving a result column as an arbitrarily-typed > python object. I think it would be unfortunate if only one half of > the coin were addressed.
Sure. ;) The Python->SQL part is perfect for adaptation and, for example, psycopg has a micro-protocols implementation to help with the adaptation of any Python object into a valid ISQLQuote one. Why two different systems? Because transating Python to SQL and SQL to Python are two very different operations, IMHO. federico -- Federico Di Gregorio http://people.initd.org/fog Debian GNU/Linux Developer [EMAIL PROTECTED] INIT.D Developer [EMAIL PROTECTED] La felicità è una tazza di cioccolata calda. Sempre. -- Io
signature.asc
Description: Questa è una parte del messaggio firmata digitalmente
_______________________________________________ DB-SIG maillist - DB-SIG@python.org http://mail.python.org/mailman/listinfo/db-sig
