On Mon, 2005-08-15 at 11:48 -0400, Madison Kelly wrote:
> Douglas McNaught wrote:
> > Madison Kelly <[EMAIL PROTECTED]> writes:
> >
> >
> >> I want to use a 'serial uniue' column in a table but there is
> >> likely to be many, many inserts and deletes from this column. I was
> >> wondering,
Michael Fuhr wrote:
On Mon, Aug 15, 2005 at 11:07:31AM -0400, Madison Kelly wrote:
This might seem like an odd question but I couldn't find the answer
in the docs (did I miss the obvious?).
The serial type is a just convenient way to define an integer column
that takes its default value fro
Madison Kelly <[EMAIL PROTECTED]> writes:
> Douglas McNaught wrote:
>> Madison Kelly <[EMAIL PROTECTED]> writes:
>>
>>> I want to use a 'serial uniue' column in a table but there is
>>> likely to be many, many inserts and deletes from this column. I was
>>> wondering, what happens when the
On Mon, Aug 15, 2005 at 11:07:31AM -0400, Madison Kelly wrote:
> This might seem like an odd question but I couldn't find the answer
> in the docs (did I miss the obvious?).
The serial type is a just convenient way to define an integer column
that takes its default value from a sequence, so loo
Madison Kelly <[EMAIL PROTECTED]> writes:
>I want to use a 'serial uniue' column in a table but there is
>likely to be many, many inserts and deletes from this column. I was
>wondering, what happens when the serial value reaches
>2,147,483,647'? Does it roll back over to '1' and ke
Douglas McNaught wrote:
Madison Kelly <[EMAIL PROTECTED]> writes:
I want to use a 'serial uniue' column in a table but there is
likely to be many, many inserts and deletes from this column. I was
wondering, what happens when the serial value reaches
2,147,483,647'? Does it roll back ov
