Description: ------------ In PEAR::DB, it was possible to access sequences from other databases in a script like this: $userid = $db->nextId("database.sequence"); In MDB2, it gives the following error: Error message: nextID: on demand sequence database.sequence could not be created This is annoying because I use the table name as the sequence name. A lot of the time, the user table may be called from another database. Using MySQL driver. Test script: --------------- <?php print_r($db->nextId("database.sequence")); ?> Expected result: ---------------- Sequence should function as expected using table in specified database. Actual result: -------------- Error message: nextID: on demand sequence database.sequence could not be created

I should add that it seems like I'm getting Error message: nextID: on demand sequence database.sequence could not be created

I should add that it seems like I'm getting the following error message because of a permission error. Error message: nextID: on demand sequence database.sequence could not be created More accurately, PEAR::MDB2 treats database.sequence as database_sequence and creates a database_sequence_seq table rather than using sequence_seq in the database named database.

This bug has been fixed in CVS. If this was a documentation problem, the fix will appear on pear.php.net by the end of next Sunday (CET). If this was a problem with the pear.php.net website, the change should be live shortly. Otherwise, the fix will appear in the package's next release. Thank you for the report and for helping us make PEAR better.