*** Tom Lane <[EMAIL PROTECTED]> [Tuesday, 02.January.2001, 18:38 -0500]:
> To enlarge a little more: the most common way to get burnt by this is
> to have different LC_xxx environment variables when starting the
> postmaster from a boot script as you do when running initdb or starting
> the postm
I have PSQL 7.02
classic join on Two tables:
select l.id from linia l,lk_strefa2linia lk
where l.id = lk.fk_linia and lk.fk_strefa=5;
gives correct linia.ids.
but
select linia.id from linia l,lk_strefa2linia lk
where l.id = lk.fk_linia and lk.fk_strefa=5;
(the only difference is second word:
*** Stephan Szabo <[EMAIL PROTECTED]> [Sunday, 06.August.2000, 14:26
-0700]:
>
> Actually, you should only be seeing one constraint out on the referencing
> table and two out of the referenced one, but yes, fundamentally it only is
> dumping the constraint triggers for the table you are dumping
*** Bruce Momjian <[EMAIL PROTECTED]> [Saturday, 05.August.2000, 19:39 -0400]:
> > Not to mentions fact that in a few places in docs it's shown as a method
> > for copying table "SELECT... INTO" which does not "take" keys with it
> > leading to database knwoledge loss.
>
> That is a good point.
Could someone explain me some fact about FK handling in postgresql (7.0.2) ?
1. WHen I create table with foreign key to other one ( with ON UPDATE CASCADE),
i get two constraints for created table: one for insert one for update.
Additionaly there is created constraint (on rows deletion) in refere
