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
> SEQUENCE, but this is (IMHO) wordy.
>
> You can select from it to find the current value with CURRVAL(), or
> get the value and increment it in one operation as:
>
> SELECT NEXTVAL ( <sequencename> );
>
> -- Kevin
>
>
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 <column_name> INTEGER NOT NULL references
<other_table>(id) and i cannot understand why sqlalchemy whant to use it
as a
<column_name> SERIAL
Thank you
Glauco
--
+------------------------------------------------------------+
Glauco Uri - Programmatore
glauco(at)allevatori.com
Sfera Carta Software(r) [EMAIL PROTECTED]
Via Bazzanese,69 Casalecchio di Reno(BO) - Tel. 051591054
+------------------------------------------------------------+
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"sqlalchemy" group.
To post to this group, send email to sqlalchemy@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/sqlalchemy?hl=en
-~----------~----~----~----~------~----~------~--~---
