Message-ID: <4A167F7F.6000509@archonet.com>
Date: Fri, 22 May 2009 11:33:35 +0100
From: Richard Huxton <dev@archonet.com>
User-Agent: Thunderbird 2.0.0.21 (X11/20090320)
MIME-Version: 1.0
To: Frank Joerdens <frank@joerdens.de>
CC: pgsql-sql@postgresql.org, Nic Ferrier <nferrier@woome.com>,
	Edward George <ed@woome.com>,
	Seb Potter <seb@woome.com>, Hannu Krosing <hannu@2ndquadrant.com>
Subject: Re: Make the planner smarter about idiosyncratic (or broken)
	ORM behaviour
References: <7d10d2df0905220233v3e54ab34lb9c3530fe3543a5c@mail.gmail.com>	
	<4A1676E1.6010102@archonet.com>
	<7d10d2df0905220318w3e69e112v42eee46b88d9f284@mail.gmail.com>
In-Reply-To: <7d10d2df0905220318w3e69e112v42eee46b88d9f284@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Frank Joerdens wrote:
> On Fri, May 22, 2009 at 10:56 AM, Richard Huxton <dev@archonet.com> wrote:
> [...]
>> Are you sure it wouldn't be easier to hire a Python guru for a couple of
>> days and have him/her hack the ORM to make it less, um, "simplistic"?
> 
> Not sure. :) Your arguments make eminent sense to me. I am not exactly
> a fan of ORMs, they make my job much harder ... but there seems to be
> no avoiding them these days.

I either like:
1. Really simple, clean ORM but makes it simple to override with custom 
SQL when you need to.
2. Very clever, sophisticated ORM but makes it simple to override with 
custom SQL when you need to.

Unfortunately I'm not a Python guy so I can't comment on Django's ORM.

-- 
   Richard Huxton
   Archonet Ltd