Re: [Q] optmizing postgres for 'single client' / many small queries

From: William Temperley <willtemperley(at)gmail(dot)com>
To: pgsql-general(at)postgresql(dot)org
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Subject: Re: [Q] optmizing postgres for 'single client' / many small queries
Date: 2009-09-04 18:08:58
Message-ID: 439dc11e0909041108o436ed3dctc462cc3798f0645e@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
> Just out of curiosity, does anyone know of any ORM anywhere that doesn't
> suck? They seem to be uniformly awful, at least in terms of their
> interfaces to SQL databases. If there were some we could recommend,
> maybe people would be less stuck with these bogus legacy architectures.

I personally like sqlalchemy - http://www.sqlalchemy.org/.

Some of the good things:
1. Table reflection, i.e. dynamic generation of mapped python classes
- great at development time - no mismatch between db and client side
code.
2. Easily extensible - about 10 lines of code gives you an interface
to Geos geometries retrieved from PostGIS
3. It seems to be possible to produce arbitrarily complex sql
statements. OK, they're usually less readable than sql, but for
dynamic query generation it definitely beats manually chopping up
text.

Cheers, Will T

Browse pgsql-general by date

  From Date Subject
Next Message Dimitri Fontaine 2009-09-04 19:34:31 Re: strange error occurs when adding index
Previous Message Tom Lane 2009-09-04 17:33:06 Re: pg_ctl with unix domain socket?