| Subject: | Provide a way to bypass DBIx::Sequence |
In the current version, Coat::Persistent always relies on DBIx::Sequence
for handling primary keys sequences.
That's good, but the user should be able to disable this if he'd rather
use the internal sequence system of the DB engine (like MySQL
autoincrement or Postgres sequences).
Something like that would be great:
Coat::Persistent->disable_internal_sequencer();
If this is called, DBIx::Sequence is no more used, for getting a next ID
for a primary key, and the value is omitted in the insertions, then the
underlying DB engine takes care of it.