First, I must say that I misread part of the error message you had in
your last message, which I think may have lead to some confusion. It
says that an implicit *index* was created, which I misread as *sequence*.
The problem is still that what ever the default value torque used for
the primary key column was already used when you tried to .save() the
Let me clarify that indexes and sequences are two separate things;
sequences are used for automatically generating primary key values, and
indices are used to help speed row access.
Jakub Piechnik wrote:
> Oki, but can I check index value from the Torque level? If so - how?
You can, but you may not need to do this. See below.
> And is it possible to switch off automate indexing in postgresql?
Torque does provide the id broker, but I have not used it, so I cannot
offer any advice there. I highly recommend using PostgreSQL's sequences.
You can change how primary keys are managed by setting the idMethod
(note capital M) attribute of the table tag, or by setting the
defaultIdMethod on the database tag in the schema file.