Skip site navigation (1) Skip section navigation (2)

Re: CHECK constraint on multiple tables

From: Thomas Kellerer <spam_eater(at)gmx(dot)net>
To: pgsql-sql(at)postgresql(dot)org
Subject: Re: CHECK constraint on multiple tables
Date: 2009-09-14 17:00:37
Message-ID: h8lsrk$g9g$1@ger.gmane.org (view raw or flat)
Thread:
Lists: pgsql-sql
Mario Splivalo wrote on 14.09.2009 16:20:
>> Have you considered refactoring so there's only one table?
> 
> Unfortunately I can't do that, due to the
> object-relational-mapper-wrapper-mambo-jumbo.
> 
You could still refactor that into one single table, then create two updateable views with the names that the dreaded OR mapper expects. That would enable you to have a proper unique check on the base table, and you OR mapper still sees two tables that it can update.

Thomas


In response to

pgsql-sql by date

Next:From: A. KretschmerDate: 2009-09-15 07:49:57
Subject: Re: ordered by join? ranked aggregate? how to?
Previous:From: wstrzalkaDate: 2009-09-14 14:25:33
Subject: ordered by join? ranked aggregate? how to?

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group