As of version 3.3 of kinterbasdb and with Firebird 2.1+ blob fields
can be treated the same as other "string" type fields when one is using
type_conv=300.
New users will be on FB 2.1 (or soon 2.5) and it would make things
easier/more consistent when dealing with blobs containing text - i.e.
they won't have to search why sa.String will not return the same thing
for a varchar or a blob column.
Doc from -
http://www.firebirdsql.org/devel/python/docs/3.3.0/beyond-python-db-api.html#parameter-conversion
Quote:
300 (the ideal for Firebird 2.1 and later)
New in v3.3
This translator configuration is identical to 200, but textual blobs are
handled in the same way as other textual types, so unicode
encoding/decoding is performed automagically. When converting in the
input direction, this doesn’t work with any Firebird version prior to
2.1, because the Firebird API doesn’t make the blob’s character set ID
available.
Werner
--
You received this message because you are subscribed to the Google Groups
"sqlalchemy" group.
To post to this group, send email to sqlalch...@googlegroups.com.
To unsubscribe from this group, send email to
sqlalchemy+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/sqlalchemy?hl=en.
