Package home | Report new bug | New search | Development Roadmap Status: Open | Feedback | All | Closed Since Version 1.11.5

Doc Bug #16708 SequenceKey() Required When Not Using INI
Submitted: 2009-10-18 03:51 UTC
From: mabgfounder Assigned:
Status: Open Package: DB_DataObject (version 1.8.12)
PHP Version: 5.3.0 OS: Windows XP
Roadmaps: (Not assigned)    
Subscription  
Comments Add Comment Add patch


Anyone can comment on a bug. Have a simpler test case? Does it work for you on a different platform? Let us know! Just going to say 'Me too!'? Don't clutter the database with that please !
Your email address:
MUST BE VALID
Solve the problem : 36 - 7 = ?

 
 [2009-10-18 03:51 UTC] mabgfounder (Brian Alexander)
Description: ------------ First off - thanks for maintaining what appears to be a nice db object library. When working from INI files it was easy to get started and worked right out of the box. However, when I tried to make classes from scratch, using the docs as a guide, I did not realize that sequenceKey() existed nor how critical it was for things to work correctly. BTW: These are the docs I was using: http://pear.php.net/manual/en/package.database.db-dataobject.intro-autobuilding.php I had no reason for the application's account on mysql to be able to create tables (that I knew of) so I did not grant those permissions. Inserts started failing because of an inability to create {tablename}_seq. I did eventually figure out that a missing sequenceKey() implementation was the problem, and after some experimentation appear to have figured out how to correctly implement it. However, a lot of time would have been saved at it been in the documentation. Thanks again for all of your time and help. This seems to be a really great library. Test script: --------------- You should be able to use the example on the page I listed with a mysql database where the user does not have table create permissions granted. Expected result: ---------------- Inserts and updates will fail

Comments