Re: mysql.org (comments to old messages)

2001-07-17 Thread Van

Monty:

You started MySQL as a database server derived from msql several years ago, and,
you made it quick.  You made it a bunch of other things, but, what's most
important is that you made it quick.  You made it stable.  Quick is good. 
Stable is better.  When both are paired, it's a pure win.  This is YOUR
contribution.  Your development and any assistance you got from the community
and crew.  Take credit.  It's yours.  We might have given suggestions, but, you
wrote the code.  We use it.  And, we love how it works.

isam, mysam, gemini, bdb, etc., table implementations are meaningless unless we
know what is behind it.

What's useful to me is that I can start a new application using the same db
engine I've used for 5 years and not have to worry that it's going to corrupt my
data.  I know the interfaces, and, the new features I can use.  ISAM is fine, or
MySAM.  I'll program on the front.  I love stability.

What is Gemini?  And, what will it do for my clients that MySQL hasn't done for
the past 5 years using ISAM, or MySAM?  Put that on the NuSphere.Org site
(whoops; mysql.org site).  I don't care.  My clients want stability and speed
and a development community they can trust and who's track record they can
check.  They already have it.  That's how you, Sinisa, David, and crew (MySQL
AB) put this stuff together.  That's why we all stuck around.  Because it's
great stuff and we've built useful, stable, quick applications using it.  And,
you and Sinisa are always here.  I don't know how you do it.  Perhaps, because
you know it has a credible future.

I'd hope Progress could see the light.

Best Regards,
Van

 Regards,
 Monty
 
 PS: Thanks for all support. If anyone thinks I am unfair in any of the
 comments above, feel free to write privately to me about this and
 I will try to correct myself in future postings.  It's quite hard
 to keep ones temper in check when one is burning with passion to
 defend oneself and the thing one has been part of creating.
 
 -
 Before posting, please check:
http://www.mysql.com/manual.php   (the manual)
http://lists.mysql.com/   (the list archive)
 
 To request this thread, e-mail [EMAIL PROTECTED]
 To unsubscribe, e-mail [EMAIL PROTECTED]
 Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

-- 
=
Linux rocks!!!   http://www.dedserius.com/
=

-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail [EMAIL PROTECTED]
To unsubscribe, e-mail [EMAIL PROTECTED]
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php




RE: mysql.org (comments to old messages)

2001-07-17 Thread Simon Green


http://www.nusphere.org
Is available to register but I don't now why you would what to ;o).?

Simon 

-Original Message-
From: Van [mailto:[EMAIL PROTECTED]]
Sent: 17 July 2001 10:36
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: mysql.org (comments to old messages)


Monty:

You started MySQL as a database server derived from msql several years ago,
and,
you made it quick.  You made it a bunch of other things, but, what's most
important is that you made it quick.  You made it stable.  Quick is good. 
Stable is better.  When both are paired, it's a pure win.  This is YOUR
contribution.  Your development and any assistance you got from the
community
and crew.  Take credit.  It's yours.  We might have given suggestions, but,
you
wrote the code.  We use it.  And, we love how it works.

isam, mysam, gemini, bdb, etc., table implementations are meaningless unless
we
know what is behind it.

What's useful to me is that I can start a new application using the same db
engine I've used for 5 years and not have to worry that it's going to
corrupt my
data.  I know the interfaces, and, the new features I can use.  ISAM is
fine, or
MySAM.  I'll program on the front.  I love stability.

What is Gemini?  And, what will it do for my clients that MySQL hasn't done
for
the past 5 years using ISAM, or MySAM?  Put that on the NuSphere.Org site
(whoops; mysql.org site).  I don't care.  My clients want stability and
speed
and a development community they can trust and who's track record they can
check.  They already have it.  That's how you, Sinisa, David, and crew
(MySQL
AB) put this stuff together.  That's why we all stuck around.  Because it's
great stuff and we've built useful, stable, quick applications using it.
And,
you and Sinisa are always here.  I don't know how you do it.  Perhaps,
because
you know it has a credible future.

I'd hope Progress could see the light.

Best Regards,
Van

 Regards,
 Monty
 
 PS: Thanks for all support. If anyone thinks I am unfair in any of the
 comments above, feel free to write privately to me about this and
 I will try to correct myself in future postings.  It's quite hard
 to keep ones temper in check when one is burning with passion to
 defend oneself and the thing one has been part of creating.
 
 -
 Before posting, please check:
http://www.mysql.com/manual.php   (the manual)
http://lists.mysql.com/   (the list archive)
 
 To request this thread, e-mail [EMAIL PROTECTED]
 To unsubscribe, e-mail
