Performance is really the bottom line for us. Would you like to qualify your opinion further, using that
as the criteria?

-----Original Message-----
From: Bo Lorentsen [mailto:bl@netgroup.dk]
Sent: Thu 2/17/2005 2:22 AM
To: Van Ingen, Lane
Cc: pgsql-novice@postgresql.org
Subject: Re: [NOVICE] Front End Languages for PostgreSQL



Van Ingen, Lane wrote:

>Does anybody have any solid information that says that one language is better as a front end to a PostgreSQL database over another, and why ?
>
I think this has more to do with the demands of the language, I have
used it with both PHP, Python and C++. I prefer python (mod_python for
apache) and C++ but this has nothing to do with the postgresql binding,
but a lot about the language.

>We are coming out of a PHP / MySQL environment, have adopted PostgreSQL, and are trying to decide which
>language would be best to use with PostgreSQL. Since the application has to be rewritten, we are considering lanuages like PHP and Java. The application is web-based.
>
>
Hmm, I think the DB (binding) is of no relevance regarding choice of
language. The software model you are (planning to) using are more
relevant, like : will you need a OO class model, and do you prefer
exceptions for future error handling. The last thing to consider is the
performance demands, but the DB binding has nothing to do with this.

Hope this helps ...

/BL



---------------------------(end of broadcast)---------------------------
TIP 4: Don't 'kill -9' the postmaster

Van Ingen, Lane wrote:

>Performance is really the bottom line for us. Would you like to qualify your opinion further, using that
>as the criteria?
>
>
Performance in general, is a really big issue :-)

But in this case, when we look at a programming language and its DB
connectivity, we need to chose languages depending on the amount and
type of work done while _processing_, not by the DB binding. The only
performance issue in relation to a language binding are related to
support for special DB features, but on the other side ... most DB API's
are made as open source, and missing features can be added relativly
easy (sometimes by just asking nicely) :-)

So, what kind of performance are you working for ? Fast DB access,
applicaiton modularity (OO), quick app. execution, concurrency execution
(multi user on a webside) ? These things You need to deside, and then
You know what to optimize for good performance.

Hope this is not too confusing :-)

/BL

---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo@postgresql.org so that your
message can get through to the mailing list cleanly