Richard Huxton writes:
> Alban Hertroys wrote:
>> I'm not sure how we got the "content" column from "description" to
>> reference "localization" back in version 7.3. Fact is, we can't seem to
>> do this anymore since version 7.4:
> I don't have 7.3.x to hand any more, but if you could create su
Tom Lane wrote:
Having just tried it, I can say that the last version that would take
that without complaint is 7.0. 7.1 and later give variants of
ERROR: UNIQUE constraint matching given keys for referenced table
"localization" not found
So I'm not sure what Alban actually did.
Neither am
Martijn van Oosterhout wrote:
On Tue, Aug 09, 2005 at 02:31:16PM +0200, Alban Hertroys wrote:
Hi all,
We migrated a database from version 7.3 something to 7.4.7 a while ago,
and ever since that time we can't make new foreign keys to a particular
table. The problem is that the primary key on
On Tue, Aug 09, 2005 at 02:31:16PM +0200, Alban Hertroys wrote:
> Hi all,
>
> We migrated a database from version 7.3 something to 7.4.7 a while ago,
> and ever since that time we can't make new foreign keys to a particular
> table. The problem is that the primary key on that table is on two
>
Alban Hertroys wrote:
Hi all,
We migrated a database from version 7.3 something to 7.4.7 a while ago,
and ever since that time we can't make new foreign keys to a particular
table.
You shouldn't have been able to before.
> The problem is that the primary key on that table is on two
columns
Hi all,
We migrated a database from version 7.3 something to 7.4.7 a while ago,
and ever since that time we can't make new foreign keys to a particular
table. The problem is that the primary key on that table is on two
columns that are unique together, but that only one of them should be
refe
