Re: PEAR::DB, backends and assertExtension
| From: | Stig S. Bakken | Date: | Sun, 14 Oct 2001 12:43:51 +0000 |
| Subject: | Re: PEAR::DB, backends and assertExtension | ||
| References: | 1 2 3 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-2281@lists.php.net to get a copy of this message | ||
Markus Fischer wrote:
>
> On Sun, Oct 14, 2001 at 01:22:44AM +0200, Stig S. Bakken wrote :
> > No you haven't overseen anything, so feel free to make it
> > suff^H^H^H^Hconsistent :-)
>
> Ok, done.
>
> If something broke (shouldn't, tested as far as I could) I'll
> fix it.
>
> Some questions which came up my mind:
>
> .) Why do have php extension names and pear::db backends
> different names? E.g. 'informix' => 'ifx' ?
Not sure about this one. It applies to ifx (Tomas) and ibase
(Sterling).
> .) What do you think about a static method of DB which returns an
> array of all supported db extension and a function which
> returns only currently installed extensions ?
>
> array DB::supported_extensions();
>
> Either return a fixed array which has to be maintained
> or make it magic to scan through DB/
>
> and
>
> array DB::installed_extensions();
>
> Which also tries to load missing compiled-in extensions
> so the result is accurat.
We can do that if the DB backends are renamed to match the extensions.
- Stig