-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Monday 25 November 2002 15:03, Dyego Souza do Carmo wrote:
> ohhh, i´m sorry , the licences i was confused about are:
>
> MySQL-Standard and MySQL-Pro , not mysql-classic ;)
>
> What are the deferences between mysql-standard and mysql-pro ?
Well,
>> The licence in mysql page is "obscure" for version 4.0
>>
>> What is a diference of MySQL-Classic and MySQL-Pro ?
LG> The only difference between those two is InnoDB - MySQL-Classic does not
LG> include it, while MySQL-Pro does. Both products are available under a
LG> commercial (non-GPL) lic
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Monday 25 November 2002 13:53, Dyego Souza do Carmo wrote:
> The licence in mysql page is "obscure" for version 4.0
>
> What is a diference of MySQL-Classic and MySQL-Pro ?
The only difference between those two is InnoDB - MySQL-Classic does not
The licence in mysql page is "obscure" for version 4.0
What is a diference of MySQL-Classic and MySQL-Pro ?
When may i use MySQL-Classic ?
When may i use MySQL-Pro ?
My Application is a commercial multi-database , running in mysql and
interbase , in my case , witch these licenceses must i use
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Monday 18 November 2002 16:46, Dyego Souza do Carmo wrote:
> MySQL Classic (Commercial License)
> Similar to MySQL Standard, but *without* InnoDB and only available as a
> commercial licensed version.
>
> MySQL Pro (Commercial)
> Similar to MySQL S
MySQL Classic (Commercial License)
Similar to MySQL Standard, but *without* InnoDB and only available as a commercial
licensed version.
MySQL Pro (Commercial)
Similar to MySQL Standard (*including* InnoDB), but only available as a commercial
licensed version.
What is the diference in (Comm
