John,
in addition to the list you posted, there's
- inconsistent/incomplete metadata support. it would be nice, for example if
the MySQL extension would be more
precise about a field type than "string", etc
i tried hard and failed to describe why i'd want to start a C based DB
library, an
On Wed, 21 Nov 2001 16:14:04 +0100 (MET)
Luc Saint-Elie <[EMAIL PROTECTED]> wrote:
> En réponse à Pierre-Alain Joye <[EMAIL PROTECTED]>:
>
>
> > This definition defines more a common interface to connect to a db,
> > execute queries, fetch the result and eventually gives errors reports
> > ;).
En réponse à Pierre-Alain Joye <[EMAIL PROTECTED]>:
> This definition defines more a common interface to connect to a db,
> execute queries, fetch the result and eventually gives errors reports
> ;).
Somehow yes (do I still win the $15,000 ???)
> IMO, the need of a real abstraction layer is no
En réponse à Joao Prado Maia <[EMAIL PROTECTED]>:
> Now for the $15,000 question: does anyone else agree with this ? If
> PEAR::DB is not abstracting the database what is the purpose of such a
> library ?
Well I strongly need thoses $15 000 $ so
What is the purpose ?
As a "average php use
Hello,
John Lim wrote:
> Each designer has a different point of view, like Tomas has
> written a really excellent oci8 "select limit" emulation, but looking
> at the code, it's so complicated that i decided not to incorporate it
> in ADODB because I value simplicity. I know Tomas' code works
> in
