[sqlalchemy] Re: strange serial problem in postgres

2007-08-17 Thread Marco Mariani
Glauco ha scritto: > Thank you kevin , i've worked a lot over PG and this tecnique is > consolidated in our model.. but here the problem is that the column > is a simply INTEGER NOT NULL references > (id) and i cannot understand why sqlalchemy whant to use it > as a > SERIAL > Make

[sqlalchemy] Re: strange serial problem in postgres

2007-08-17 Thread Glauco
justanyone ha scritto: > In Postgres at least, serial columns are typically defined as: > > CREATE TABLE FOO ( > id_piano serial primary key, > ... > ) > > This automatically creates a sequence foo_id_piano_seq. Of course, > you can also create a sequence separate from a table with CREATE >

[sqlalchemy] Re: strange serial problem in postgres

2007-08-17 Thread justanyone
In Postgres at least, serial columns are typically defined as: CREATE TABLE FOO ( id_piano serial primary key, ... ) This automatically creates a sequence foo_id_piano_seq. Of course, you can also create a sequence separate from a table with CREATE SEQUENCE, but this is (IMHO) wordy. You

[sqlalchemy] Re: strange serial problem in postgres

2007-08-17 Thread Michael Bayer
On Aug 17, 2007, at 4:21 AM, Glauco wrote: > > SQLError: (ProgrammingError) relation "scadenziario_id_piano_seq" does > not exist > 'select nextval(\'"scadenziario_id_piano_seq"\')' {} > > but > > the table is: > > > CREATE TABLE scadenziario ( > id_pianoINTE