[DB-SIG] Type code mappings: expanding the type objects
Federico Di Gregorio
fog at initd.org
Thu Jan 8 14:38:23 EST 2004
Il gio, 2004-01-08 alle 14:00, M.-A. Lemburg ha scritto:
> > products to be more standards compliant.
> In that case, perhaps BOOLEAN should be at top-level ?!
i vote for making it top-level.
> mxODBC let's you set a flag to one of these values:
> * always return 8-bit strings (in the database encoding)
> * allow the database to decide whether or not to send Unicode
> * always return Unicode (with 8-bit strings decoded according
> to an encoding you set on the connection; unfortunately,
> there's no easy way to read the database default encoding)
sounds good and i would like to see something like that standarized in
the DBAPI. currently psycopg uses the encoding parameter of the
connection to set the "client_encoding" variable but stops there.
Federico Di Gregorio http://people.initd.org/fog
Debian GNU/Linux Developer fog at debian.org
INIT.D Developer fog at initd.org
God is real. Unless declared integer. -- Anonymous FORTRAN programmer
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: Questa parte del messaggio =?ISO-8859-1?Q?=E8?= firmata
Url : http://mail.python.org/pipermail/db-sig/attachments/20040108/df968964/attachment.bin
More information about the DB-SIG