Hello internals@, I've been looking into improving PDO_ODBC; specifically, bringing it up to parity with other drivers, as well as dealing with its quirks. The company I work for supports PHP on IBM i, and while we maintain the native database drivers for the platform, we (and IBM) have been recommending new applications migrate to ODBC.
However, the procedural ODBC driver does have some limitations like no in/out parameters (which is a very common thing with stored procedures here, unfortunately). PDO_ODBC does support this, but we've noticed some issues: * Persistent connections aren't checked, even though the procedural ODBC driver does. This has bitten some of our clients, so we have a patch for them that does impement this; this is PR GH-6805. * Many of the connection attributes don't seem to be implemented; some of these seem trivial to implement, others less so. * In/out parameters require users to remember to specify size and add one for the null terminator. I'm not familar with other ODBC drivers to call this a driver/platform quirk, PDO_ODBC limitation, or something else, but figuring out a good solution for this would make life easier for users. * As always, ODBC being a generic abstraction later itself bites us (i.e no standard way to get last ID). I'm curious if anyone has suggestions for what to be done or how to get these done. Regards, Calvin * -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: https://www.php.net/unsub.php
