All good. I looked closely at the new logic in the Sequence method; other
changes look plausible but I'm not familiar enough with AIS building and
merging to be sure. I believe the Persistit branch is now also good to go.
On Thu, Apr 11, 2013 at 11:07 AM, Nathan Williams <email address hidden>wrote:
> That is probably the simplest. Should be just a tiny parser tweak to get
> hat ALTER accepted I think.
>
> Postgres is similar. For SERIAL columns, they create the table as is,
> create and attach sequence, restore value with a routine, and then do the
> table inserts. They don't do IDENTITY so the BY DEFAULT vs ALWAYS isn't an
> issue. If you insert values manually into them, it will get a duplicate key
> when the sequence comes to it.
> --
>
> https://code.launchpad.net/~nwilliams/akiban-server/seq-accum-fix/+merge/158279
> Your team Akiban Technologies is subscribed to branch lp:akiban-server.
>
All good. I looked closely at the new logic in the Sequence method; other
changes look plausible but I'm not familiar enough with AIS building and
merging to be sure. I believe the Persistit branch is now also good to go.
On Thu, Apr 11, 2013 at 11:07 AM, Nathan Williams <email address hidden>wrote:
> That is probably the simplest. Should be just a tiny parser tweak to get /code.launchpad .net/~nwilliams /akiban- server/ seq-accum- fix/+merge/ 158279
> hat ALTER accepted I think.
>
> Postgres is similar. For SERIAL columns, they create the table as is,
> create and attach sequence, restore value with a routine, and then do the
> table inserts. They don't do IDENTITY so the BY DEFAULT vs ALWAYS isn't an
> issue. If you insert values manually into them, it will get a duplicate key
> when the sequence comes to it.
> --
>
> https:/
> Your team Akiban Technologies is subscribed to branch lp:akiban-server.
>