甲骨文，PDO_OCI 与 OCI8

问题描述

我工作的公司目前使用一些基本功能来抽象 OCI 库作为数据库连接的一种手段.我们正在考虑切换到 PHP 的 PDO 对象，但从一些快速搜索来看，Oracle 驱动程序似乎比其他 PDO 驱动程序成熟一些.如果有人在生产环境中使用过 PDO/oci8，我将不胜感激.

The company I work for currently uses some basic functions to abstract the OCI libraries as a means for DB connectivity. We're considering switching to PHP's PDO object, but from some quick searches, it looks like the Oracle driver is a bit less mature than the other PDO drivers. I would appreciate some pro/cons for PDO/oci8 from anyone who has used it in a production environment.

谢谢！

推荐答案

在我看来，Oracle 对为 PDO 开发驱动程序不感兴趣，它正在开发自己的驱动程序，以使您更接近 oracle 数据库......到 oracle 驱动程序...等等:)

It seems to me that Oracle is not interested in developing a driver for PDO it's developing it's own driver to keep you close to oracle database... to oracle driver... etc. :)

据我所知，如果你能应付 max.4000 CHARS 的 VARCHAR2 文本.如果您需要 CLOB(和/或更大)，请不要使用 PDO_OCI.

As far as I've seen there is no problem if you can cope with max. texts of VARCHAR2 of 4000 CHARS. If you need CLOBs (and/or bigger) don't go with PDO_OCI.

我创建了一套类PDOSurrogate"，作为 Oracle 的 PDO 替代品.当 PDO 足够成熟时，我可以使用 Refactor->Rename 将其更改为 PDO.

I've created a suite of classes "PDOSurrogate" as a drop in replacement for PDO with Oracle. When PDO is mature enough I can use Refactor->Rename to change it to PDO.

这篇关于甲骨文，PDO_OCI 与 OCI8的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持跟版网！