Re: Enforcing serial uniqueness?

From: Csaba Nagy <nagy(at)ecircle-ag(dot)com>
To: Alban Hertroys <alban(at)magproductions(dot)nl>
Cc: Postgres general mailing list <pgsql-general(at)postgresql(dot)org>
Subject: Re: Enforcing serial uniqueness?
Date: 2006-03-22 12:38:31
Message-ID: 1143031111.23597.33.camel@coppola.muc.ecircle.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

> I didn't suggest anything of the kind. I was just suggesting a (IMO)
> cleaner way to allow access to the sequence, so that the users of the
> OP's database don't make too much of a mess of it. As I said, it won't
> matter much to the sequence. It's just a matter of wanting to do things
> the 'proper' way.

OK, my fault not reading the original post, but "sequences" and "no gap"
have some kind of emotional trigger for me cause they remind me the ID
mess I mentioned.

I still didn't read completely the OP, and I don't have time to do it
now, so the following might not apply: I guess the OP should stop using
user accessible sequence IDs anyway, and use letter-code aliases instead
if really needed. Those won't have any sequencing, can be made human
readable and are still easy to type. And the data base WILL become
corrupted sooner or later if the users have direct access to it.

Just my 2c,
Csaba.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Steven Brown 2006-03-22 13:04:32 Re: Enforcing serial uniqueness?
Previous Message Alban Hertroys 2006-03-22 12:28:17 Re: Enforcing serial uniqueness?