Ronald J Kimball wrote:
Wes Cravens wrote:
In an effort to create strictly sequential (Incrementing Integer no
gaps) primary keys my method has traditionally been:
BEGIN;
LOCK table;
SELECT MAX(id) FROM table;
INSERT INTO table...;
COMMIT;
I'm relatively new to DBIC and have not really seen a way to do this
unless I create a wrapper to handle it.
Is there something I am missing?
Why do require strictly sequential primary keys?
It's not always necessary but we do have architecture in an accounting
transaction system where items must be strictly sequential and can also
never be deleted. The auditing side of the application require this.
Wes
_______________________________________________
List: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/dbix-class
IRC: irc.perl.org#dbix-class
SVN: http://dev.catalyst.perl.org/repos/bast/DBIx-Class/
Searchable Archive: http://www.grokbase.com/group/[email protected]
