| From: | Chris Travers <chris(dot)travers(at)gmail(dot)com> |
|---|---|
| To: | Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at> |
| Cc: | "Rafal Pietrak *EXTERN*" <rafal(at)zorro(dot)isa-geek(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: foreign key from array element |
| Date: | 2012-09-18 09:34:59 |
| Message-ID: | CAKt_ZfsUKh9fHduJsHWQBcPzfVwGDd76g6n56WTjDFdp+kDsDg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Tue, Sep 18, 2012 at 12:37 AM, Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at>wrote:
>
>
> You :^)
>
> The list of patches for the commitfest is here:
> https://commitfest.postgresql.org/action/commitfest_view?id=15
>
> There is no reviewer for "Array ELEMENT Foreign Keys" yet.
>
> Silly question perhaps better saved for the review process but what does
that buy us that many<->many mapping tables don't? Are there cases where
doing this with a constraint trigger is already preferable to using extra
tables?
Best wishes,
Chris Travers
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Eden Cardim | 2012-09-18 09:53:15 | Column aliases in WHERE clauses |
| Previous Message | Craig Ringer | 2012-09-18 09:10:54 | Data recovery after inadvertent update? |