From 865d947dc538e35936ba0f962f1c800bfe2afa00 Mon Sep 17 00:00:00 2001 From: Mike Bayer Date: Tue, 31 Jan 2006 02:15:16 +0000 Subject: [PATCH] fixed code error --- doc/build/content/metadata.myt | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/doc/build/content/metadata.myt b/doc/build/content/metadata.myt index 1624944930..26193bbf25 100644 --- a/doc/build/content/metadata.myt +++ b/doc/build/content/metadata.myt @@ -15,9 +15,9 @@ ) user_prefs = Table('user_prefs', engine, - Column('pref_id', Integer, primary_key = True), - Column('user_id', Integer, nullable = False, ForeignKey("users.user_id")) - Column('pref_name', String(40), nullable = False), + Column('pref_id', Integer, primary_key=True), + Column('user_id', Integer, ForeignKey("users.user_id"), nullable=False), + Column('pref_name', String(40), nullable=False), Column('pref_value', String(100)) ) @@ -182,4 +182,4 @@ DROP TABLE employees

Defining a Sequence means that it will be created along with the table.create() call, and more importantly the sequence will be explicitly used when inserting new rows for this table. For databases that dont support sequences, the Sequence object has no effect. A sequence can also be specified with optional=True which indicates the Sequence should only be used on a database that requires an explicit sequence (which currently is just Oracle). A database like Postgres, while it uses sequences to create primary keys, is often used via the SERIAL column option which removes the need for explicit access to the sequence.

- \ No newline at end of file + -- 2.47.2