Re: how to implement unusual constraint

From: danmcb <danielmcbrearty(at)gmail(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: how to implement unusual constraint
Date: 2007-06-24 18:45:00
Message-ID: 1182710700.341097.182380@n60g2000hse.googlegroups.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message ssoo 2007-06-25 00:51:30 alter table type from double precision to real
Previous Message Tom Lane 2007-06-24 15:38:14 Re: low transaction ID wrap limit