From: Jaime Casanova <systemguards@yahoo.com>
To: pgsql-admin@postgresql.org
Subject: Re: unique constraints on foreign keys
Date: Mon, 20 Sep 2004 18:18:52 -0500 (CDT)
Message-ID: <20040920231852.9042.qmail@web50002.mail.yahoo.com> (raw)
In-Reply-To: <20040920135913.H79243@megazone.bigpanda.com>
--- Stephan Szabo <sszabo@megazone.bigpanda.com>
escribió:
>
> On Mon, 20 Sep 2004, Jaime Casanova wrote:
>
> > There is a way to not enforce the creation of a
> > primary or unique index on a referenced table?
>
> Not really. It's not the index that's important
> per-se, it's the uniqueness that is implied.
OK. What about to teach the planner always do a
seq on that table and do not ask for use the
index? but not using "set" instructions. can i do
that?
_________________________________________________________
Do You Yahoo!?
Información de Estados Unidos y América Latina, en Yahoo! Noticias.
Visítanos en http://noticias.espanol.yahoo.com
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-admin@postgresql.org
Cc: systemguards@yahoo.com
Subject: Re: unique constraints on foreign keys
In-Reply-To: <20040920231852.9042.qmail@web50002.mail.yahoo.com>
* 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