Marco Colombo wrote:
If want to develop a commercial application that:
- runs under Linux - I can;
- uses HTTP as protocol, and connects to a GPL-ed web server - I can;
- uses MySQL as a database backend - I can't, unless I rewrite the
client library, or buy a commercial licence from them. Why?
W
On Tue, 8 Mar 2005, Scott Marlowe wrote:
On Tue, 2005-03-08 at 09:06, Shelby Cain wrote:
--- Howard Cole <[EMAIL PROTECTED]> wrote:
Although not appropriate for a speed comparison, you
might want to note
that the use of Mysql versions 4.0 upward now
require commercial license
for clients, which are
Scott Marlowe wrote:
On Tue, 2005-03-08 at 09:06, Shelby Cain wrote:
--- Howard Cole <[EMAIL PROTECTED]> wrote:
Although not appropriate for a speed comparison, you
might want to note
that the use of Mysql versions 4.0 upward now
require commercial license
for clients, which are no longer
This will not answer you question, but documents some of the evidence
for you:
http://www.geocities.com/mailsoftware42/db/
Rick Casey, Research Associate
Institute for Behavioral Genetics
[EMAIL PROTECTED]
303.735.3518
Rick Schumeyer wrote:
I’m interested in comparing the performance of postgres
Scott Marlowe <[EMAIL PROTECTED]> writes:
> However, Fedora Core 2 still includes MySQL V 3.xx.yy because of the
> issues wth V4.xx.yy's licensing. However, Suse does include the latest
> version. So there's some difference of opinion on the issue from
> different distros.
Not any more --- it's
On Tue, 2005-03-08 at 09:06, Shelby Cain wrote:
> --- Howard Cole <[EMAIL PROTECTED]> wrote:
> >
> > Although not appropriate for a speed comparison, you
> > might want to note
> > that the use of Mysql versions 4.0 upward now
> > require commercial license
> > for clients, which are no longer L
--- Howard Cole <[EMAIL PROTECTED]> wrote:
>
> Although not appropriate for a speed comparison, you
> might want to note
> that the use of Mysql versions 4.0 upward now
> require commercial license
> for clients, which are no longer LGPL, whereas
> Postgres is free (BSD
> license). This makes
You may want to consider other things...
MySQL adds complexity in that it has several database engines: MyISAM,
InnoDB and MAXDB. All of which have different performance
characteristics. MyISAM is very fast for databases with few
transactions, but InnoDB is more comparable to Postgres in that it
On Mon, 2005-03-07 at 13:35 -0600, Scott Marlowe wrote:
> Tune both reasonably according the the best practices for each database.
>
Also, you should consult people on the MySQL lists to make sure it's
being tuned properly as well. And make sure both databases have access
to the same hardware res
On Mon, 2005-03-07 at 12:00, Rick Schumeyer wrote:
> Iâm interested in comparing the performance of postgresql and mysql
>
> on various combinations of user loads and database sizes. I have seen
>
> a few statements to the effect of âmysql is faster for small, low use
>
> applications, but post
Rick Schumeyer wrote:
I'm interested in comparing the performance of postgresql and mysql
on various combinations of user loads and database sizes. I have seen
a few statements to the effect of "mysql is faster for small, low use
applications, but postgresql is better for bigger stuff". I would l
I’m interested in comparing the performance of postgresql
and mysql
on various combinations of user loads and database sizes.
I have seen
a few statements to the effect of “mysql is faster for
small, low use
applications, but postgresql is better for bigger stuff”.
I would like
to run
12 matches
Mail list logo
