| From: | "Ismael (dot)(dot)(dot)(dot)" <ismaelpsp(at)hotmail(dot)com> |
|---|---|
| To: | <scott(dot)marlowe(at)gmail(dot)com>, <rod(at)iol(dot)ie>, <doug(at)mcnaught(dot)org> |
| Cc: | <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: deleting the master but not the detail |
| Date: | 2008-07-17 18:22:13 |
| Message-ID: | BLU103-W33F7BA55F79BB571BC113AA38E0@phx.gbl |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
It seems like 3 vs 1 so you win :)
I'll drop the constraint and verify the integrity of the new records manually
tanks
>
> On Thu, Jul 17, 2008 at 10:52 AM, Douglas McNaught wrote:
>> On Thu, Jul 17, 2008 at 12:11 PM, Ismael .... wrote:
>>>
>>> hi
>>> I have one of those master-detail relationships here and I need to be able
>>> to delete the master but leave the details untouched
>>
>> Then remove the referential integrity constraint, since it's obviously
>> incompatible with your business requirements.
>
> Generally I'd agree, but it might be useful to set the child record
> referencing id field to NULL in this circumstance.
_________________________________________________________________
Tenemos lo que búscas…JUEGOS.
http://club.prodigymsn.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2008-07-17 18:43:15 | Re: [HACKERS] postmaster.pid not visible |
| Previous Message | Scott Marlowe | 2008-07-17 18:02:29 | Re: deleting the master but not the detail |