Re: Re: cvs: php4 /pear DB.php /pear/DBcommon.phpmysql.php
| From: | Chuck Hagenbuch | Date: | Mon, 04 Dec 2000 22:46:50 +0000 |
| Subject: | Re: Re: cvs: php4 /pear DB.php /pear/DBcommon.phpmysql.php | ||
| References: | 1 2 3 4 5 6 7 | Groups: | php.pear |
| Request: | Send a blank email to php-pear+get-528@lists.php.net to get a copy of this message | ||
Quoting Sebastian Bergmann <sb@sebastian-bergmann.de>:
> That wasn't the "how" I meant. I mean, we don't really want to check
> during each and every call to nextid() if the table exists, do we?
>
> So, we would need to put it into the PEAR installation stuff, which makes
> no sense, either, since we need that db_sequence in every database we work
> on.
No, that doesn't work...
How about only running the table-creation branch of the code if you get an
error running the initial query (or, analyze whatever error you get back to see
whether you need to make the table or just the row).
> > Because this is going to be DB-specific, the nextid() function in
> > DB_common should probably be a stub returning a DB_NOT_SUPPORTED
> > error object, with implementations (and thus table syntax) stored in
> > the individual drivers.
>
> I was thinking about that, but need to do more of it - thinking I mean
> :-)
? Do you have arguments for keeping it in DB_common?
-chuck
--
Charles Hagenbuch, <chuck@horde.org>
"If you can't stand the heat, get out of the chicken!" - Baby Blues