[Nitro] Og, adapting postgresql to reorgnaization

[transfire at gmail.com]

On Mar 5, 8:02 pm, "Judson Lester" <nya... at gmail.com> wrote:
> Oh, we're on the same page.  I just wish that an auto-incrementing
> type was part of the SQL spec, so that we didn't have such vast
> variations between how databases handle a pretty basic operation.
>
> That said, I continue to examine how Postgres could usefully use it's
> sequence lookup safely.
>
> Judson
>
> On 3/5/07, Jos Backus <j... at catnook.com> wrote:
>
> > On Wed, Feb 21, 2007 at 04:33:28PM -0800, Judson Lester wrote:
> > > Why autoincrements weren't part of the original spec, I'll never know.
>
> > But PostgreSQL has support for sequences, which are in SQL2003, unlike MySQL's
> > proprietary autoincrement "feature". See
> >http://www.varlena.com/GeneralBits/71.phpand
> >http://dev.mysql.com/tech-resources/faq.html#gen5
>
> > (Yes, I vastly prefer PostgreSQL over MySQL.)

Think this has been discussed before and the solution is to not use
autoincrement. There shoud be an adapter method #new_id(table). In
PostgreSQL this would quesry the sequence.

Can MySQL handles this? Other stores?

T.