> 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'
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
>> quer
Jay Thorne writes:
>
> Okay, now I need an example. I've never seen a query on any db where a single
> table query was slower than a two table join. Of course, I'm biased here,
> since my knowledge of the more bizarre db's is limited. I've only seen things
> like sybase, oracle, mysql, po
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.
Please, please, please KILL THIS THREAD!
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
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 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.
Act
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.
+Rem
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
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 ba
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
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 http://www.phpbuild
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? No
14 matches
Mail list logo
