Does this mean that the auto pk tables are no longer supported? Or is
it just not used on DbAdapters that support sequences?
On 9/6/05, Andrus Adamchik <andru..bjectstyle.org> wrote:
> Right, if you go from 1.1 to 1.2 on PostgreSQL, you'd have to create
> PK sequences. I guess what we can do to make it smoother is extending
> sequence creation syntax to pick current max value per CAY-314:
>
> select setval('pk_my_table', coalesce(max(id) + 1, 200)) from my_table
>
> Andrus
>
>
> On Sep 6, 2005, at 10:39 AM, Gentry, Michael ((Contractor)) wrote:
>
> > I've been flopping between 1.1 and 1.2 and when I tried running one of
> > my demo apps, written using 1.1, under 1.2 with PostgreSQL it
> > completely
> > bombed. I couldn't do INSERTs at all because it kept doing a SELECT
> > nextval('pk_table') to try to get primary keys. Well, being a 1.1
> > application, I didn't have sequences in my database, I had the
> > auto_pk_support table for primary keys.
> >
> > Does this mean if someone has something written in 1.1/PostgreSQL and
> > then tries to use 1.2, they have migration problems?
> >
> > Thanks,
> >
> > /dev/mrg
> >
> >
>
>
This archive was generated by hypermail 2.0.0 : Tue Sep 06 2005 - 10:54:34 EDT