hi,
Is there any issue with using modperl with postgres vs mysql
for a database driven website? Don't want to bark up the wrong
tree in a mod_perl project only to discover I picked the wrong .db :-/
From a licensing perspective which one is less risky if doing some
work for a client?
Quoting dreamwvr [EMAIL PROTECTED] [Mar 21, 2002 13:10]:
Is there any issue with using modperl with postgres vs mysql
for a database driven website? Don't want to bark up the wrong
tree in a mod_perl project only to discover I picked the wrong
.db :-/
Take a look at
darren chamberlain [EMAIL PROTECTED] writes:
Quoting dreamwvr [EMAIL PROTECTED] [Mar 21, 2002 13:10]:
Is there any issue with using modperl with postgres vs mysql
for a database driven website? Don't want to bark up the wrong
tree in a mod_perl project only to discover I picked the wrong
Quoting Dave Hodgkinson [EMAIL PROTECTED] [Mar 21, 2002 13:25]:
darren chamberlain [EMAIL PROTECTED] writes:
Quoting dreamwvr [EMAIL PROTECTED] [Mar 21, 2002 13:10]:
Is there any issue with using modperl with postgres vs mysql
for a database driven website? Don't want to bark up the
On March 21, 2002 10:37 am, darren chamberlain wrote:
Quoting Dave Hodgkinson [EMAIL PROTECTED] [Mar 21, 2002 13:25]:
darren chamberlain [EMAIL PROTECTED] writes:
Quoting dreamwvr [EMAIL PROTECTED] [Mar 21, 2002 13:10]:
Is there any issue with using modperl with postgres vs mysql
Postgres: +More relational? So they say. More features perhaps.
+stored procedures - ie. you can make query wrapping methods
-pain the rear postgres user permissions to control.
+been doing complex sql queries (subselects etc,)
for longer.
On Thu, 21 Mar 2002, Jay Thorne wrote:
The first one I noted was that he assumes that a high performance app has
several joins. I think everyone here who's developed a few db apps will tell
you that joins are hugely costly and should be avoided for an application's
most common cases.
On Thu, 21 Mar 2002, Rafiq Ismail (ADMIN) wrote:
Mysql:+we all start with it.
+Bench marks much faster.
+/-Can allow nested queries (subselects again) though this is a
relatively new feature.
Eh? Subselects aren't scheduled for implementation until 4.1. The
On March 21, 2002 01:05 pm, Dave Rolsky wrote:
On Thu, 21 Mar 2002, Jay Thorne wrote:
The first one I noted was that he assumes that a high performance app has
several joins. I think everyone here who's developed a few db apps will
tell you that joins are hugely costly and should be
Please, please, please KILL THIS THREAD!
Hi all,
On Thu, 21 Mar 2002, Perrin Harkins wrote:
Please, please, please KILL THIS THREAD!
I second that. It's all been done before guys.
73,
Ged.
On Thursday, March 21, 2002, at 01:05 PM, Dave Rolsky wrote:
Further on, he was discussing threaded discussion forums and assumed a
recursive query. While recursing the DATA is probably (though
provabably not
always) necessary, there is no need to storm the db with that many
queries,
Is there any issue with using modperl with postgres vs mysql
for a database driven website? Don't want to bark up the wrong
tree in a mod_perl project only to discover I picked the wrong .db :-/
http://www.mysql.com/news/article-91.html
This was an interesting article, even though it didn't
13 matches
Mail list logo
