> >Why not just drop the "references" clause? I mean, the point of having
> >transactions is to guarantee integrity within a transaction, if you're not
> >going to have that, why even bother with the clause?
> >
> Quite the opposite - the point is to guaratee the integrity *outside*
> the transaction.
That's actually what I was saying. Within a single transaction rather
than across multiple transactions. If you have to go across multiple
transactions, there's no real point in having integrity constraints.
> >Most of my databases don't even user "references", just because I like the
> >flexibility, and I have multitable keys (keys that can refer to rows from
> >multiple tables).
> >
> >
> Not much to brag about :-)
Do you know of a better way to handle multitable references?
Jon
>
> Dima
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 9: the planner will ignore your desire to choose an index scan if your
> joining column's datatypes do not match
>