Bigserial - sequences on tables

#11

D Yuniskis <not.going.to.be (AT) seen (DOT) com> wrote:

Quote:

In light of this type of usage, could I impose upon you
to please explain the consequences of each of these
"serial/sequence" approaches?

What you're doing is fine, and just what SERIAL is intended for.

The only issue is that you might worry that someone might create a mess
by inserting a record and explicitly specifying the id rather than
letting the automatic value be used. But if you're the only person
modifying the table, it's good enough to just Not Do That.

-M-

#12

On Mon, 28 Feb 2011 23:47:23 +0000, Matthew Woodcraft wrote:

Quote:

If what you want is to forbid people setting explicit values, you can do
that with per-column permissions.

(But before Postgresql 8.4 using a trigger was the best way, yes.)

It still is the best way. It gives you the highest degree of control.

--
http://mgogala.byethost5.com

#13

On 2011-02-28, Mladen Gogala <no (AT) email (DOT) here.invalid> wrote:

Quote:

On Mon, 28 Feb 2011 22:13:29 +0000, Matthew Woodcraft wrote:

It overrides the default (like for any other default), and it doesn't
affect the sequence.

So, when the sequence reaches the given number, you will have a primary
key violation? That sounds like a plan.

yes, that works well. when they retry the next value from the sequence
will be tried. this is usually good.

--
⚂⚃ 100% natural

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

Bigserial - sequences on tables

comp.databases.postgresql comp.databases.postgresql

Re: Bigserial - sequences on tables - 02-28-2011 , 05:52 PM

Re: Bigserial - sequences on tables - 03-01-2011 , 10:35 AM

Re: Bigserial - sequences on tables - 03-09-2011 , 04:19 AM