From: Gianluca Riccardi <ml-reader@moonwatcher.it>
To: pgsql-sql@postgresql.org
Subject: Re: DB design and foreign keys
Date: Wed, 14 Dec 2005 11:27:47 +0100
Message-ID: <439FF3A3.7080909@moonwatcher.it> (raw)
In-Reply-To: <1134500394.3587.115.camel@state.g2switchworks.com>
References: <439F0FE8.1050503@moonwatcher.it>
<1134500394.3587.115.camel@state.g2switchworks.com>
[cut]
> Given this table layout, I'm gonna take a wild guess and ask if you're
> coming from MySQL and expecting the second serial order_code to be a
> sub-autoincrement to id?
>
no, always used PostgreSQL, but i'm having a deeper approach now, until
now i've been using th ORDBMS in a very 'easy' manner :(
> If so, it won't be. That's a mysqlism. If
> you want something similar, you'll have to implement it yourself, and
> note that such a thing tends to be a poor performer with lots of
> parallel updates, and it can also be susceptible to race conditions if
> no locking is used.
>
>
thank you, regards,
Gianluca Riccardi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: ml-reader@moonwatcher.it
Subject: Re: DB design and foreign keys
In-Reply-To: <439FF3A3.7080909@moonwatcher.it>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox