OCI extension - brainstorming
| From: | predator79 at web dot de | Date: | Thu, 17 Oct 2002 13:54:37 +0000 |
| Subject: | OCI extension - brainstorming | ||
| Groups: | php.dev | ||
| Request: | Send a blank email to php-dev+get-89651@lists.php.net to get a copy of this message | ||
just a few thoughts.
the OCIQuery that maxim proposed has the advantage of being pretty high-level, making it much easier
for mysql programmers to get a grip at oracle, but then again i think that every self-respecting php
developer would write a function/method that does this for him ;-). from an extension point of view
i think we shouldn't give up the granularity IMHO... but if we go for it, maybe we can change
the result type (in accordance to the shift of focus in php5) to be a php object that contains the
statement handle, row+column count,..etc. fields?
while we are at it and regarding data types: shall we change the way lobs are handled? perhaps a
switch between object/content return types. i cannot quite see the advantage of having the lobs
loaded on demand, rather than 'unpacking' them as soon as a result is fetched.
btw, connection pooling, which thies mentioned, would be an absolute +.
perhaps we should wrap around more oci functions, specially the type conversion ones, and offer
these as part of the extension.
Abdul