Pavel Císař

FDB does nothing with POSIX signal handlers, BUT it uses ctypes to work with Firebird client library that certainly does something to finalize so/ddl gracefuly. The library initialization is deferred...

This is an example of unhelpful issue report. What it means: doesn't work? Why it's problem of FDB and not SQLAlchemy? Without relevant information added, I'll close this after 24...

Well, the core of this problem is that there could be error messages that are encoded in OS encoding at the server (path, filenames etc.). In your case it happens...

The correct method (patch) should use the None/"NONE" connection charset in FDB with its redefinition in ibase.py/charset_map from 'getpreferredencoding()' to 'latin-1', instead hijacking OCTETS.

Well, I was not aware of 'latin-1' meaning at the time I was creating FDB, so using getpreferredencoding() was the best from bad solutions I was able to came with....

@mrotteveel I will change the mapping for 'NONE' charset, not for None value (when connection charset is not specified at all). This should not break any application that does not...

Well, timezone support is quite tricky. You need to use 'get_timezone()' function (provided by firebird-driver) to create tzinfo objects. This is preferred method to obtain timezone information for construction of...

Well, I'm not happy with current solution either, but converting tzinfo behind the scene to required format is not that simple as it seems due to differences in various implementations...

1. BlobReaders are not closed when cursor iteration is finished, but when cursor is **closed**. That's because the underlying Firebird structures are AFAIK related. So, until you do not close...

Well, while I'm not against the idea, I'll insist that it must be an optional alternative, not the default one. * Using the environment variable for client library (engine) is...