On Dec 23, 2:55 pm, Christophe Pettus wrote:
> On Dec 23, 2010, at 11:35 AM, Eric wrote:
>
> > a) To fix this, one must identify the sequences that are not correct.
> > I scoured pg_catalog and friends and cannot identify where PostgreSQL
> > exposes the link between the "id" and sequence columns.
On Dec 23, 2010, at 11:35 AM, Eric wrote:
> a) To fix this, one must identify the sequences that are not correct.
> I scoured pg_catalog and friends and cannot identify where PostgreSQL
> exposes the link between the "id" and sequence columns.
Just FYI, it's stored in pg_depend.
--
-- Christophe
We recently started the test and upgrade process to bring our large
Django applications more up to date with 1.3 to help test new things.
We found that http://code.djangoproject.com/changeset/13363 introduced
backwards incompatible changes.
Previously, using PostgreSQL, it was possible to take a m