[EMAIL PROTECTED]
 Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

-- 
=
Linux rocks!!!   http://www.dedserius.com/
=

-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail [EMAIL PROTECTED]
To unsubscribe, e-mail
[EMAIL PROTECTED]
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail [EMAIL PROTECTED]
To unsubscribe, e-mail [EMAIL PROTECTED]
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php




mysql.org (comments to old messages)

2001-07-16 Thread Michael Widenius


Hi!

I am now finally back from Australia after a 36 hour, which involved 4
hours waiting for a airplane to be repaired, 3 plane changes and one
missed airplane.  Finally back in Finland, we got the message that our
baggage had been lost on the way :(

Australia was great, but it's real nice to be back home.

I am in this email trying to shortly comment on the questions that have
been left unanswered, in an attempt to ensure that everyone
understands my standpoint in this case.

Those that are already fed up with this discussion, please go back to
your usual business of tuning MySQL, filing bug reports or helping
other users on the MySQL email lists.  Those that want a little more
background information are free to continue.

From: Thomas J Keller [EMAIL PROTECTED] forwarded email from Britt
Johnson:

Britt Your comments about us not participating in any meaninful fashion
Britt in the open source community are disappointing because it means
Britt NuSphere has not done a good job communicating its work, I believe 
Britt we provide a significant service and have allowed many people who
Britt otherwise could not use open source software to use it because of
Britt our work on improving windows ports, integration of components,
Britt and major features.  We contribute back fixes and improvements to
Britt many open source communities including apache, perl, php and mysql.
Britt Much of that work is available at no cost through downloads at our
Britt website.  I'd invite you to download and try NuSphere MySQL and 
Britt see an example of what we have done.

I found the above statement by Britt confusing.  It's hard to say
what NuSphere has been doing and not done.

Apart from the crypt function, which I couldn't include in MySQL, and
some small changes required to get Gemini to work within MySQL, I
can't just now remember any patches or changes that NuSphere has
contributed to the MySQL server. If there has been any other code
contributions, they have been minor and infrequent.

Britt The importance of our investment is reflected in Monty's own words:
Britt NuSphere has identified a very important technical enhancement 
Britt needed to transform MySQL into an enterprise-enabled database capable 
Britt of competing with commercial heavyweights, said Michael Monty 
Britt Widenius, chief technology officer of MySQL AB. In MySQL's five-year 
Britt history, this is the most significant contribution from a source 
Britt outside MySQL AB that has ever occurred.

This is an interesting item (at least for me). The background was that
NuSphere said they would release Gemini in January 2001 and wanted to
get some publicity out of this.  NuSphere emailed me the above text
and asked if I could put approve the above text for their press
release where they would announce Gemini.  We at MySQL wanted (at that
time) to support them, so we said they could go ahead with the press
release, but they had to some changes, which involved changing 'THE
most' to 'one of the most' or 'a most significant'.

Another thing is also that while NuSphere delayed the release of
Gemini because of their own reasons, Heikki Tuuri at Innobase got
interested in MySQL.  His table handler, InnoDB, which has been
included in the MySQL source releases since 3.23.34, is an as
important contribution as Gemini.

cut

Britt As we said last January, we planned on Gemini being released
Britt under an open source license as part of the launch of MySQL 4.0,
Britt but that release has not shipped so we have decided to release
Britt the source through mysql.org instead soon after its launch (the
Britt community needs to setup CVS to support that effort).  Note that 
Britt Gemini has both commercial and open source licenses just like 
Britt MySQL itself and the products we are currently shipping are 
Britt provided with a commercial license of Gemini.  We absolutely
Britt believe we have the right to do this.

We offered NuSphere to be included into the MySQL 3.23 release, just
like BDB and InnoDB, but NuSphere was not interested.

Britt seams to have missed to inform you here about one basic flaw in
the above argument.

The reason we at MySQL can provide MySQL under an open source and a
commercial license is that the we have the copyright to all the GPL
MySQL server code except Berkeley DB (which is not really GPL, but has
a strict copyright), Gemini and InnoDB. This gives us the right to
release the code under a standard commercial license, as long as we
don't include any of the above components, without an approval from
the copyright holders, into this release.  We do have such agreements
with InnoDB and and understanding of how to do this with the Berkeley
DB people.

NuSphere has the same benefit. They can release Gemini without MySQL
under a commercial license. They can't not release Gemini with MySQL
under any not GPL compatible license.

The above statement by Britt is a clear violation of the GPL license.

http://www.gnu.org/copyleft/gpl-faq.html

The