Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: FOREIGN KEYS vs PERFORMANCE
- From: PFC <lists(at)peufeu(dot)com>
- To: "Michael Glaesemann" <grzm(at)myrealbox(dot)com>, "Rodrigo Sakai" <rodrigo(dot)sakai(at)zanthus(dot)com(dot)br>
- Cc: pgsql-performance(at)postgresql(dot)org
- Subject: Re: FOREIGN KEYS vs PERFORMANCE
- Date: Wed, 12 Apr 2006 09:22:52 +0200
I think this is an old question, but I want to know if it really is well worth to not create some foreign keys an deal with the referential integrity at application-level?????
Trust me : do it in the application and you'll enter a world of hurt. I'm doing it with some mysql apps, and it's a nightmare ; doing cascaded delete's by hand, etc, you always forget something, you have to modify a million places in your code everytime you add a new table, your ORM bloats, you get to write cleanup cron scripts which take forever to run, your website crashes etc.
- Follow-Ups:
- Re: FOREIGN KEYS vs PERFORMANCE
- From: Jim C. Nasby
- Re: FOREIGN KEYS vs PERFORMANCE
- From: Craig A. James
- Re: FOREIGN KEYS vs PERFORMANCE
- References:
- FOREIGN KEYS vs PERFORMANCE
- From: Rodrigo Sakai
- Re: FOREIGN KEYS vs PERFORMANCE
- From: Michael Glaesemann
- FOREIGN KEYS vs PERFORMANCE
- Prev by Date: Re: pgmemcache
- Next by Date: Re: Better index stategy for many fields with few values
- Previous by thread: Re: FOREIGN KEYS vs PERFORMANCE
- Next by thread: Re: FOREIGN KEYS vs PERFORMANCE
- Indexes: