Re: *Proper* solution for 1..* relationship?
| От | Josh Kupershmidt |
|---|---|
| Тема | Re: *Proper* solution for 1..* relationship? |
| Дата | |
| Msg-id | CAK3UJREh6OoBF4fC5N6KEMqO3biOJ1An-B33GcP2_L-nO9T+cw@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: *Proper* solution for 1..* relationship? (Wolfgang Keller <feliphil@gmx.net>) |
| Ответы |
Re: *Proper* solution for 1..* relationship?
|
| Список | pgsql-novice |
On Tue, Apr 30, 2013 at 7:56 AM, Wolfgang Keller <feliphil@gmx.net> wrote:
>> The most straightforward way I know to enforce this is to check
>> that at least one child exists in a DEFERRED trigger on the the
>> parent. You still need to worry about concurrency issues.
>
> Imho it's absurd that I have to do this ("worry about concurrency
> issues") myself, how long - more than fourty years after the invention
> of relational databases?
You're not the first one to wish for something like this, and the SQL
standard actually has the CREATE ASSERTION syntax which I believe
would be able cover your use-case. Unfortunately, almost no databases
support this feature :-(
Josh
В списке pgsql-novice по дате отправления: