On Saturday 14 May 2011, you wrote:
> You have been subscribed to a public bug:
>
> I tried upgrading my postgres from 8.4 to 9.0 which lead to the
> following error:
>
> Restoring database schema to new cluster
>
> > > psql:/usr/lib/postgresql/9.0/bin/pg_upgrade_dump_db.sql:24606: ERROR:
> > > column "name" in child table must be marked NOT NULL
>
I have already filed a bug in postgres, a few days ago, see #6024
We are doing (in postgres) sth. that the specification didn't expect us, but
allowed us, to do: drop the constraint from an inherited table. Since the
inheritance is a feature only used in ir.actions, we are unlikely to modify
our ORM to prevent that.
Of course, what we can do, is to fix the orm models not to have null names :)
But that may not fix all existing dbs (to be investigated further).
On Saturday 14 May 2011, you wrote: lib/postgresql/ 9.0/bin/ pg_upgrade_ dump_db. sql:24606: ERROR:
> You have been subscribed to a public bug:
>
> I tried upgrading my postgres from 8.4 to 9.0 which lead to the
> following error:
>
> Restoring database schema to new cluster
>
> > > psql:/usr/
> > > column "name" in child table must be marked NOT NULL
>
I have already filed a bug in postgres, a few days ago, see #6024
We are doing (in postgres) sth. that the specification didn't expect us, but
allowed us, to do: drop the constraint from an inherited table. Since the
inheritance is a feature only used in ir.actions, we are unlikely to modify
our ORM to prevent that.
Of course, what we can do, is to fix the orm models not to have null names :)
But that may not fix all existing dbs (to be investigated further).