Title: RE: [GENERAL] Roll Back dont roll back counters
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Um, no, primary keys should not always be opaque. Technical primary
keys should always be opaque. Relational modelling has been built to
exploit primary keys actually being the business
"Ben-Nes Michael" <[EMAIL PROTECTED]> writes:
> Its not that I care about holes, but if roll back mean to return the DB to
> its original status because a foul sql chain command then logically I expect
> that everything will roll back like the action was never accorded
That's the general rule, bu
Its not that I care about holes, but if roll back mean to return the DB to
its original status because a foul sql chain command then logically I expect
that everything will roll back like the action was never accorded
> Why do people care about holes anyway? I've never understood that...
>
-
On Thu, 16 Aug 2001, Martijn van Oosterhout wrote:
> You can tell the order anyway. The order doesn't change, it's only that
> there may be numbers missing,
Please note the message from "Michael Ansley (UK)". If two of more
connections get a cache from a sequence and the inserts are 'sporatic'
-feira, 16 de agosto de 2001 09:27
To: Martijn van Oosterhout
Cc: Ben-Nes Michael; [EMAIL PROTECTED]
Subject: Re: [GENERAL] Roll Back dont roll back counters
On Thu, 16 Aug 2001, Martijn van Oosterhout wrote:
> Why do people care about holes anyway? I've never understood that...
The sin
On Thu, 16 Aug 2001, Martijn van Oosterhout wrote:
> Why do people care about holes anyway? I've never understood that...
The single seat syndrome? (It's my database and I'm the only one using
it.)
Trying to put intelligence into the field? (I can tell the order the
entries were made in the t
From: "Ben-Nes Michael" <[EMAIL PROTECTED]>
> If I design a table with SERIAL type and then try to insert few rows, but
> some of the rows are rolled back the roll back process does not roll back
> the counter status.
>
> Is there a way to do a roll back to the counter ?
No - sequences (as used
