Bug #17680 Updated: PEAR->nextId does not allow cross-database sequences
| From: | cox@php.net | Date: | Mon, 10 Jun 2002 13:15:46 +0000 |
| Subject: | Bug #17680 Updated: PEAR->nextId does not allow cross-database sequences | ||
| References: | 1 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-6875@lists.php.net to get a copy of this message | ||
ID: 17680
Updated by: cox@php.net
Reported By: leedjarv@interest.ee
-Status: Open
+Status: Closed
Bug Type: PEAR related
Operating System: Linux
PHP Version: 4.2.1
New Comment:
This bug has been fixed in CVS. You can grab a snapshot of the
CVS version at http://snaps.php.net/. In case this was a
documentation
problem, the fix will show up soon at http://www.php.net/manual/.
In case this was a PHP.net website problem, the change will show
up on the PHP.net site and on the mirror sites.
Thank you for the report, and for helping us make PHP better.
Previous Comments:
------------------------------------------------------------------------
[2002-06-10 09:04:24] leedjarv@interest.ee
PEAR's implementation of sequences does not allow cross-database
sequences for DBMSes which allow x-db queries. For example, with MySQL,
cross-database queries are allowed, but one can't do
$new_id = $SQL->nextId("database2.table");
because the dot (.) in sequence name is translated into underscore (_),
which results in sequence name of "database.database2_table_seq", which
is NOT the intended result.
------------------------------------------------------------------------
--
Edit this bug report at http://bugs.php.net/?id=17680&edit=1