MySQL commercial licence
Folks, We have a commercial product that uses mysql 4.0.24. We bought a commercial licence for this version. We want to upgrade to 5.0.21. I spoke with the MySQL saleswoman this morning and she says they don't do upgrades and want another entire licence fee for v5.x. Does anyone else have experience of this? Upgrading commercial licences? What's the story? Thanks - Adam -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
RE: MySQL commercial licence
Checking. I don't think the customer bought the "network" version. Apparently its MySQL Pro Licence V4. It's a bit rich not to offer upgrades at a discount IMO. Adam -Original Message- From: David Logan [mailto:[EMAIL PROTECTED] Sent: 12 May 2006 11:52 To: Adam Lipscombe Cc: 'MySQL List' Subject: Re: MySQL commercial licence Adam Lipscombe wrote: >Folks, > > >We have a commercial product that uses mysql 4.0.24. We bought a >commercial licence for this version. We want to upgrade to 5.0.21. > >I spoke with the MySQL saleswoman this morning and she says they don't >do upgrades and want another entire licence fee for v5.x. > > >Does anyone else have experience of this? Upgrading commercial >licences? What's the story? > > >Thanks - Adam > > > > Hi Adam, That is a very interesting development. Is your license under the MySQL Network? I am considering using this for a number of new servers and would have to rethink my strategy if this is the case. I notice their Network FAQ has Q: Does MySQL Network include MySQL 5.0? A: Yes, MySQL Network includes all updates and upgrades including MySQL 5.0 It is also very interesting that the Network product automatically includes a GPL covered product rather than a commercial one by default. How many people actually check on that before purchase? Are they aware they have purchased a GPL product and are now obligated under that license to GPL their distributed products? Regards -- David Logan South Australia when in trouble, or in doubt run in circles, scream and shout -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Drop Index if Exists
Folks, Does this work in MYSQL 5? I tried "DROP INDEX [NAME] IF EXISTS;" and got an error "check your syntax". Thanks - Adam -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Drop Index if Exists
Thanks What I am getting at is: does the "IF EXISTS" qualifier work in this context? I have an index that is present in some DB's but not in others. I want to run a generic script to upgrade them all. I don't want the script to stop if the index is not present. Thanks - Adam Visolve DB TEAM wrote: Hello Adam,This is the exact syntax to drop the index.DROP INDEX index_name ON tbl_nameThanksVisolve DB Team . -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
backwards compatibility when exporting M
Folks I am trialling MySQL 5 before we all upgrade, however others need to import my dump files into their existing MySQL4.x databases MySQL 5 mysqldump seems exports BIT fields as true = '', false = '\0'. When that dump file is imported into MySQL 4 these value are not interpreted correctly. MySQL4.x does not have a real BIT type , rather it uses TINYINT(1). Both '' and '\0' seem to be interpreted as "false", and the relevant TINYINT(1) field is set to 0. So far that has meant that I have to hand-edit my dump file to convert '' to 1, '\0' to 0. Does anyone know a way around this? TIA - Adam Lipscombe -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Mysqldump line endings
Folks By default mysqldump uses linefeed as the line ending. This results in the data looking odd in a Windows text editor, as they expect \r\n. I have experimented with the --tab and --line-terminated-by options, but this results in a separate txt file for each table. Is there any way to persuade mysqldump to produce one file (with "insert into" statements) and also use Windows style line endings? TIA - Adam -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Mysqldump INSERT statements (Was Mysqldump line endings)
>> (--result-file) option to save your output but use the > output redirector >> to map the output of mysqldump to a file you specify, you will get the >>CRLF line endings you seek. Many thanks. One more thing: by default mysqldump uses --extended-insert=TRUE. This results in all the VALUES data being on one line. IF the table has much data this produces very long lines when viewed in a text editor. (WordPad crashes!) If --extended-insert=FALSE then multiple INSERT statements are used. IS there any way to have 1 INSERT statement with each subsequent data line on a separate line? E.g. : INSERT INTO t1 VALUES (1,2,3), (1,4,5), (1,6,7); TIA - Adam -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Problems with importing the british pound (£) an d euro (€) sign
Folks, I have a mysql 5.0 db with the following char sets: mysql> show variables like '%char%'; +--+--+ | Variable_name| Value| +--+--+ | character_set_client | latin1 | | character_set_connection | latin1 | | character_set_database | latin1 | | character_set_results| latin1 | | character_set_server | latin1 | | character_set_system | utf8 | | character_sets_dir | C:\MySQL\share\charsets\ | +--+--+ I have a column that stores currency symbols - two of which are the British pound (£) and euro (€) sign. I can I export via mysqldump no with problem - the "£" sign appears in the export file OK, although the euro is converted into an odd looking set of chars But when I import using the command line client like this: "mysql -u -p < datadump.sql", the £ sign and euro sign get changed into "£" and "€" respectively. I have tried forcing the encoding by using "mysql --default-character-set=latin1 -u -p < datadump.sql" but this produces the same results. Any ideas? TIA - Adam -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
how to "drop index if exists"
Folks How can one conditionally drop an index in MySQL? Googling shows that the "drop index" does not support an "if exists" qualifier - apparently a bug has been raised but as far as I know its not fixed yet. Does anyone know of a work-around? TIA - Adam -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: how to "drop index if exists"
Fantastic, thanks very much! Adam Rob Wultsch wrote: On Nov 29, 2007 4:34 AM, Adam Lipscombe <[EMAIL PROTECTED]> wrote: Folks How can one conditionally drop an index in MySQL? Googling shows that the "drop index" does not support an "if exists" qualifier - apparently a bug has been raised but as far as I know its not fixed yet. Does anyone know of a work-around? TIA - Adam Sent my first response late at night and not the community... And the response also sucked. DROP INDEX is mapped to ALTER TABLE tbl_name DROP INDEX. ALTER IGNORE TABLE tbl_name DROP INDEX ought to be functionally equivalent to IF EXISTS. What is your goal? -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: how to "drop index if exists"
Sorry I got carried away in my former response. When I tried this, ALTER IGNORE TABLE tbl_name DROP INDEX seems to fail if the index does not exist. The DROP INDEX statement is part of a larger script, what I want is for the script to conue to execute if this index does not exist. e.g. ALTER IGNORE TABLE table_name DROP INDEX index_name; ALTER IGNORE TABLE table_name ADD INDEX UNIQUE index_name(column_1,column_2); Thanks - Ada Rob Wultsch wrote: On Nov 29, 2007 4:34 AM, Adam Lipscombe <[EMAIL PROTECTED]> wrote: Folks How can one conditionally drop an index in MySQL? Googling shows that the "drop index" does not support an "if exists" qualifier - apparently a bug has been raised but as far as I know its not fixed yet. Does anyone know of a work-around? TIA - Adam Sent my first response late at night and not the community... And the response also sucked. DROP INDEX is mapped to ALTER TABLE tbl_name DROP INDEX. ALTER IGNORE TABLE tbl_name DROP INDEX ought to be functionally equivalent to IF EXISTS. What is your goal? -- Adam Lipscombe T: 01872 575083 M: 07957 548686 E: [EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
How to set trabnsaction isoloation in my.ini file
I have MySql 4.1.12 installed on an XP box in C:\mysql. I have the settings below in my C;\MySql\my.ini file: I have the transaction-isolation set to READ-COMMITTED but the server seems to ignore this. When the server starts up the tx_isolation as reported by mysqladmin extended-status is REPEATABLE-READ. I can set it manually from the mysql command line and that works. The tx_isolation is then reported as READ-COMMITTED. Its almost as if the server is not reading the my.ini file. How can I set the tx isolation level on startup? Does anyone have any ideas? Thanks -Adam [mysqld] # The TCP/IP Port the MySQL Server will listen on port=3306 #Path to installation directory. All paths are usually resolved relative to this. basedir="C:/MySQL/" #Path to the database root datadir="C:/MySQL/Data/" # The default character set that will be used when a new schema or table is # created and no character set is defined default-character-set=latin1 # The default storage engine that will be used when create new tables when default-storage-engine=INNODB # The maximum amount of concurrent sessions the MySQL server will # allow. One of these connections will be reserved for a user with # SUPER privileges to allow the administrator to login even if the # connection limit has been reached. max_connections=100 # Query cache is used to cache SELECT results and later return them # without actual executing the same query once again. Having the query # cache enabled may result in significant speed improvements, if your # have a lot of identical queries and rarely changing tables. See the # "Qcache_lowmem_prunes" status variable to check if the current value # is high enough for your load. # Note: In case your tables change very often or if your queries are # textually different every time, the query cache may result in a # slowdown instead of a performance improvement. query_cache_size=0 # The number of open tables for all threads. Increasing this value # increases the number of file descriptors that mysqld requires. # Therefore you have to make sure to set the amount of open files # allowed to at least 4096 in the variable "open-files-limit" in # section [mysqld_safe] table_cache=256 # Maximum size for internal (in-memory) temporary tables. If a table # grows larger than this value, it is automatically converted to disk # based table This limitation is for a single table. There can be many # of them. tmp_table_size=13M # How many threads we should keep in a cache for reuse. When a client # disconnects, the client's threads are put in the cache if there aren't # more than thread_cache_size threads from before. This greatly reduces # the amount of thread creations needed if you have a lot of new # connections. (Normally this doesn't give a notable performance # improvement if you have a good thread implementation.) thread_cache_size=8 #*** MyISAM Specific options # The maximum size of the temporary file MySQL is allowed to use while # recreating the index (during REPAIR, ALTER TABLE or LOAD DATA INFILE. # If the file-size would be bigger than this, the index will be created # through the key cache (which is slower). myisam_max_sort_file_size=100G # If the temporary file used for fast index creation would be bigger # than using the key cache by the amount specified here, then prefer the # key cache method. This is mainly used to force long character keys in # large tables to use the slower key cache method to create the index. myisam_max_extra_sort_file_size=100G # If the temporary file used for fast index creation would be bigger # than using the key cache by the amount specified here, then prefer the # key cache method. This is mainly used to force long character keys in # large tables to use the slower key cache method to create the index. myisam_sort_buffer_size=26M # Size of the Key Buffer, used to cache index blocks for MyISAM tables. # Do not set it larger than 30% of your available memory, as some memory # is also required by the OS to cache rows. Even if you're not using # MyISAM tables, you should still set it to 8-64M as it will also be # used for internal temporary disk tables. key_buffer_size=8M # Size of the buffer used for doing full table scans of MyISAM tables. # Allocated per thread, if a full scan is needed. read_buffer_size=64K read_rnd_buffer_size=256K # This buffer is allocated when MySQL needs to rebuild the index in # REPAIR, OPTIMZE, ALTER table statements as well as in LOAD DATA INFILE # into an empty table. It is allocated per thread so be careful with # large settings. sort_buffer_size=256K #*** INNODB Specific options *** # Use this option if you have a MySQL server with InnoDB support enabled # but you do not plan to use it. This will save memory and disk space # and speed up some things. #skip-innodb # Additional memory pool that is used by InnoDB to store metadata # information. If InnoDB requires more memory for this purpose it will # start to allocate it from
RE: How to set trabnsaction isoloation in my.ini file
>> It may not be. Do you specify this file when you start the server on >> the command line? If you don't then you need to move my.ini to the >>windows directory: You are quite right. When I moved the my.ini file to c:\windows it worked. I assumed that it would work 'cos the mySQL installer created the file in the installation dir. Many thanks - Adam -Original Message- From: Kristen G. Thorson [mailto:[EMAIL PROTECTED] Sent: 17 May 2005 17:23 To: Adam Lipscombe Cc: mysql@lists.mysql.com Subject: Re: How to set trabnsaction isoloation in my.ini file Adam Lipscombe wrote: >I have MySql 4.1.12 installed on an XP box in C:\mysql. > >I have the settings below in my C;\MySql\my.ini file: > >I have the transaction-isolation set to READ-COMMITTED but the server >seems to ignore this. When the server starts up the tx_isolation as >reported by mysqladmin extended-status is REPEATABLE-READ. > >I can set it manually from the mysql command line and that works. The >tx_isolation is then reported as READ-COMMITTED. > > >Its almost as if the server is not reading the my.ini file. > > > It may not be. Do you specify this file when you start the server on the command line? If you don't then you need to move my.ini to the windows directory: "When the MySQL server starts on Windows, it looks for options in two files: the `my.ini' file in the Windows directory, and the `C:\my.cnf' file. The Windows directory typically is named something like `C:\WINDOWS' or `C:\WinNT'. You can determine its exact location from the value of the |WINDIR| environment variable using the following command: C:\> echo %WINDIR% MySQL looks for options first in the `my.ini' file, then in the `my.cnf' file. However, to avoid confusion, it's best if you use only one file. If your PC uses a boot loader where the |C:| drive isn't the boot drive, your only option is to use the `my.ini' file. Whichever option file you use, it must be a plain text file." -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
