guys,
i inserted 1 record into my database (default
nextval('sequencename'::regclass) where (start 1 increment 1)). then i
tried to insert 1 other record twice but both those inserts failed
because of a domain check (ERROR: value too long for type character
varying(X). when i was finally able to
John Smith [EMAIL PROTECTED] writes:
i had insert errors yesterday (ERROR: invalid input syntax for
integer ERROR: column 'columnname' is of type date but expression is
of type integer) but they didn't cause any increment jumps. and when
i insert a record now the sequence increments just
On Thu, Jan 25, 2007 at 12:33:51 -0500,
John Smith [EMAIL PROTECTED] wrote:
guys,
i inserted 1 record into my database (default
nextval('sequencename'::regclass) where (start 1 increment 1)). then i
tried to insert 1 other record twice but both those inserts failed
because of a domain check
On 1/25/07, John Smith [EMAIL PROTECTED] wrote:
guys,
i inserted 1 record into my database (default
nextval('sequencename'::regclass) where (start 1 increment 1)). then i
tried to insert 1 other record twice but both those inserts failed
because of a domain check (ERROR: value too long for type
On Thursday 25 January 2007 09:53, Douglas McNaught wrote:
Nature of the beast. Â Sequence increments aren't rolled back on
transaction abort (for performance and concurrency reasons), so you
should expect gaps.
Behavior long ago noted and accounted for. But I've always wondered why this
was
Benjamin Smith [EMAIL PROTECTED] writes:
On Thursday 25 January 2007 09:53, Douglas McNaught wrote:
Nature of the beast. Â Sequence increments aren't rolled back on
transaction abort (for performance and concurrency reasons), so you
should expect gaps.
Behavior long ago noted and accounted
Douglas McNaught wrote:
Benjamin Smith [EMAIL PROTECTED] writes:
On Thursday 25 January 2007 09:53, Douglas McNaught wrote:
Nature of the beast. ?Sequence increments aren't rolled back on
transaction abort (for performance and concurrency reasons), so you
should expect gaps.
