Heh, I see. The sequence currval was set lower than what was already in
the table. It just so happened we had holes in our data for the values
it was selecting. Thanks for pointing that out!
Kris
Michael Fuhr wrote:
On Thu, Mar 24, 2005 at 04:45:02PM -0500, Kris Kiger wrote:
I'm positive n
On Thursday 24 March 2005 1:45 pm, Kris Kiger wrote:
> I'm positive no one else has been in the database. There are two
> of us who work on it and we have been side by side all afternoon.
> The problem appears to be purely internal to the database. I'm
> running more tests as we speak and we are
Kris Kiger <[EMAIL PROTECTED]> writes:
> I'm positive no one else has been in the database. There are two of us
> who work on it and we have been side by side all afternoon. The problem
> appears to be purely internal to the database. I'm running more tests
> as we speak and we are still reci
On Thu, Mar 24, 2005 at 04:45:02PM -0500, Kris Kiger wrote:
> I'm positive no one else has been in the database. There are two of us
> who work on it and we have been side by side all afternoon. The problem
> appears to be purely internal to the database. I'm running more tests
> as we speak
I'm positive no one else has been in the database. There are two of us
who work on it and we have been side by side all afternoon. The problem
appears to be purely internal to the database. I'm running more tests
as we speak and we are still recieving the same sporadic errors. It
works for
On Thu, 2005-03-24 at 15:21, Kris Kiger wrote:
> I have a table that looks like this:
>
> Table "public.hd"
> Column |Type
> |Modifiers
> ---+-
I have a table that looks like this:
Table "public.hd"
Column |Type
|Modifiers
---+-+-
