DB, DB_DO and sequences
| From: | Matt Craig | Date: | Mon, 25 Apr 2005 13:47:20 +0000 |
| Subject: | DB, DB_DO and sequences | ||
| Groups: | php.pear.general | ||
| Request: | Send a blank email to pear-general+get-18946@lists.php.net to get a copy of this message | ||
(my only experience is through DO so maybe this is more a question of DataObject)
Could someone give an explanation of the reasoning behind DB defaulting to using it's own sequences even when a database has native sequences?
For instance,
CREATE TABLE tab1 (
id SERIAL, AUTONUMBER, etc.
...
);
DB creates the sequence, tab1_seq, if not explicitly told not to. Now, not everyone in my company accesses the database with PHP using DB. Some use the command line, some use MS Access, etc. and all those other methods use native sequences. The non-PHP people don't want to use some other non-native sequence such as the one created by DB, because that is extra hassle.
So why does DB do this with sequences? It seems like it would be very common that DB is not the only access method to a database.
matt
--
Disclaimer: This message (including any attachments) contains
confidential information intended for a specific individual and purpose,
and is protected by law. If you are not the intended recipient, you
should delete this message. Any disclosure, copying, or distribution of
this message, or the taking of any action based on it, is strictly
prohibited.