Re: how to implement unusual constraint - Mailing list pgsql-general

From danmcb
Subject Re: how to implement unusual constraint
Date
Msg-id 1182710700.341097.182380@n60g2000hse.googlegroups.com
Whole thread Raw
In response to Re: how to implement unusual constraint  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: how to implement unusual constraint  (Andrew Sullivan <ajs@crankycanuck.ca>)
List pgsql-general
"So frequently the best advice for someone who's thinking of doing
something like this is "redesign your schema so you don't need to". "

I've thought about that. The obvious way to do it would be to split
into two tables, one for the originals, one for the translations (the
objects are actually phrases in many languages). But I'd rather avoid
that because in all other ways, the objects have the same properties,
reference the same objects, and so on. Splitting into two types is not
really desirable, from the point of view of what they are modelling.



pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: low transaction ID wrap limit
Next
From: danmcb
Date:
Subject: Re: finding items with 0 rels for a 0 to many relationship