From: Chris Browne <cbbrowne@acm.org>
To: pgsql-performance@postgresql.org
Subject: Re: Decide between Postgresql and Mysql (help of
Date: Thu, 30 Mar 2006 17:53:08 -0500
Message-ID: <60mzf7pmsr.fsf@dba2.int.libertyrms.com> (raw)
References: <1143559902.1241.16.camel@servidor>
<op.s642dpyecigqcu@apollo13>
<1143575445.3625.87.camel@state.g2switchworks.com>
<200603291901.59320.listsubscriptions@oghma.on.ca>
<442B4138.8030207@modgraph-usa.com>
<60acb7rgnr.fsf@dba2.int.libertyrms.com>
<1143746489.26940.34.camel@state.g2switchworks.com>
smarlowe@g2switchworks.com (Scott Marlowe) writes:
> And that, nowadays, is generally the state of web development. It's
> not the language you're using to write it in, it's how efficiently
> you're using your database.
Which properly puts my comments in their place :-).
More importantly, that seems like a valid statement which has a *wide*
scope of effects and side-effects. Including some that ought to put
PostgreSQL in a very good place, in that it provides some very good
ways of achieving high efficiency.
Neat performance thing du jour: Hibernate seems to be the "neat new
Java persistence thing."
I have been very unimpressed with some of the web frameworks I have
seen thus far in their interaction with databases.
We use RT (Request Tracker) for tracking tickets, and in its attempt
to be "database agnostic," it actually only achieves being
MySQL(tm)-specific, because they have an automated query generator
that is only good at one style of queries at a time. Coworkers have
suggested improved queries that are (on occasion) hundreds or
thousands of times faster than what it generates; those improvements
fall on deaf ears because they wouldn't work with all the databases.
(Well, more precisely, they wouldn't work with MySQL(tm).)
There's a home grown flavor of Java persistence mapping; it doesn't
seem as heinous as RT's, but it still doesn't make it overly
convenient to replace poor queries with more efficient ones.
Hibernate has a nifty thing in the form of "Named Queries." It'll
often use its own "HQL" to auto-generate SQL, but any time the DBAs
come up with something that's nicely tuned, it seems to be highly
recommended to generate a "Named Query" for that which allows a Nice
Query to be made part of the application without too much weeping and
gnashing of teeth on either DBA or developers' sides.
A framework that allows you to thereby "soup up" how efficiently you
use your database... Hmm... I wonder if that fits into anyone's
notable quote? :-).
--
(format nil "~S@~S" "cbbrowne" "acm.org")
http://www3.sympatico.ca/cbbrowne/lisp.html
"When I was a boy of fourteen, my father was so ignorant I could
hardly stand to have the old man around. But when I got to be
twenty-one, I was astonished at how much the old man had learned in
seven years." -- Mark Twain
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: cbbrowne@acm.org
Subject: Re: Decide between Postgresql and Mysql (help of
In-Reply-To: <60mzf7pmsr.fsf@dba2.int.libertyrms.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox