Benetl, a free ETL tool for MySQL, out in version 4.9
Dear all, Benetl, a free ETL tool for MySQL, is out in version 4.9. This new version is providing some code optimizations, tests coverage improvement. This version supports Java 1.8 and providesone bug correction (dist function now returns result as double type). You should really update. Benetl is freely dowloadable at:https://www.benetl.net You can learn more about ETL tools at: http://en.wikipedia.org/wiki/Extract,_transform,_load Thanks for your interest. Regards, -- Benoît Carpentier https://www.benetl.net Founder of Benetl and Java project manager
ANN: Stored routine debugger Hopper, version 2.0.1 released
Dear ladies and gentlemen, Upscene Productions is proud to announce version 2.0.1 of "Hopper", a stored routine debugger for InterBase, Firebird and MySQL. Major version 2 has a fully renewed user interface, support for Firebird 3 packages, stored functions, MySQL diagnostic-statements, binary data in variables and much more. For more information, see http://www.upscene.com/go/?go=news=20180627 With regards, Martijn Tonies Upscene Productions http://www.upscene.com
ANN: Stored routine debugger Hopper, version 2.0 released
Dear ladies and gentlemen, Upscene Productions is proud to announce version 2 of "Hopper", a stored routine debugger for InterBase, Firebird and MySQL. This version includes support for Firebird 3 packages and stored functions, MySQL diagnostic-statements, binary data in variables and much more. For more information, check the Hopper page on this website. http://www.upscene.com/stored_procedure_debugger/ About Hopper Hopper is a stored routine debugging tool for MySQL, Firebird and InterBase. If you use stored procedures on these database systems, Hopper will be a great tool for debugging these routines. About Upscene Productions Based in The Netherlands, Europe, this small but dedicated company has been providing database developers with useful tools for over 15 years. Slowly expanding the product portfolio and gaining recognition amongst InterBase and Firebird database developers, they now offer tools for a whole range of database systems, including Oracle and Microsoft SQL Server.
Benetl, a free ETL tool for MySQL, out in version 4.8
Dear all, Benetl, a free ETL tool for MySQL, is out in version 4.8. This new version is providing some code optimizations, tests coverage improvement. This version supports Java 1.8 and providesone bug correction. You should really update. Benetl is freely dowloadable at:http://www.benetl.net You can learn more about ETL tools at: http://en.wikipedia.org/wiki/Extract,_transform,_load Thanks for your interest. Regards, -- Benoît Carpentier http://www.benetl.net Founder of Benetl and Java project manager
Benetl, a free ETL tool for MySQL, out in version 4.7
Dear all, Benetl, a free ETL tool for MySQL, is out in version 4.7. This new version is providing some code optimizations, performance and tests coverage improvement. This version provides also two corrections : - correcting one bug in debug mode. - correcting one bug in logging system. You should really update. Benetl is freely dowloadable at:http://www.benetl.net You can learn more about ETL tools at: http://en.wikipedia.org/wiki/Extract,_transform,_load Thanks for your interest. Regards, -- Benoît Carpentier http://www.benetl.net Founder of Benetl and Java project manager
compile problem with newest version of mysql-server
Hi all,
Recently, I got the newest version of mysql-server from the github,
Bug I got some compile problem as follows:
cmake -DCMAKE_INSTALL_PREFIX=/u04/my3306 \
-DMYSQL_DATADIR=/u04/my3306/data -DMYSQL_USER=mysql \
-DSYSCONFDIR=/etc -DWITH_MYISAM_STORAGE_ENGINE=1 \
-DWITH_INNOBASE_STORAGE_ENGINE=1 \
-DMYSQL_UNIX_ADDR=/u04/my3306/run/mysql.sock \
-DMYSQL_TCP_PORT=3306 -DENABLED_LOCAL_INFILE=1 \
-DWITH_PARTITION_STORAGE_ENGINE=1 -DEXTRA_CHARSETS=all -DDEFAULT_CHARSET=utf8 \
-DDEFAULT_COLLATION=utf8_general_ci -DCMAKE_C_FLAGS_RELWITHDEBINFO="-O2 -g" \
-DCMAKE_CXX_FLAGS_RELWITHDEBINFO="-O2 -g" \
-DCMAKE_C_FLAGS="-O2 -g" -DCMAKE_CXX_FLAGS="-O2 -g" -DWITH_BOOST=/root/
-- Looking for kqueue
-- Looking for kqueue - not found
-- Looking for EVFILT_TIMER
-- Looking for EVFILT_TIMER - not found
CMake Error at configure.cmake:540 (MESSAGE):
No mysys timer support detected!
Call Stack (most recent call first):
CMakeLists.txt:443 (INCLUDE)
-- Configuring incomplete, errors occurred!
See also "/root/mysql/mysql-server-mysql-5.7.8/CMakeFiles/CMakeOutput.log".
See also "/root/mysql/mysql-server-mysql-5.7.8/CMakeFiles/CMakeError.log".
And end of CMakeError.log as follows, and it seems like I had miss event.h file.
/root/mysql/mysql-server-mysql-5.7.8/CMakeFiles/CMakeTmp/CheckSymbolExists.c:3:23:
fatal error: sys/event.h: No such file or directory
#include
^
compilation terminated.
gmake[1]: *** [CMakeFiles/cmTryCompileExec2077689452.dir/CheckSymbolExists.c.o]
Error 1
gmake[1]: Leaving directory
`/root/mysql/mysql-server-mysql-5.7.8/CMakeFiles/CMakeTmp'
gmake: *** [cmTryCompileExec2077689452/fast] Error 2
File
/root/mysql/mysql-server-mysql-5.7.8/CMakeFiles/CMakeTmp/CheckSymbolExists.c:
/* */
#include
#include
#include
int main(int argc, char** argv)
{
(void)argv;
#ifndef EVFILT_TIMER
return ((int*)(_TIMER))[argc];
#else
(void)argc;
return 0;
#endif
}
Can anyone knows how to fix this problem ?
Dacai.
Re: command is not allowed with this MySQL version
- Original Message - From: yoku ts. yoku0...@gmail.com Subject: Re: command is not allowed with this MySQL version Christophe has already told, The used MySQL version is 5.5.40 from Debian Wheezy package. No, that's the new version. It'd be fun to know what the OLD version was, too. Maybe you missed *mysql command-line client's --local-infile option* Not particularly helpful, since Christophe already said it's a PHP application :-) -- Unhappiness is discouraged and will be corrected with kitten pictures. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
[Solved] Re: command is not allowed with this MySQL version
Hi, Le 12/12/2014 11:51, Johan De Meersman a écrit : - Original Message - From: yoku ts. yoku0...@gmail.com Subject: Re: command is not allowed with this MySQL version Christophe has already told, The used MySQL version is 5.5.40 from Debian Wheezy package. No, that's the new version. It'd be fun to know what the OLD version was, too. Absolutely no idea : The app was running on a shared hosting, and don't have access to it ... Maybe you missed *mysql command-line client's --local-infile option* Not particularly helpful, since Christophe already said it's a PHP application :-) Right :) and the solve was in PHP behavior (all seems fine now ...) . The configuration was fine, but to take care of 'local-infile' parameter in PHP configuration (and on Debian) the php5-mysqlnd package must be installed instead of php5-mysql. Hoping this can help someone in the future. Regards. Christophe. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
Re: command is not allowed with this MySQL version
2014/12/12 02:10 +0100, Christophe When the app tries to do this, it raises an error : 'The used command is not allowed with this MySQL version' The used MySQL version is 5.5.40 from Debian Wheezy package. I found that some parameters or variables (local_infile for instance) can be used to get rid of this error, but can't really find the right configuration. Well, yes, if local_infile is 0 or FALSE then 'LOCAL' is forbidden. If 'LOCAL' is not used then the MySQL user needs privilege 'FILE' to read from the server s own disk. What else have you tryed, with what outcome? because the statement as it stands is good MySQL. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
command is not allowed with this MySQL version
Hi there, One of our customers would like to modernize his IT : new servers with new OS, etc. But he got an old fashion PHP/MySQL application that make queries like this : LOAD DATA LOCAL INFILE '/files/tmp_import.csv' IGNORE INTO TABLE users FIELDS TERMINATED BY ';' LINES TERMINATED BY '\n' IGNORE 1 LINES (@dummy, nom, prenom, @dummy, @dummy, email, @dummy, @dummy, @dummy, @dummy, @dummy, @dummy, @dummy, @dummy, @dummy, @dummy, @dummy, @dummy, @dummy, @dummy, @dummy, @dummy,@dummy, @dummy, @dummy, @dummy, @dummy, @dummy, @dummy, @dummy, @dummy, @dummy, @dummy, @dummy, @dummy, @dummy, @dummy, @dummy) When the app tries to do this, it raises an error : 'The used command is not allowed with this MySQL version' The used MySQL version is 5.5.40 from Debian Wheezy package. I found that some parameters or variables (local_infile for instance) can be used to get rid of this error, but can't really find the right configuration. Is there any way to do this ? Thanks and regards. Christophe. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
Re: command is not allowed with this MySQL version
- Original Message - From: Christophe t...@stuxnet.org Subject: command is not allowed with this MySQL version 'The used command is not allowed with this MySQL version' Out of sheer morbid curiosity, what version were they running? -- Unhappiness is discouraged and will be corrected with kitten pictures. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
Re: command is not allowed with this MySQL version
Hi, Christophe has already told, The used MySQL version is 5.5.40 from Debian Wheezy package. Maybe you missed *mysql command-line client's --local-infile option* $ bin/mysql mysql SELECT @@version; ++ | @@version | ++ | 5.5.40-log | ++ 1 row in set (0.00 sec) mysql SELECT @@local_infile; ++ | @@local_infile | ++ | 1 | ++ 1 row in set (0.00 sec) mysql LOAD DATA LOCAL INFILE '/files/tmp_import.csv' INTO TABLE users FIELDS TERMINATED BY ';' LINES TERMINATED BY '\n' IGNORE 1 LINES (@dummy, nom, prenom, @dummy, @dummy, email, @dummy, @dummy, @dummy, @dummy, @dummy, @dummy, @dummy, @dummy, @dummy, @dummy, @dummy, @dummy, @dummy, @dummy, @dummy, @dummy,@dummy, @dummy, @dummy, @dummy, @dummy, @dummy, @dummy, @dummy, @dummy, @dummy, @dummy, @dummy, @dummy, @dummy, @dummy, @dummy); ERROR 1148 (42000): The used command is not allowed with this MySQL version $ bin/mysql --local-infile mysql LOAD DATA LOCAL INFILE '/files/tmp_import.csv' INTO TABLE users FIELDS TERMINATED BY ';' LINES TERMINATED BY '\n' IGNORE 1 LINES (@dummy, nom, prenom, @dummy, @dummy, email, @dummy, @dummy, @dummy, @dummy, @dummy, @dummy, @dummy, @dummy, @dummy, @dummy, @dummy, @dummy, @dummy, @dummy, @dummy, @dummy,@dummy, @dummy, @dummy, @dummy, @dummy, @dummy, @dummy, @dummy, @dummy, @dummy, @dummy, @dummy, @dummy, @dummy, @dummy, @dummy); ERROR 1146 (42S02): Table 'd1.users' doesn't exist Would you try it? yoku0825, 2014-12-12 11:00 GMT+09:00 Johan De Meersman vegiv...@tuxera.be: - Original Message - From: Christophe t...@stuxnet.org Subject: command is not allowed with this MySQL version 'The used command is not allowed with this MySQL version' Out of sheer morbid curiosity, what version were they running? -- Unhappiness is discouraged and will be corrected with kitten pictures. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
Re: How to get all known bugs on specified mysql version?
don't use GTID is my suggestion :) 2014-07-07 7:42 GMT+08:00 娄帅 louis.hust...@gmail.com: Hi, all, I want to use MySQL 5.6.18 in production, so i want to get all known bugs on this version. Now i check the bugfix section in MySQL 5.6.19 and above version. Am i doing the right thing? Or Do you have a better method? Any input will be appreciated! -- Phone: +86 1868061 Email Gtalk: yloui...@gmail.com Personal Blog: http://www.vmcd.org
Re: How to get all known bugs on specified mysql version?
Why do not use GTID? Just curious...WB 2014-07-07 3:18 GMT-03:00 louis liu yloui...@gmail.com: don't use GTID is my suggestion :) 2014-07-07 7:42 GMT+08:00 娄帅 louis.hust...@gmail.com: Hi, all, I want to use MySQL 5.6.18 in production, so i want to get all known bugs on this version. Now i check the bugfix section in MySQL 5.6.19 and above version. Am i doing the right thing? Or Do you have a better method? Any input will be appreciated! -- Phone: +86 1868061 Email Gtalk: yloui...@gmail.com Personal Blog: http://www.vmcd.org
Re: How to get all known bugs on specified mysql version?
Am 07.07.2014 12:37, schrieb wagnerbianchi.com: Why do not use GTID? Just curious...WB just read the changelogs and endless count of bugreports it's a new feature and it works as buggy as replication years ago where you had the rebuild the slave all the time and maybe still if temporary tables and memory tables are part of the game - i had a reason to switch to normal tables with hash-names and remove them finally since that didn't break replication all the time 2014-07-07 3:18 GMT-03:00 louis liu yloui...@gmail.com: don't use GTID is my suggestion :) 2014-07-07 7:42 GMT+08:00 娄帅 louis.hust...@gmail.com: Hi, all, I want to use MySQL 5.6.18 in production, so i want to get all known bugs on this version. Now i check the bugfix section in MySQL 5.6.19 and above version. Am i doing the right thing? Or Do you have a better method? Any input will be appreciated! signature.asc Description: OpenPGP digital signature
Re: How to get all known bugs on specified mysql version?
Hello, On 7/6/2014 7:42 PM, 娄帅 wrote: Hi, all, I want to use MySQL 5.6.18 in production, so i want to get all known bugs on this version. Now i check the bugfix section in MySQL 5.6.19 and above version. Am i doing the right thing? Or Do you have a better method? Any input will be appreciated! The easiest way to see which bugs are pending is to actually search the bugs database, http://bugs.mysql.com Here is one example search you can perform. Note, many of these bugs (such as bug #49728) are low-impact edge-cases that are prioritized lower than other more important high-impact bugs. Our development teams have limited resources. We triage and prioritize what they can work on based on how severe the bug is, how often is may be encountered, and how easy it may be to work around. http://bugs.mysql.com/search.php?search_for=status[]=Activeseverity=limit=Allorder_by=idcmd=displayphpver=5.5os=0os_details=bug_age=0tags=similar=target=last_updated=0defect_class=allworkaround_viability=allimpact=allfix_risk=allfix_effort=alltriageneeded= Anyone can join the fight! Start by submitting an OCA (Oracle Contributor's Agreement). http://www.oracle.com/technetwork/community/oca-486395.html If you have any questions about the OCA, please contact the MySQL community team. http://www.mysql.com/about/contact/?topic=community Then, any patches you provide can be analyzed, possibly improved, and potentially merged into the actual source code. For some recent examples, see: http://www.tocker.ca/2014/06/09/mysql-5-6-19-community-release-notes.html -- Shawn Green MySQL Senior Principal Technical Support Engineer Oracle USA, Inc. - Hardware and Software, Engineered to Work Together. Office: Blountville, TN -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
How to get all known bugs on specified mysql version?
Hi, all, I want to use MySQL 5.6.18 in production, so i want to get all known bugs on this version. Now i check the bugfix section in MySQL 5.6.19 and above version. Am i doing the right thing? Or Do you have a better method? Any input will be appreciated!
Benetl, a free ETL tool for MySQL, out in version 4.5
Dear all, Benetl, a free ETL tool for MySQL, is out in version 4.5. This version of Benetl is now Java 7 and has been tested on 64 bit systems. This versions is correcting two bugs: Trouble with double parsing when data contains ',' as float separator Divide function now accepts negative operand and shows an error when divide by 0 Part operator brings a new function: fact. New error messages provided. More than 100 tests passed. You should really update. Benetl is freely dowloadable at:http://www.benetl.net You can learn more about ETL tools at: http://en.wikipedia.org/wiki/Extract,_transform,_load Thanks for your interest. Regards, -- Benoît Carpentier http://www.benetl.net Founder of Benetl and Java project manager
RE: MySQL version 3.23 to 5.x features
Assuming that your goal is to migrate an old database, perhaps the things that will bite you the fastest: * TYPE=MyISAM -- ENGINE=MyISAM. * CHARACTER SETs -- no concept in until 4.1. Use DEFAULT CHARACTER SET=latin1 for now. Later you can figure out how to migrate to utf8. (Note that 5.5 defaults to utf8, which is likely to dislike your bytes.) I would dump the data, then import into 5.x. Upgrading step by step would be quite tedious. Migration to InnoDB is also desirable, but not mandatory. -Original Message- From: Nagaraj S [mailto:nagaraj@gmail.com] Sent: Thursday, August 22, 2013 12:16 AM To: shawn green Cc: mysql@lists.mysql.com Subject: Re: MySQL version 3.23 to 5.x features wow it really helped me a lot. I really thank Shawn,Dale Jesper for there inputs On Wed, Aug 21, 2013 at 7:13 PM, shawn green shawn.l.gr...@oracle.comwrote: Hello Naga, On 8/21/2013 6:45 AM, Nagaraj S wrote: Hello, Can anyone share the features/comparison from MySQL version 3.23 to 5.x in single document? I can get from Google, however I have to navigate different pages/sites, if it is in single document that will be useful to see the overview of mysql features While not exactly just one single page for all changes, there is a single page of the fine manual within each new major version that describes the big features that are new or changed within that version. http://dev.mysql.com/doc/**refman/5.0/en/mysql-nutshell.**htmlhttp:// dev.mysql.com/doc/refman/5.0/en/mysql-nutshell.html http://dev.mysql.com/doc/**refman/5.1/en/mysql-nutshell.**htmlhttp:// dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html http://dev.mysql.com/doc/**refman/5.5/en/mysql-nutshell.**htmlhttp:// dev.mysql.com/doc/refman/5.5/en/mysql-nutshell.html http://dev.mysql.com/doc/**refman/5.6/en/mysql-nutshell.**htmlhttp:// dev.mysql.com/doc/refman/5.6/en/mysql-nutshell.html Unfortunately, to learn what we changed between 3.23 - 4.0 or between 4.0 - 4.1, you are going to need to review the change logs http://dev.mysql.com/doc/**refman/4.1/en/news.htmlhttp://dev.mysql.co m/doc/refman/4.1/en/news.html from http://dev.mysql.com/doc/**refman/4.1/en/index.htmlhttp://dev.mysql.c om/doc/refman/4.1/en/index.html This manual describes features that are not included in every edition of MySQL 3.23, MySQL 4.0, and MySQL 4.1; such features may not be included in the edition of MySQL 3.23, MySQL 4.0, or MySQL 4.1; licensed to you. I can pretty much summarize the deficiencies in 3.23 like this * No InnoDB, Archive, CSV, Federated, or Blackhole storage engines * No table partitioning * No Views * No Stored Procedures or Stored Functions * No Triggers * No Events * Severe scalability limits (won't run as fast with reasonably concurrent loads even on great hardware as later versions) * Completely out of print (unpublished) and unsupported. * Missing literally thousands of bug fixes and performance improvements Any new project should be starting out with 5.6. Any production server should be on 5.5 or 5.6 by now or migrating soon. It is also a fairly safe bet that if you are still operating a 3.23 instance of MySQL that it is also time to upgrade your hardware. Regards, -- Shawn Green MySQL Principal Technical Support Engineer Oracle USA, Inc. - Hardware and Software, Engineered to Work Together. Office: Blountville, TN -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
Re: MySQL version 3.23 to 5.x features
wow it really helped me a lot. I really thank Shawn,Dale Jesper for there inputs On Wed, Aug 21, 2013 at 7:13 PM, shawn green shawn.l.gr...@oracle.comwrote: Hello Naga, On 8/21/2013 6:45 AM, Nagaraj S wrote: Hello, Can anyone share the features/comparison from MySQL version 3.23 to 5.x in single document? I can get from Google, however I have to navigate different pages/sites, if it is in single document that will be useful to see the overview of mysql features While not exactly just one single page for all changes, there is a single page of the fine manual within each new major version that describes the big features that are new or changed within that version. http://dev.mysql.com/doc/**refman/5.0/en/mysql-nutshell.**htmlhttp://dev.mysql.com/doc/refman/5.0/en/mysql-nutshell.html http://dev.mysql.com/doc/**refman/5.1/en/mysql-nutshell.**htmlhttp://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html http://dev.mysql.com/doc/**refman/5.5/en/mysql-nutshell.**htmlhttp://dev.mysql.com/doc/refman/5.5/en/mysql-nutshell.html http://dev.mysql.com/doc/**refman/5.6/en/mysql-nutshell.**htmlhttp://dev.mysql.com/doc/refman/5.6/en/mysql-nutshell.html Unfortunately, to learn what we changed between 3.23 - 4.0 or between 4.0 - 4.1, you are going to need to review the change logs http://dev.mysql.com/doc/**refman/4.1/en/news.htmlhttp://dev.mysql.com/doc/refman/4.1/en/news.html from http://dev.mysql.com/doc/**refman/4.1/en/index.htmlhttp://dev.mysql.com/doc/refman/4.1/en/index.html This manual describes features that are not included in every edition of MySQL 3.23, MySQL 4.0, and MySQL 4.1; such features may not be included in the edition of MySQL 3.23, MySQL 4.0, or MySQL 4.1; licensed to you. I can pretty much summarize the deficiencies in 3.23 like this * No InnoDB, Archive, CSV, Federated, or Blackhole storage engines * No table partitioning * No Views * No Stored Procedures or Stored Functions * No Triggers * No Events * Severe scalability limits (won't run as fast with reasonably concurrent loads even on great hardware as later versions) * Completely out of print (unpublished) and unsupported. * Missing literally thousands of bug fixes and performance improvements Any new project should be starting out with 5.6. Any production server should be on 5.5 or 5.6 by now or migrating soon. It is also a fairly safe bet that if you are still operating a 3.23 instance of MySQL that it is also time to upgrade your hardware. Regards, -- Shawn Green MySQL Principal Technical Support Engineer Oracle USA, Inc. - Hardware and Software, Engineered to Work Together. Office: Blountville, TN -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
MySQL version 3.23 to 5.x features
Hello, Can anyone share the features/comparison from MySQL version 3.23 to 5.x in single document? I can get from Google, however I have to navigate different pages/sites, if it is in single document that will be useful to see the overview of mysql features -Naga
Re: MySQL version 3.23 to 5.x features
Hello Naga, On 8/21/2013 6:45 AM, Nagaraj S wrote: Hello, Can anyone share the features/comparison from MySQL version 3.23 to 5.x in single document? I can get from Google, however I have to navigate different pages/sites, if it is in single document that will be useful to see the overview of mysql features While not exactly just one single page for all changes, there is a single page of the fine manual within each new major version that describes the big features that are new or changed within that version. http://dev.mysql.com/doc/refman/5.0/en/mysql-nutshell.html http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html http://dev.mysql.com/doc/refman/5.5/en/mysql-nutshell.html http://dev.mysql.com/doc/refman/5.6/en/mysql-nutshell.html Unfortunately, to learn what we changed between 3.23 - 4.0 or between 4.0 - 4.1, you are going to need to review the change logs http://dev.mysql.com/doc/refman/4.1/en/news.html from http://dev.mysql.com/doc/refman/4.1/en/index.html This manual describes features that are not included in every edition of MySQL 3.23, MySQL 4.0, and MySQL 4.1; such features may not be included in the edition of MySQL 3.23, MySQL 4.0, or MySQL 4.1; licensed to you. I can pretty much summarize the deficiencies in 3.23 like this * No InnoDB, Archive, CSV, Federated, or Blackhole storage engines * No table partitioning * No Views * No Stored Procedures or Stored Functions * No Triggers * No Events * Severe scalability limits (won't run as fast with reasonably concurrent loads even on great hardware as later versions) * Completely out of print (unpublished) and unsupported. * Missing literally thousands of bug fixes and performance improvements Any new project should be starting out with 5.6. Any production server should be on 5.5 or 5.6 by now or migrating soon. It is also a fairly safe bet that if you are still operating a 3.23 instance of MySQL that it is also time to upgrade your hardware. Regards, -- Shawn Green MySQL Principal Technical Support Engineer Oracle USA, Inc. - Hardware and Software, Engineered to Work Together. Office: Blountville, TN -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
Re: MySQL version 3.23 to 5.x features
Hi Naga, On 21/08/2013 23:43, shawn green wrote: Hello Naga, On 8/21/2013 6:45 AM, Nagaraj S wrote: Hello, Can anyone share the features/comparison from MySQL version 3.23 to 5.x in single document? I can get from Google, however I have to navigate different pages/sites, if it is in single document that will be useful to see the overview of mysql features While not exactly just one single page for all changes, there is a single page of the fine manual within each new major version that describes the big features that are new or changed within that version. Just to add one reference to Shawn's list, there is also a MySQL Server Version Reference at https://dev.mysql.com/doc/mysqld-version-reference/en/index.html. It is lower level such as which options and functions are available in each major version. However it does not start out before version 5.0, so will not help you over the 3.23 - 4.0 - 5.0 hurdle. Best regards, Jesper Krogh MySQL Support -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
Fwd: Re: libmysqlclient so version
Forwarding my reply here, as it might be interesting to other people too. Original Message Subject: Re: libmysqlclient so version Date: Mon, 05 Aug 2013 14:10:28 +0200 From: rafal somla rafal.so...@oracle.com Organization: Oracle Corporation To: Sebastien FLAESCH s...@4js.com Hello Sebastien, Thank you for your interest in our latest MySQL server release. On 07/31/2013 01:03 PM, Sunanda Menon wrote: * The C API libmysqlclient shared-library .so files now have version 18.1.0 (up from version 18.0.0 used in MySQL 5.5). (Bug #16809055) What impact has this change regarding backward compatibility with existing C programs linked to older 5.6 libmysqlclient.so libs and what is the general policy regarding the backward compatibility for this library - where can we find clear statements in the doc? Does it make sense to change the .so version in a bug fix release, when the 5.6 was already releases as GA? We are providing database drivers for MySQL in our development tool. We have a C shared library linked to libmysqlclient.so, and we have to link it with the correct 5.6 library version. What solution would you recommend, if you change the .so version number in MySQL 5.6 upgrade / bug fix releases? Although we changed the minor library version in 5.6.13, it should be fully backward compatible with previous versions and code using the library should work without any problems. In particular, any code which links against libmysqlclient.so depends on libmysqlclient.so.18 (note that the minor version number is not present in the soname). Version 18.1.0 of the library installs with a symbolic link libmysqlclient.so.18 - libmysqlclient.so.18.1.0. Thus we expect all applications to work as before after upgrading to MySQL 5.6.13. Please let us know if it does not work for you. With Best Regards, Rafal Somla, Senior Software Developer @ MySQL/Oracle -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
Re: libmysqlclient so version
Hello again! On 2013-08-05 15:07, Sebastien FLAESCH wrote: Hello Rafal and thank you for you answer. Note I sent a similar mail in the mailing list. So I think you should also answer in the mailing list too. I understand that it should be ok regarding libmysqlclient.so.18.1.0. $ ldd -r /home/sf/genero/devel/fgl/fgl/opt/fgl/dbdrivers/dbmmys55x.so libmysqlclient.so.18 = /opt3/dbs/mys/5.6.10/lib/libmysqlclient.so.18 (0xb7298000) If I may ask you something that would help me a lot: We have an internal debate, where some argue that we could have a unique binary linked to libmysqlclient.so, that could work for all MySQL versions, for example for all 5.x versions. While it appears that 5.5.x and 5.6.x libraries are compatible (since the major version number (18) of the lib did not change), my instinct is that we should produce one specific binary for each major MySQL version we want to support (i.e 4.1.x, 5.0.x, 5.1.x, 5.4.x, 5.5.x, 5.6.x) ... We need a clear rule...!! For example with Oracle database, we have a binary for each major version of Oracle (9.0.x, 9.2.x, 10.1.x, 10.2.x, 11.1.x, 11.2.x, 12.1.x) I asked for a clear compatibility statement in the doc... If you could state that it's STRONGLY recommended to link C binaries with a libmysqlclient.so.num version for each major MySQL, it would help me to define a clear rule for our product... In general we strive to keep the library backward compatible - as long as the major version of the library is the same, it should be safe to use the library with old applications. You should care about minor version only if you want to use some new API calls introduced in later release of the library. I think the best practice would be to check which release of the library is used at runtime (using mysql_client_version() API call) and then either make use of new features conditional on this version check or error-out if library is not recent enough The major version of libmysqlclient library is not tied to a particular version of MySQL server. It rather reflects changes in the C API itself. Thus it is quite possible that two different versions of MySQL server offer the same version 18.X of the client library with the same functionality, but perhaps the newer version contains bug fixes or improvements in the implementation of this functionality. Thus I do not see a need to produce new version of binaries for each new released version of MySQL server. Rather, you should re-compile your applications only if either: a) you want to use new C API features introduced in the new release, or b) we introduce incompatible change in C API and thus increase its major version number (e.g from 18.X to 19.0). In that case new binaries will look for libmysqlclient.so.19 while old ones will still use libmysqlclient.so.18. Note that even without re-compiling your apps, if you upgrade your MySQL installation then new version of libmysqlcient.so will be installed on your system and picked up by the dynamic linker. So your application will take benefit of bug fixes and other improvements in C API implementation. Best Regards, Rafal Best regards, Sebastien FLAESCH Four JS Development Tools On 08/05/2013 02:10 PM, rafal somla wrote: Hello Sebastien, Thank you for your interest in our latest MySQL server release. On 07/31/2013 01:03 PM, Sunanda Menon wrote: * The C API libmysqlclient shared-library .so files now have version 18.1.0 (up from version 18.0.0 used in MySQL 5.5). (Bug #16809055) What impact has this change regarding backward compatibility with existing C programs linked to older 5.6 libmysqlclient.so libs and what is the general policy regarding the backward compatibility for this library - where can we find clear statements in the doc? Does it make sense to change the .so version in a bug fix release, when the 5.6 was already releases as GA? We are providing database drivers for MySQL in our development tool. We have a C shared library linked to libmysqlclient.so, and we have to link it with the correct 5.6 library version. What solution would you recommend, if you change the .so version number in MySQL 5.6 upgrade / bug fix releases? Although we changed the minor library version in 5.6.13, it should be fully backward compatible with previous versions and code using the library should work without any problems. In particular, any code which links against libmysqlclient.so depends on libmysqlclient.so.18 (note that the minor version number is not present in the soname). Version 18.1.0 of the library installs with a symbolic link libmysqlclient.so.18 - libmysqlclient.so.18.1.0. Thus we expect all applications to work as before after upgrading to MySQL 5.6.13. Please let us know if it does not work for you. With Best Regards, Rafal Somla, Senior Software Developer @ MySQL/Oracle -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
Re: Red Hat will switch the default database in its enterprise distribution, RHEL, from MySQL to MariaDB, when version 7 is released.
Am 14.06.2013 21:29, schrieb Daevid Vincent: http://www.itwire.com/business-it-news/open-source/60292-red-hat-ditches-mysql-switches-to-mariadb no wonder since oracle is fucking up *every* opensource project they touched over the last years and most other distributions are doing the same what *isses me* is that Oracle needed to step in the Fedora process to keep their package and all the crap in SPEC files after that is just horrible they would have been better work with the community the last two years ago instead now try to insist that their version is kept in whatever distributions repos __ http://dev.mysql.com/doc/relnotes/mysql/5.5/en/news-5-5-33.html in the past you could spot here fixes of the next version and sometimes avoid to update to the currecnt if one of the bugs would hurt you and that was only one example signature.asc Description: OpenPGP digital signature
Re: Red Hat will switch the default database in its enterprise distribution, RHEL, from MySQL to MariaDB, when version 7 is released.
and they are *still fucking too stupid* to fix their dmaned mailing-list server to add List/Bulk headers which would prevent all this auto-replies from well maintained mailservers Am 14.06.2013 21:42, schrieb Reindl Harald: Am 14.06.2013 21:29, schrieb Daevid Vincent: http://www.itwire.com/business-it-news/open-source/60292-red-hat-ditches-mysql-switches-to-mariadb no wonder since oracle is fucking up *every* opensource project they touched over the last years and most other distributions are doing the same what *isses me* is that Oracle needed to step in the Fedora process to keep their package and all the crap in SPEC files after that is just horrible they would have been better work with the community the last two years ago instead now try to insist that their version is kept in whatever distributions repos __ http://dev.mysql.com/doc/relnotes/mysql/5.5/en/news-5-5-33.html in the past you could spot here fixes of the next version and sometimes avoid to update to the currecnt if one of the bugs would hurt you and that was only one example signature.asc Description: OpenPGP digital signature
Benetl, a free ETL tool for MySQL, out in version 4.4
Dear all, Benetl, a free ETL tool for MySQL, is out in version 4.4. This version brings much better peformances with a new functionality: batch mode. In the GUI you can set the number of lines to be commited in a same transaction. This versions is correcting two bugs: The last line read was forgotten we re-run an EtlTool (bug brought by version 4.3). The last line read was read again if its position in the file is equal to first line to read position, when re-run an EtlTool. Some GUI improvement and new tests added. You should really update. Benetl is freely dowloadable at:http://www.benetl.net You can learn more about ETL tools at: http://en.wikipedia.org/wiki/Extract,_transform,_load Thanks for your interest. Regards, -- Benoît Carpentier http://www.benetl.net Founder of Benetl and Java project manager
Version 5.6.2-m5 Boolean Datatype
Hi, I've just created some tables that I designed using the MySQL Workbench Model. However, the database type BOOLEAN which was in my models has been converted to TINYINT(1); I'm currently running MySQL Version 5.6.2-m5 on Windows 2008 server. Any ideas why this has been removed ? Neil
Re: Version 5.6.2-m5 Boolean Datatype
Hi, Like the link states For clarity: a TINYINT(1) datatype does NOT ENFORCE a boolean value data entry. For instance, it's still possible to insert a value of 2 (any integer up to the TINYINT max value). I personally don't see the added value of a 'BOOLEAN' synonym type which infact behaves unlike a boolean should. Has BOOL, BOOLEAN been taken out of MySQL 5.6 ? On Wed, May 22, 2013 at 6:01 PM, Ian Simpson i...@it.myjobgroup.co.ukwrote: BOOLEAN is a synonym for TINYINT(1) in MySQL: http://dev.mysql.com/doc/refman/5.6/en/numeric-type-overview.html On 22 May 2013 17:55, Neil Tompkins neil.tompk...@googlemail.com wrote: Hi, I've just created some tables that I designed using the MySQL Workbench Model. However, the database type BOOLEAN which was in my models has been converted to TINYINT(1); I'm currently running MySQL Version 5.6.2-m5 on Windows 2008 server. Any ideas why this has been removed ? Neil
Re: Version 5.6.2-m5 Boolean Datatype
Hey Neil, Why not just store it as a TINYINT, that's what I do when I only care about 0 or 1 values? On Wed, May 22, 2013 at 2:19 PM, Neil Tompkins neil.tompk...@googlemail.com wrote: Hi Shawn I plan in installing the latest MySQL version tomorrow. Does MySQL not support Bool eg true and false Neil On 22 May 2013, at 19:05, shawn green shawn.l.gr...@oracle.com wrote: Hello Neil, On 5/22/2013 1:05 PM, Neil Tompkins wrote: Hi, Like the link states For clarity: a TINYINT(1) datatype does NOT ENFORCE a boolean value data entry. For instance, it's still possible to insert a value of 2 (any integer up to the TINYINT max value). I personally don't see the added value of a 'BOOLEAN' synonym type which infact behaves unlike a boolean should. Has BOOL, BOOLEAN been taken out of MySQL 5.6 ? On Wed, May 22, 2013 at 6:01 PM, Ian Simpson i...@it.myjobgroup.co.uk wrote: BOOLEAN is a synonym for TINYINT(1) in MySQL: http://dev.mysql.com/doc/refman/5.6/en/numeric-type-overview.html On 22 May 2013 17:55, Neil Tompkins neil.tompk...@googlemail.com wrote: Hi, I've just created some tables that I designed using the MySQL Workbench Model. However, the database type BOOLEAN which was in my models has been converted to TINYINT(1); I'm currently running MySQL Version 5.6.2-m5 on Windows 2008 server. Any ideas why this has been removed ? This is exactly the same behavior that MySQL has had for over a decade. Nothing has been added or removed since release 4.1.0 (2003-04-03) http://dev.mysql.com/doc/refman/4.1/en/numeric-type-overview.html http://dev.mysql.com/doc/refman/4.1/en/news-4-1-x.html Also, why are you using a pre-release (milestone) version of 5.6 when the full release (GA) versions of 5.6 are available? http://dev.mysql.com/doc/relnotes/mysql/5.6/en/ Regards, -- Shawn Green MySQL Principal Technical Support Engineer Oracle USA, Inc. - Hardware and Software, Engineered to Work Together. Office: Blountville, TN -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql -- -- May the source be with you.
Re: Version 5.6.2-m5 Boolean Datatype
Hi Shawn I plan in installing the latest MySQL version tomorrow. Does MySQL not support Bool eg true and false Neil On 22 May 2013, at 19:05, shawn green shawn.l.gr...@oracle.com wrote: Hello Neil, On 5/22/2013 1:05 PM, Neil Tompkins wrote: Hi, Like the link states For clarity: a TINYINT(1) datatype does NOT ENFORCE a boolean value data entry. For instance, it's still possible to insert a value of 2 (any integer up to the TINYINT max value). I personally don't see the added value of a 'BOOLEAN' synonym type which infact behaves unlike a boolean should. Has BOOL, BOOLEAN been taken out of MySQL 5.6 ? On Wed, May 22, 2013 at 6:01 PM, Ian Simpson i...@it.myjobgroup.co.ukwrote: BOOLEAN is a synonym for TINYINT(1) in MySQL: http://dev.mysql.com/doc/refman/5.6/en/numeric-type-overview.html On 22 May 2013 17:55, Neil Tompkins neil.tompk...@googlemail.com wrote: Hi, I've just created some tables that I designed using the MySQL Workbench Model. However, the database type BOOLEAN which was in my models has been converted to TINYINT(1); I'm currently running MySQL Version 5.6.2-m5 on Windows 2008 server. Any ideas why this has been removed ? This is exactly the same behavior that MySQL has had for over a decade. Nothing has been added or removed since release 4.1.0 (2003-04-03) http://dev.mysql.com/doc/refman/4.1/en/numeric-type-overview.html http://dev.mysql.com/doc/refman/4.1/en/news-4-1-x.html Also, why are you using a pre-release (milestone) version of 5.6 when the full release (GA) versions of 5.6 are available? http://dev.mysql.com/doc/relnotes/mysql/5.6/en/ Regards, -- Shawn Green MySQL Principal Technical Support Engineer Oracle USA, Inc. - Hardware and Software, Engineered to Work Together. Office: Blountville, TN -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
Re: Version 5.6.2-m5 Boolean Datatype
Hello Neil, On 5/22/2013 1:05 PM, Neil Tompkins wrote: Hi, Like the link states For clarity: a TINYINT(1) datatype does NOT ENFORCE a boolean value data entry. For instance, it's still possible to insert a value of 2 (any integer up to the TINYINT max value). I personally don't see the added value of a 'BOOLEAN' synonym type which infact behaves unlike a boolean should. Has BOOL, BOOLEAN been taken out of MySQL 5.6 ? On Wed, May 22, 2013 at 6:01 PM, Ian Simpson i...@it.myjobgroup.co.ukwrote: BOOLEAN is a synonym for TINYINT(1) in MySQL: http://dev.mysql.com/doc/refman/5.6/en/numeric-type-overview.html On 22 May 2013 17:55, Neil Tompkins neil.tompk...@googlemail.com wrote: Hi, I've just created some tables that I designed using the MySQL Workbench Model. However, the database type BOOLEAN which was in my models has been converted to TINYINT(1); I'm currently running MySQL Version 5.6.2-m5 on Windows 2008 server. Any ideas why this has been removed ? This is exactly the same behavior that MySQL has had for over a decade. Nothing has been added or removed since release 4.1.0 (2003-04-03) http://dev.mysql.com/doc/refman/4.1/en/numeric-type-overview.html http://dev.mysql.com/doc/refman/4.1/en/news-4-1-x.html Also, why are you using a pre-release (milestone) version of 5.6 when the full release (GA) versions of 5.6 are available? http://dev.mysql.com/doc/relnotes/mysql/5.6/en/ Regards, -- Shawn Green MySQL Principal Technical Support Engineer Oracle USA, Inc. - Hardware and Software, Engineered to Work Together. Office: Blountville, TN -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
Re: Version 5.6.2-m5 Boolean Datatype
Why not use ENUM with True|False or Y|N Only issue is it doesn't throw and error of you enter an illegal value but I don't think I've ever flagged the field as NOT NULL. On Wed, May 22, 2013 11:32, Darryle Steplight wrote: Hey Neil, Why not just store it as a TINYINT, that's what I do when I only care about 0 or 1 values? On Wed, May 22, 2013 at 2:19 PM, Neil Tompkins neil.tompk...@googlemail.com wrote: Hi Shawn I plan in installing the latest MySQL version tomorrow. Does MySQL not support Bool eg true and false Neil On 22 May 2013, at 19:05, shawn green shawn.l.gr...@oracle.com wrote: Hello Neil, On 5/22/2013 1:05 PM, Neil Tompkins wrote: Hi, Like the link states For clarity: a TINYINT(1) datatype does NOT ENFORCE a boolean value data entry. For instance, it's still possible to insert a value of 2 (any integer up to the TINYINT max value). I personally don't see the added value of a 'BOOLEAN' synonym type which infact behaves unlike a boolean should. Has BOOL, BOOLEAN been taken out of MySQL 5.6 ? On Wed, May 22, 2013 at 6:01 PM, Ian Simpson i...@it.myjobgroup.co.uk wrote: BOOLEAN is a synonym for TINYINT(1) in MySQL: http://dev.mysql.com/doc/refman/5.6/en/numeric-type-overview.html On 22 May 2013 17:55, Neil Tompkins neil.tompk...@googlemail.com wrote: Hi, I've just created some tables that I designed using the MySQL Workbench Model. However, the database type BOOLEAN which was in my models has been converted to TINYINT(1); I'm currently running MySQL Version 5.6.2-m5 on Windows 2008 server. Any ideas why this has been removed ? This is exactly the same behavior that MySQL has had for over a decade. Nothing has been added or removed since release 4.1.0 (2003-04-03) http://dev.mysql.com/doc/refman/4.1/en/numeric-type-overview.html http://dev.mysql.com/doc/refman/4.1/en/news-4-1-x.html Also, why are you using a pre-release (milestone) version of 5.6 when the full release (GA) versions of 5.6 are available? http://dev.mysql.com/doc/relnotes/mysql/5.6/en/ Regards, -- Shawn Green -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
RE: Version 5.6.2-m5 Boolean Datatype
In query syntax, TRUE is the same as 1; FALSE is the same as 0.
A minor syntax note: ENUM('FALSE', 'TRUE') would require quotes when using it.
If you have multiple 'flags', consider the SET datatype. (Yeah, it is somewhat
clumsy.)
If you have installed 5.6, simply try BOOL or BOOLEAN. I suspect (without
proof) that it works the same as it has for more than a decade.
-Original Message-
From: Wm Mussatto [mailto:mussa...@csz.com]
Sent: Wednesday, May 22, 2013 1:57 PM
To: mysql@lists.mysql.com
Subject: Re: Version 5.6.2-m5 Boolean Datatype
Why not use ENUM with True|False or Y|N Only issue is it doesn't throw
and error of you enter an illegal value but I don't think I've ever
flagged the field as NOT NULL.
On Wed, May 22, 2013 11:32, Darryle Steplight wrote:
Hey Neil,
Why not just store it as a TINYINT, that's what I do when I only
care
about 0 or 1 values?
On Wed, May 22, 2013 at 2:19 PM, Neil Tompkins
neil.tompk...@googlemail.com
wrote:
Hi Shawn
I plan in installing the latest MySQL version tomorrow. Does MySQL
not
support Bool eg true and false
Neil
On 22 May 2013, at 19:05, shawn green shawn.l.gr...@oracle.com
wrote:
Hello Neil,
On 5/22/2013 1:05 PM, Neil Tompkins wrote:
Hi, Like the link states
For clarity: a TINYINT(1) datatype does NOT ENFORCE a boolean
value
data
entry. For instance, it's still possible to insert a value of 2
(any
integer up to the TINYINT max value). I personally don't see the
added
value of a 'BOOLEAN' synonym type which infact behaves unlike a
boolean
should.
Has BOOL, BOOLEAN been taken out of MySQL 5.6 ?
On Wed, May 22, 2013 at 6:01 PM, Ian Simpson
i...@it.myjobgroup.co.uk
wrote:
BOOLEAN is a synonym for TINYINT(1) in MySQL:
http://dev.mysql.com/doc/refman/5.6/en/numeric-type-
overview.html
On 22 May 2013 17:55, Neil Tompkins
neil.tompk...@googlemail.com
wrote:
Hi,
I've just created some tables that I designed using the MySQL
Workbench
Model. However, the database type BOOLEAN which was in my
models
has
been
converted to TINYINT(1); I'm currently running MySQL Version
5.6.2-m5 on
Windows 2008 server.
Any ideas why this has been removed ?
This is exactly the same behavior that MySQL has had for over a
decade.
Nothing has been added or removed since release 4.1.0 (2003-04-03)
http://dev.mysql.com/doc/refman/4.1/en/numeric-type-overview.html
http://dev.mysql.com/doc/refman/4.1/en/news-4-1-x.html
Also, why are you using a pre-release (milestone) version of 5.6
when
the full release (GA) versions of 5.6 are available?
http://dev.mysql.com/doc/relnotes/mysql/5.6/en/
Regards,
--
Shawn Green
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql
Re: Version 5.6.2-m5 Boolean Datatype
On 05/22/2013 06:55 PM, Neil Tompkins wrote: Hi, I've just created some tables that I designed using the MySQL Workbench Model. However, the database type BOOLEAN which was in my models has been converted to TINYINT(1); I'm currently running MySQL Version 5.6.2-m5 on Windows 2008 server. BOOLEAN has been a simple alias for TINYINT in MySQL ever since, for a more true boolean you may want to try BIT(1) http://dev.mysql.com/doc/refman/5.6/en/bit-type.html The BIT type was introduced in 5.6. For example: create table b1 (id int primary key, b bit(1)); insert into b1 values(1, true); insert into b1 values(2, false); select * from b1 WHERE b = true; == ++--+ | id | b| ++--+ | 1 | [00 01]| ++--+ 1 row in set (0.00 sec) Note that the BIT column value is actually returned as a VARBINARY string though ... -- hartmut -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
RE: Version 5.6.2-m5 Boolean Datatype
2013/05/22 21:17 +, Rick James In query syntax, TRUE is the same as 1; FALSE is the same as 0. and UNKNOWN is NULL. (I actually have used a three-state comparison.) It has been suggested that one who wants a real two-state field use the type CHAR(0) NULL. If you have more 'flags', consider the SET datatype. (Yeah, it is somewhat clumsy.) And SET is mapped onto some integer, even as ENUM is. BIT, now deprecated I understand, would have been the perfect type to map ENUM onto. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
Benetl, a free ETL tool for MySQL, out in version 4.3
Dear all, Benetl, a free ETL tool for MySQL, is out in version 4.3. This version brings a new way of reading control_file.xml files, several code corrections. This versions is correcting two bugs: Trouble with entity_id when inserting raw data. Trouble with sql script creation when setting none. Benetl is freely dowloadable at:http://www.benetl.net You can learn more about ETL tools at: http://en.wikipedia.org/wiki/Extract,_transform,_load Thanks for your interest. Regards, -- Benoît Carpentier http://www.benetl.net Founder of Benetl and Java project manager
ANN: Hopper, version 1.1.0 released
ANN: Hopper, version 1.1.0 released Dear ladies and gentlemen, Upscene Productions is proud to announce version 1.1.0 of our product called Hopper. Hopper is a Windows-based Stored Routine and Trigger Debugger, available for InterBase, Firebird and MySQL. For more information, see http://www.upscene.com/go/?go=hopper This release contains bugfixes and some small new features, see http://www.upscene.com/displaynews.php?item=20130129 With regards, Martijn Tonies Upscene Productions http://www.upscene.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
Benetl, a free ETL tool for MySQL, out in version 4.1
Dear all, Benetl, a free ETL tool for MySQL, is out in version 4.1. This version brings GUI improvement: control of field names and table (EtlTool) name. With this version, it is now possible to use and with if operator on a part formula. This version brings some code correction and improvement. Benetl is freely dowloadable at:http://www.benetl.net You can learn more about ETL tools at: http://en.wikipedia.org/wiki/Extract,_transform,_load Thanks for your interest. Regards, -- Benoît Carpentier http://www.benetl.net Founder of Benetl and Java project manager
ANN: Hopper (stored procedure debugger), version 1.0.3 released
ANN: Hopper, version 1.0.3 released Dear ladies and gentlemen, Upscene Productions is proud to announce version 1.0.3 of our product called Hopper. Hopper is a Windows-based Stored Routine and Trigger Debugger, available for InterBase, Firebird and MySQL. This version fixes an imporant error with the MySQL version, amongst other small issues. For more information, see http://www.upscene.com/displaynews.php?item=20120801 With regards, Martijn Tonies Upscene Productions http://www.upscene.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
ANN: Hopper, version 1.0.2 released
ANN: Hopper, version 1.0.2 released Dear ladies and gentlemen, Upscene Productions is proud to announce version 1.0.2 of our product called Hopper. Hopper is a Windows-based Stored Routine and Trigger Debugger, available for InterBase, Firebird and MySQL. For more information, see http://www.upscene.com/displaynews.php?item=20120713 With regards, Martijn Tonies Upscene Productions http://www.upscene.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
Re: ANN: Hopper (stored procedure debugger), version 1.0.1 released
Hello Jan, others, I do find your juvenile comments about worshipping, changing product names etc just that. Ah, you must be from the marketing department -- always willing to make friends and influence people. Please, Jan, I'm obviously not, I'm but a simple programmer. And given the fact that you started out by implying I worshipped Bill Gates, I'll take it you aren't willing to make new friends either. Website has been modified, product announcement as well. Can we close the book on this now? With regards, Martijn Tonies Upscene Productions http://www.upscene.com Download Database Workbench for Oracle, MS SQL Server, Sybase SQL Anywhere, MySQL, InterBase, NexusDB and Firebird! -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
Re: ANN: Hopper (stored procedure debugger), version 1.0.1 released
I do find your juvenile comments about worshipping, changing product names etc just that. Ah, you must be from the marketing department -- always willing to make friends and influence people. In examinations, the foolish ask questions that the wise cannot answer. -- Oscar Wilde Jan Steinman, EcoReality Co-op -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
Re: ANN: Hopper (stored procedure debugger), version 1.0.1 released
Hello Jan, Can you PLEASE note in your listing when a product is Microsloth-only? While you're at it, can you PLEASE note it prominently on your website? I looked through your product description and saw no specific requirements beyond what databases were supported. It wasn't until I tried to download it that I noticed the warning sign. (.EXE in the file name) Hard as it is to believe, the entire world does not worship at the alter of Bill Gates. We don't allow any Microsloth products on our site. Although you have a point about the product announcement and lack of mentioning the required OS on our website, I do find your juvenile comments about worshipping, changing product names etc just that. I'll adjust the website and announcements. :) Have a nice weekend. With regards, Martijn Tonies Upscene Productions http://www.upscene.com Download Database Workbench for Oracle, MS SQL Server, Sybase SQL Anywhere, MySQL, InterBase, NexusDB and Firebird! -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
Re: ANN: Hopper (stored procedure debugger), version 1.0.1 released
Can you PLEASE note in your listing when a product is Microsloth-only? While you're at it, can you PLEASE note it prominently on your website? I looked through your product description and saw no specific requirements beyond what databases were supported. It wasn't until I tried to download it that I noticed the warning sign. (.EXE in the file name) Hard as it is to believe, the entire world does not worship at the alter of Bill Gates. We don't allow any Microsloth products on our site. In a low-energy future... the wealth of nations will be measured by the quantity and quality of their forests. -- David Holmgren Jan Steinman, EcoReality Co-op -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
ANN: Hopper (stored procedure debugger), version 1.0.1 released
ANN: Hopper, version 1.0.1 released Dear ladies and gentlemen, Upscene Productions is proud to announce version 1 of a new product called Hopper. Hopper is a Stored Routine and Trigger Debugger, available for InterBase, Firebird and MySQL. For more information, see http://www.upscene.com/displaynews.php?item=20120620 With regards, Martijn Tonies Upscene Productions http://www.upscene.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
License question on libmysql.dll and C/C++ API Version 4.0 question about Victoria Reznichenko response
Hello, Y read this message: http://lists.mysql.com/mysql/109590 and I would like to ask for authorization but I don´t see the email address in that thread (it says: sales@stripped). Can someone tell me that email address?. Thanks in advance. Claudia.
Re: License question on libmysql.dll and C/C++ API Version 4.0 question about Victoria Reznichenko response
Hello Claudia, On 6/18/2012 2:13 PM, Claudia Murialdo wrote: Hello, Y read this message: http://lists.mysql.com/mysql/109590 and I would like to ask for authorization but I don´t see the email address in that thread (it says: sales@stripped). Can someone tell me that email address?. Thanks in advance. Claudia. That link is 10 years old and that address is no longer valid. MySQL has been bought twice since then once directly by Sun Microsystems then again when Oracle purchased Sun. Your current questions need to be asked to Oracle. These numbers will route you to the appropriate resources http://www.oracle.com/us/support/contact-068555.html -- Shawn Green MySQL Principal Technical Support Engineer Oracle USA, Inc. - Hardware and Software, Engineered to Work Together. Office: Blountville, TN -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
Re: RFE: Allow to use version-specific my.cnf files
On 04/27/2012 03:26 PM, Shawn Green wrote: I frequently need to have multiple versions ready to operate on my machine at any time. I solved the configuration file problems by only setting them up in the basedir of the installed version. For those special occasions when I need to configure multiple copies of the same version, I create a separate set of --datadir folders and craft separate configuration files for both. I start mysqld using the --defaults-file option and point that at the special file for each instance. As a matter of convenience, if you need to constantly run with multiple instances on the same host and if any one of those may need to be using a different version than the others, then the utility mysqld_multi may be what you need to be looking at. Each instance you manage by the script can have their own separate set of settings all stored in the same, common, configuration file. Check it out: http://dev.mysql.com/doc/refman/5.1/en/mysqld-multi.html Hi Shawn, thanks for pointing to that. So we have a possibility to define different options for different server instances using mysqld_multi. My proposal allows to have something similar for clients as well (without need to specify any command-line argument), or in cases when we want to define the same options to more servers, according to their version. It's probably nothing we cannot do now. But it could be a nice option, much more cleaner in some environments. Cheers, Honza -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
RE: RFE: Allow to use version-specific my.cnf files
I think you need deal with only these: * Diff my.cnf (set as a parameter to mysqld) * Diff tree for all the data (and reflect this in my.cnf) * Diff port (3306 can't be shared between the instances) -Original Message- From: Andrés Tello [mailto:mr.crip...@gmail.com] Sent: Wednesday, April 25, 2012 8:52 AM To: Honza Horak Cc: mysql@lists.mysql.com Subject: Re: RFE: Allow to use version-specific my.cnf files Reads interesting, but... Why would you need that? I mean... If I run several databases in the same hardware, I use completely diferent paths for evertying, so I can have atomic, clean and specific files for each instance/version of the database I think is much more easy to migrato to another hardware that way, just copy the instance and you are set... On Wed, Apr 25, 2012 at 9:23 AM, Honza Horak hho...@redhat.com wrote: Hi, PostgreSQL allows to use version-specific configuration files, which allows to change some settings only for particular version of DB. I think a similar enhancement would be nice and usable for administrators of MySQL as well. Please, consider the attached patch as a simple proposal. Any comments are welcome. Cheers, Honza -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
Re: RFE: Allow to use version-specific my.cnf files
On 04/25/2012 05:52 PM, Andrés Tello wrote:
Reads interesting, but...
Why would you need that?
I mean... If I run several databases in the same hardware, I use completely
diferent paths for evertying, so I can have atomic, clean and specific
files for each instance/version of the database
Thanks for your opinion.
You're right, it doesn't make too much sense regarding system-wide
configuration files, such as /etc/my.cnf. A real use case I see is when
we speak about users' config files, like ~/.my.cnf.
Let's say we have two different MySQL versions on one hardware, then
it's possible we'll need a bit different options for each instance.
MySQL unfortunately doesn't distinguish between user-specific (usually
called rc files) and system-wide config files. Trying to have the patch
simple, I applied the feature to all config files (which was not necessary).
The attached patch now is a bit more complicated, but restricts the
feature only for config files in user's home directory. I believe this
makes more sense, than the original one.
Any comments welcome again.
Cheers,
Honza
diff -up mysql-5.5.22/mysys/default.c.versionedcnf mysql-5.5.22/mysys/default.c
--- mysql-5.5.22/mysys/default.c.versionedcnf 2012-03-02 20:44:47.0 +0100
+++ mysql-5.5.22/mysys/default.c 2012-04-27 09:44:01.136938181 +0200
@@ -37,6 +37,7 @@
#include m_string.h
#include m_ctype.h
#include my_dir.h
+#include mysql_version.h
#ifdef __WIN__
#include winbase.h
#endif
@@ -660,18 +661,24 @@ static int search_default_file(Process_o
const char *config_file)
{
char **ext;
+ char **version_ext;
const char *empty_list[]= { , 0 };
+ const char *versioned_list[]= { , - MYSQL_SERVER_VERSION, 0 };
my_bool have_ext= fn_ext(config_file)[0] != 0;
const char **exts_to_use= have_ext ? empty_list : f_extensions;
+ const char **versioned_exts_to_use= (dir[0] == FN_HOMELIB) ? versioned_list : empty_list;
for (ext= (char**) exts_to_use; *ext; ext++)
- {
-int error;
-if ((error= search_default_file_with_ext(opt_handler, handler_ctx,
- dir, *ext,
- config_file, 0)) 0)
- return error;
- }
+for (version_ext= (char**) versioned_exts_to_use; *version_ext; version_ext++)
+{
+ int error;
+ char full_ext[FN_REFLEN + sizeof(MYSQL_SERVER_VERSION) + 2];
+ strxmov(full_ext,*ext,*version_ext,NullS);
+ if ((error= search_default_file_with_ext(opt_handler, handler_ctx,
+ dir, full_ext,
+ config_file, 0)) 0)
+return error;
+}
return 0;
}
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql
Re: RFE: Allow to use version-specific my.cnf files
Hello Honza, On 4/27/2012 4:35 AM, Honza Horak wrote: On 04/25/2012 05:52 PM, Andrés Tello wrote: Reads interesting, but... Why would you need that? I mean... If I run several databases in the same hardware, I use completely diferent paths for evertying, so I can have atomic, clean and specific files for each instance/version of the database Thanks for your opinion. You're right, it doesn't make too much sense regarding system-wide configuration files, such as /etc/my.cnf. A real use case I see is when we speak about users' config files, like ~/.my.cnf. Let's say we have two different MySQL versions on one hardware, then it's possible we'll need a bit different options for each instance. MySQL unfortunately doesn't distinguish between user-specific (usually called rc files) and system-wide config files. Trying to have the patch simple, I applied the feature to all config files (which was not necessary). The attached patch now is a bit more complicated, but restricts the feature only for config files in user's home directory. I believe this makes more sense, than the original one. Any comments welcome again. Cheers, I frequently need to have multiple versions ready to operate on my machine at any time. I solved the configuration file problems by only setting them up in the basedir of the installed version. For those special occasions when I need to configure multiple copies of the same version, I create a separate set of --datadir folders and craft separate configuration files for both. I start mysqld using the --defaults-file option and point that at the special file for each instance. As a matter of convenience, if you need to constantly run with multiple instances on the same host and if any one of those may need to be using a different version than the others, then the utility mysqld_multi may be what you need to be looking at. Each instance you manage by the script can have their own separate set of settings all stored in the same, common, configuration file. Check it out: http://dev.mysql.com/doc/refman/5.1/en/mysqld-multi.html -- Shawn Green MySQL Principal Technical Support Engineer Oracle USA, Inc. - Hardware and Software, Engineered to Work Together. Office: Blountville, TN -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
RFE: Allow to use version-specific my.cnf files
Hi,
PostgreSQL allows to use version-specific configuration files, which
allows to change some settings only for particular version of DB.
I think a similar enhancement would be nice and usable for
administrators of MySQL as well.
Please, consider the attached patch as a simple proposal. Any comments
are welcome.
Cheers,
Honza
diff -up mysql-5.5.22/mysys/default.c.versionedcnf mysql-5.5.22/mysys/default.c
--- mysql-5.5.22/mysys/default.c.versionedcnf 2012-03-02 20:44:47.0 +0100
+++ mysql-5.5.22/mysys/default.c 2012-04-25 14:51:32.824181063 +0200
@@ -37,6 +37,7 @@
#include m_string.h
#include m_ctype.h
#include my_dir.h
+#include mysql_version.h
#ifdef __WIN__
#include winbase.h
#endif
@@ -94,10 +95,10 @@ static my_bool defaults_already_read= FA
static const char **default_directories = NULL;
#ifdef __WIN__
-static const char *f_extensions[]= { .ini, .cnf, 0 };
+static const char *f_extensions[]= { .ini, .cnf, .ini- MYSQL_SERVER_VERSION, .cnf- MYSQL_SERVER_VERSION, 0 };
#define NEWLINE \r\n
#else
-static const char *f_extensions[]= { .cnf, 0 };
+static const char *f_extensions[]= { .cnf, .cnf- MYSQL_SERVER_VERSION, 0 };
#define NEWLINE \n
#endif
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql
Re: RFE: Allow to use version-specific my.cnf files
Reads interesting, but... Why would you need that? I mean... If I run several databases in the same hardware, I use completely diferent paths for evertying, so I can have atomic, clean and specific files for each instance/version of the database I think is much more easy to migrato to another hardware that way, just copy the instance and you are set... On Wed, Apr 25, 2012 at 9:23 AM, Honza Horak hho...@redhat.com wrote: Hi, PostgreSQL allows to use version-specific configuration files, which allows to change some settings only for particular version of DB. I think a similar enhancement would be nice and usable for administrators of MySQL as well. Please, consider the attached patch as a simple proposal. Any comments are welcome. Cheers, Honza -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
Re: hide server-version at connect?
I suppose the assumption is that any client needs the server version to figure out the compatible set of capabilities, as there is no separate protocol versioning afaik. I suppose you could change the version in the source to the lowest that has the full featureset you need. -- Bier met grenadyn Is als mosterd by den wyn Sy die't drinkt, is eene kwezel Hy die't drinkt, is ras een ezel -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
Re: hide server-version at connect?
Am 10.01.2012 12:44, schrieb Johan De Meersman:
I suppose the assumption is that any client needs the server version to
figure out
the compatible set of capabilities, as there is no separate protocol
versioning afaik.
sure? what's the binary between version and mysql_native_password?
5.5.19-log�voI^}{rL��a'9,l]o7_\1}mysql_native_password
I suppose you could change the version in the source to the lowest that has
the
full featureset you need.
hmm - all servers/clients are Fedora with the same versions :-)
mysql 5.5 would be enough i guess, but how to create a patch for
rpmbuild which must not be permanently changed for every mysql update
signature.asc
Description: OpenPGP digital signature
Re: hide server-version at connect?
- Original Message - From: Reindl Harald h.rei...@thelounge.net sure? what's the binary between version and mysql_native_password? No idea, I never bothered to look at the raw protocol :-) mysql 5.5 would be enough i guess, but how to create a patch for rpmbuild which must not be permanently changed for every mysql update I wouldn't think that bit of the code changes a lot between versions, really. Still, do you really think exposing that is such a risk? Do you have servers exposed to the net? -- Bier met grenadyn Is als mosterd by den wyn Sy die't drinkt, is eene kwezel Hy die't drinkt, is ras een ezel -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
Re: hide server-version at connect?
Am 10.01.2012 13:29, schrieb Johan De Meersman: - Original Message - From: Reindl Harald h.rei...@thelounge.net sure? what's the binary between version and mysql_native_password? No idea, I never bothered to look at the raw protocol :-) me too :-) mysql 5.5 would be enough i guess, but how to create a patch for rpmbuild which must not be permanently changed for every mysql update I wouldn't think that bit of the code changes a lot between versions i will look really. Still, do you really think exposing that is such a risk? Do you have servers exposed to the net? currently i am scanning all servers from a OpenVAS-Appliance and my primary target is get away all information disclosures samba is the next in the list blwoing out even build-number *grr* all or nothing :-) signature.asc Description: OpenPGP digital signature
Re: hide server-version at connect?
Security through obscurity? If none of your MySQL (or samba) servers are open to untrusted networks, why do you need to hide this information. Sent from my iPad On Jan 10, 2012, at 6:35 AM, Reindl Harald h.rei...@thelounge.net wrote: Am 10.01.2012 13:29, schrieb Johan De Meersman: - Original Message - From: Reindl Harald h.rei...@thelounge.net sure? what's the binary between version and mysql_native_password? No idea, I never bothered to look at the raw protocol :-) me too :-) mysql 5.5 would be enough i guess, but how to create a patch for rpmbuild which must not be permanently changed for every mysql update I wouldn't think that bit of the code changes a lot between versions i will look really. Still, do you really think exposing that is such a risk? Do you have servers exposed to the net? currently i am scanning all servers from a OpenVAS-Appliance and my primary target is get away all information disclosures samba is the next in the list blwoing out even build-number *grr* all or nothing :-) -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
Re: hide server-version at connect?
- Original Message - From: Johnny Withers joh...@pixelated.net Security through obscurity? That sentence has been overused way too much. If you want to remove all obscurity from your security, just publish your passwords and private keys. If none of your MySQL (or samba) servers are open to untrusted networks, why do you need to hide this information. Because even on a trusted network you can have untrusted agents. Think malcontent employees, viruses, et cetera. Security comes in layers, the more the better - although I do agree that this particular layer is not the first priority. -- Bier met grenadyn Is als mosterd by den wyn Sy die't drinkt, is eene kwezel Hy die't drinkt, is ras een ezel -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
Re: hide server-version at connect?
On 10/01/12 15:41, Chris Tate-Davies wrote: On 10/01/12 13:34, Johan De Meersman wrote: - Original Message - From: Johnny Withersjoh...@pixelated.net Security through obscurity? That sentence has been overused way too much. If you want to remove all obscurity from your security, just publish your passwords and private keys. If none of your MySQL (or samba) servers are open to untrusted networks, why do you need to hide this information. Because even on a trusted network you can have untrusted agents. Think malcontent employees, viruses, et cetera. Security comes in layers, the more the better - although I do agree that this particular layer is not the first priority. Indeed, have a read of http://en.wikipedia.org/wiki/Defence_in_depth Sorry, wrong link, this is the right one: http://en.wikipedia.org/wiki/Defense_in_depth_(computing) http://en.wikipedia.org/wiki/Defense_in_depth_%28computing%29 - Registered Office: 15 Stukeley Street, London WC2B 5LT, England. Registered in England number 1421223 This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the email by you is prohibited. Please note that the information provided in this e-mail is in any case not legally binding; all committing statements require legally binding signatures. http://www.inflightproductions.com
Re: hide server-version at connect?
On 10/01/12 13:34, Johan De Meersman wrote: - Original Message - From: Johnny Withersjoh...@pixelated.net Security through obscurity? That sentence has been overused way too much. If you want to remove all obscurity from your security, just publish your passwords and private keys. If none of your MySQL (or samba) servers are open to untrusted networks, why do you need to hide this information. Because even on a trusted network you can have untrusted agents. Think malcontent employees, viruses, et cetera. Security comes in layers, the more the better - although I do agree that this particular layer is not the first priority. Indeed, have a read of http://en.wikipedia.org/wiki/Defence_in_depth *Chris Tate-Davies* *Software Development* Inflight Productions Ltd Telephone: 01295 269 680 15 Stukeley Street | London | WC2B 5LT *Email:*chris.tatedav...@inflightproductions.com mailto:chris.tatedav...@inflightproductions.com *Web:*www.inflightproductions.com http://www.inflightproductions.com/ - Registered Office: 15 Stukeley Street, London WC2B 5LT, England. Registered in England number 1421223 This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the email by you is prohibited. Please note that the information provided in this e-mail is in any case not legally binding; all committing statements require legally binding signatures. http://www.inflightproductions.com
Re: hide server-version at connect?
On Jan 9, 2012, at 7:27 PM, Reindl Harald wrote: Nessus/OpenVAS Test detects the exact server version _ NVT: MySQL Detection (OID: 1.3.6.1.4.1.25623.1.0.100152) Overview: MySQL, a open source database system is running at this host. MySQL Version '5.5.19-log' was detected on the remote host. _ is there any way to not disclosure the mysqld-version for a anonymous connected client? For the case you give below, no authentication has yet taken place, so you don't know whether the client is anonymous or not. But the version is needed for proper client-server negotiation to take place, I believe. Even if that were not true, any client, anonymous or not, can use SELECT @@version or SELECT VERSION() to get the version. [harry@srv-rhsoft:~]$ telnet localhost 3306 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. N 5.5.19-logs+%b?QYO]g��ke8'Xg~e\}!(mysql_native_password -- Paul DuBois Oracle Corporation / MySQL Documentation Team Madison, Wisconsin, USA www.mysql.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
Problem installing python MySQLdb on Mac OS X Version 10.5.8
-compiling build/bdist.macosx-10.4-i386/egg/MySQLdb/__init__.py to __init__.pyc byte-compiling build/bdist.macosx-10.4-i386/egg/MySQLdb/connections.py to connections.pyc byte-compiling build/bdist.macosx-10.4-i386/egg/MySQLdb/constants/__init__.py to __init__.pyc byte-compiling build/bdist.macosx-10.4-i386/egg/MySQLdb/constants/CLIENT.py to CLIENT.pyc byte-compiling build/bdist.macosx-10.4-i386/egg/MySQLdb/constants/CR.py to CR.pyc byte-compiling build/bdist.macosx-10.4-i386/egg/MySQLdb/constants/ER.py to ER.pyc byte-compiling build/bdist.macosx-10.4-i386/egg/MySQLdb/constants/FIELD_TYPE.py to FIELD_TYPE.pyc byte-compiling build/bdist.macosx-10.4-i386/egg/MySQLdb/constants/FLAG.py to FLAG.pyc byte-compiling build/bdist.macosx-10.4-i386/egg/MySQLdb/constants/REFRESH.py to REFRESH.pyc byte-compiling build/bdist.macosx-10.4-i386/egg/MySQLdb/converters.py to converters.pyc byte-compiling build/bdist.macosx-10.4-i386/egg/MySQLdb/cursors.py to cursors.pyc byte-compiling build/bdist.macosx-10.4-i386/egg/MySQLdb/release.py to release.pyc byte-compiling build/bdist.macosx-10.4-i386/egg/MySQLdb/times.py to times.pyc creating stub loader for _mysql.so byte-compiling build/bdist.macosx-10.4-i386/egg/_mysql.py to _mysql.pyc creating build/bdist.macosx-10.4-i386/egg/EGG-INFO copying MySQL_python.egg-info/PKG-INFO - build/bdist.macosx-10.4-i386/egg/EGG-INFO copying MySQL_python.egg-info/SOURCES.txt - build/bdist.macosx-10.4-i386/egg/EGG-INFO copying MySQL_python.egg-info/dependency_links.txt - build/bdist.macosx-10.4-i386/egg/EGG-INFO copying MySQL_python.egg-info/top_level.txt - build/bdist.macosx-10.4-i386/egg/EGG-INFO writing build/bdist.macosx-10.4-i386/egg/EGG-INFO/native_libs.txt zip_safe flag not set; analyzing archive contents... creating 'dist/MySQL_python-1.2.3-py2.6-macosx-10.4-i386.egg' and adding 'build/bdist.macosx-10.4-i386/egg' to it removing 'build/bdist.macosx-10.4-i386/egg' (and everything under it) Processing MySQL_python-1.2.3-py2.6-macosx-10.4-i386.egg Removing /usr/local/lib/python2.6/site-packages/MySQL_python-1.2.3-py2.6-macosx-10.4-i386.egg Copying MySQL_python-1.2.3-py2.6-macosx-10.4-i386.egg to /usr/local/lib/python2.6/site-packages MySQL-python 1.2.3 is already the active version in easy-install.pth Installed /usr/local/lib/python2.6/site-packages/MySQL_python-1.2.3-py2.6-macosx-10.4-i386.egg Processing dependencies for MySQL-python==1.2.3 Finished processing dependencies for MySQL-python==1.2.3 TIA! -larry -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
Re: Problem installing python MySQLdb on Mac OS X Version 10.5.8
On Mon, Jan 9, 2012 at 2:21 PM, Larry Martell larry.mart...@gmail.com wrote:
Some may consider this slightly off-topic, but I'm out of places to
turn to, so I'm hoping someone here can help me.
I am having no luck with getting the python module MySQLdb to work on
my Mac. I am getting the dreaded 'wrong architecture' message when I
try to import the module. I googled this, and found this page:
http://stackoverflow.com/questions/3061277/python-mysql-wrong-architecture-error
Following the instructions there I found that I did indeed have the 64
bit MySQL and a 32 bit python. I rectified that by deleting the 64-bit
install and then installing the 32-bit. Here's confirmation of that:
$ python -c 'import platform; print platform.platform()'
Darwin-9.8.0-i386-32bit
$ ls -l /usr/local/mysql
lrwxr-xr-x 1 root wheel 24 Jan 8 22:09 /usr/local/mysql -
mysql-5.5.19-osx10.5-x86
I rebuilt and reinstalled, but no joy. I added the env vars to my
.profile as suggested on that web page:
PATH=/usr/local/mysql/bin:${PATH}
export PATH
export DYLD_LIBRARY_PATH=/usr/local/mysql/lib/
export VERSIONER_PYTHON_PREFER_64_BIT=no
export VERSIONER_PYTHON_PREFER_32_BIT=yes
export ARCHFLAGS=-arch i386
Sourced my .profile, rebuilt and reinstalled, same error.
I'm thinking that perhaps something from the build I did when I had I
the 64-bit MySQL is getting left behind and messing up the new build.
But I don't know what that could be.
I solved this, and this is exactly what it was. Although I was doing a
'sudo python setup.py clean' between builds, it was not removing
everything. I did a 'sudo rm -rf build/*', then rebuild and reinstall,
and this error went away.
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql
Re: Chinese characters not displaying in Workbench latest version
The problem was the character set not loaded on the OS On 21 Nov 2011, at 22:08, Michael Cole colemic...@gmail.com wrote: I think what he was asking is, Are you running the Mysql workbench on the same machine? You may not have the correct Fonts. Being replicated the character sets of the two dbs should be the same have you checked that they actually are set to the same? On Monday, November 21, 2011 9:20:10 PM Neil Tompkins wrote: MySQL workbench On 21 Nov 2011, at 13:36, Chris Tate-Davies chris.tatedav...@inflightproductions.com wrote: What are you using to view the data? On Mon, 2011-11-21 at 08:22 -0500, h...@tbbs.net wrote: ; 2011/11/20 20:27 +, Tompkins Neil Does anyone know why Chinese characters are not displaying correctly in a replicated database on a slave machine ? I'm just getting square boxes. What displays them? it sounds to me as if the display lacks something, not so much MySQL. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/mysql?unsub=neil.tompk...@googlemail.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Re: Chinese characters not displaying in Workbench latest version
- Original Message - From: Tompkins Neil neil.tompk...@googlemail.com Does anyone know why Chinese characters are not displaying correctly in a replicated database on a slave machine ? I'm just getting square boxes. Random thought: terminal character set ? -- Bier met grenadyn Is als mosterd by den wyn Sy die't drinkt, is eene kwezel Hy die't drinkt, is ras een ezel -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Re: Chinese characters not displaying in Workbench latest version
; 2011/11/20 20:27 +, Tompkins Neil Does anyone know why Chinese characters are not displaying correctly in a replicated database on a slave machine ? I'm just getting square boxes. What displays them? it sounds to me as if the display lacks something, not so much MySQL. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Re: Chinese characters not displaying in Workbench latest version
What are you using to view the data? On Mon, 2011-11-21 at 08:22 -0500, h...@tbbs.net wrote: ; 2011/11/20 20:27 +, Tompkins Neil Does anyone know why Chinese characters are not displaying correctly in a replicated database on a slave machine ? I'm just getting square boxes. What displays them? it sounds to me as if the display lacks something, not so much MySQL. -- Chris Tate-Davies chris.tatedav...@inflightproductions.com - Registered Office: 15 Stukeley Street, London WC2B 5LT, England. Registered in England number 1421223 This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the email by you is prohibited. Please note that the information provided in this e-mail is in any case not legally binding; all committing statements require legally binding signatures. http://www.inflightproductions.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Re: Chinese characters not displaying in Workbench latest version
MySQL workbench On 21 Nov 2011, at 13:36, Chris Tate-Davies chris.tatedav...@inflightproductions.com wrote: What are you using to view the data? On Mon, 2011-11-21 at 08:22 -0500, h...@tbbs.net wrote: ; 2011/11/20 20:27 +, Tompkins Neil Does anyone know why Chinese characters are not displaying correctly in a replicated database on a slave machine ? I'm just getting square boxes. What displays them? it sounds to me as if the display lacks something, not so much MySQL. -- Chris Tate-Davies chris.tatedav...@inflightproductions.com - Registered Office: 15 Stukeley Street, London WC2B 5LT, England. Registered in England number 1421223 This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the email by you is prohibited. Please note that the information provided in this e-mail is in any case not legally binding; all committing statements require legally binding signatures. http://www.inflightproductions.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/mysql?unsub=neil.tompk...@googlemail.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Re: Chinese characters not displaying in Workbench latest version
I think what he was asking is, Are you running the Mysql workbench on the same machine? You may not have the correct Fonts. Being replicated the character sets of the two dbs should be the same have you checked that they actually are set to the same? On Monday, November 21, 2011 9:20:10 PM Neil Tompkins wrote: MySQL workbench On 21 Nov 2011, at 13:36, Chris Tate-Davies chris.tatedav...@inflightproductions.com wrote: What are you using to view the data? On Mon, 2011-11-21 at 08:22 -0500, h...@tbbs.net wrote: ; 2011/11/20 20:27 +, Tompkins Neil Does anyone know why Chinese characters are not displaying correctly in a replicated database on a slave machine ? I'm just getting square boxes. What displays them? it sounds to me as if the display lacks something, not so much MySQL. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Chinese characters not displaying in Workbench latest version
Does anyone know why Chinese characters are not displaying correctly in a replicated database on a slave machine ? I'm just getting square boxes. Thanks Neil
How often should we upgrade MySQL version
We are running MySQL 5.1.46 with master to master replication with 3 other servers for 3 different websites in 3 different parts of the world. My question is how often should we be looking to upgrade our MySQL version considering we can't really afford any downtime. Thanks Neil -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
RE: How often should we upgrade MySQL version
Ever heard the old saying, If it ain't broke, don't fix it. ;-) I'd say that as a general rule: 1. if you aren't experiencing problems then don't upgrade. 2. if you aren't subject to any vulnerabilities that may be found, then don't upgrade 3. if you don't need a new feature introduced, then don't upgrade 4. if you need to be up 100%, then don't upgrade Having said that, it is possible to upgrade with minimal downtime if you're smart about it. Get another server (or two or three) that is a clone of the existing ones. Upgrade those. Test those. Swap over. Then for the next release, do the same thing with the servers you now have as the spares. If you're in such a mission critical situation, you should have spare servers and live hot-swapable backups anyways right. -Original Message- From: Neil Tompkins [mailto:neil.tompk...@googlemail.com] Sent: Friday, November 18, 2011 11:54 AM To: MySQL ML Subject: How often should we upgrade MySQL version We are running MySQL 5.1.46 with master to master replication with 3 other servers for 3 different websites in 3 different parts of the world. My question is how often should we be looking to upgrade our MySQL version considering we can't really afford any downtime. Thanks Neil -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=dae...@daevid.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Re: How often should we upgrade MySQL version
I love the answer On Fri, Nov 18, 2011 at 10:59 PM, Daevid Vincent dae...@daevid.com wrote: Ever heard the old saying, If it ain't broke, don't fix it. ;-) I'd say that as a general rule: 1. if you aren't experiencing problems then don't upgrade. 2. if you aren't subject to any vulnerabilities that may be found, then don't upgrade 3. if you don't need a new feature introduced, then don't upgrade 4. if you need to be up 100%, then don't upgrade Having said that, it is possible to upgrade with minimal downtime if you're smart about it. Get another server (or two or three) that is a clone of the existing ones. Upgrade those. Test those. Swap over. Then for the next release, do the same thing with the servers you now have as the spares. If you're in such a mission critical situation, you should have spare servers and live hot-swapable backups anyways right. -Original Message- From: Neil Tompkins [mailto:neil.tompk...@googlemail.com] Sent: Friday, November 18, 2011 11:54 AM To: MySQL ML Subject: How often should we upgrade MySQL version We are running MySQL 5.1.46 with master to master replication with 3 other servers for 3 different websites in 3 different parts of the world. My question is how often should we be looking to upgrade our MySQL version considering we can't really afford any downtime. Thanks Neil -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=dae...@daevid.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/mysql?unsub=muadshib...@gmail.com -- *___* * * السجل .. كل الأخبار من كل مكان www.alsjl.com صفحة السجل على فيسبوك http://www.facebook.com/alsjl *Muad Shibani* * * Aden Yemen Mobile: 00967 733045678 www.muadshibani.com
Benetl, a free ETL tool for MySQL, is out in version 3.9.
Dear all, Benetl, a free ETL tool for MySQL, is out in version 3.9. This version is correcting two bugs in GUI and brings code improvement. Benetl is freely dowloadable at: http://www.benetl.net You can learn more about ETL tools at: http://en.wikipedia.org/wiki/Extract,_transform,_load Thanks for your interest. Regards, -- Benoît Carpentier http://www.benetl.net Founder of Benetl and Java project manager -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Benetl, a free ETL tool for MySQL, is out in version 3.8.
Dear all, Benetl, a free ETL tool for MySQL, is out in version 3.8. It is now supporting official MySQL (5.x) driver(s), not provided. Benetl is freely dowloadable at: http://www.benetl.net Please read documentation to see how to use the official MySQL driver instead of the provided driver. You can learn more about ETL tools at: http://en.wikipedia.org/wiki/Extract,_transform,_load Thanks for your interest. Regards -- Benoît Carpentier http://www.benetl.net Founder of Benetl and Java project manager -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Are those patches already includes in 5.5 community version?
For pathces like : *EBay Patches (5.0)* have included: - variable length memory storage engine - pool of threads - Virtual columns and others like *Google Patches (5.0 5.1)* included improvements in : - statistics/monitoring - lock contention - binlog - malloc() - filesorts - innodb I/O and wait statistics - SHOW …STATISTICS statements - smp scalability - I/O scalability - semisync replication - many more *Percona Patches (5.0)* focus on - statistics/monitoring - performance/scalability - buffer pool content/mutexes - microslow patch Thx -- Regards Zhu Chao
Re: Are those patches already includes in 5.5 community version?
Just looked at version 5.5/5.6 document: http://dev.mysql.com/doc/refman/5.5/en/memory-storage-engine.html at least the variable length memory patch is not included, i guess same with others; It is disappointed MySQL is not including those into the 5.5/5.6 version; BTW: i was reading http://ronaldbradford.com/blog/beyond-mysql-ga-patches-storage-engines-forks-and-pre-releases-fosdem-2010-2010-02-11/previously; On Tue, Apr 26, 2011 at 12:34 AM, Zhu,Chao zhuc...@gmail.com wrote: For pathces like : *EBay Patches (5.0)* have included: - variable length memory storage engine - pool of threads - Virtual columns and others like *Google Patches (5.0 5.1)* included improvements in : - statistics/monitoring - lock contention - binlog - malloc() - filesorts - innodb I/O and wait statistics - SHOW …STATISTICS statements - smp scalability - I/O scalability - semisync replication - many more *Percona Patches (5.0)* focus on - statistics/monitoring - performance/scalability - buffer pool content/mutexes - microslow patch Thx -- Regards Zhu Chao -- Regards Zhu Chao
Highest version of MySQL available for 2.4 kernel (RH/Cent OS 3.5)?
What is the highest version of MySQL available for a 2.4 kernel (Redhat/Cent OS 3.5)? And where can I find it to download? Thanks, -Hank
Benetl a free ETL tool using MySQL is out in version 3.7
Dear all, Benetl, a free ETL tool for files using MySQL, is out in version 3.7. You can freely download it at: www.benetl.net This version brings new controls and messages in the GUI. This version brings improvements and a bug correction in GUI. You should update. You can learn more about ETL tools at: http://en.wikipedia.org/wiki/Extract,_transform,_load Thanks for your interest. Regards, -- Benoît Carpentier http://www.benetl.net Founder of Benetl and Java project manager -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Benetl a free ETL tool using MySQL is out in version 3.7
Dear all, Benetl, a free ETL tool for files using MySQL, is out in version 3.7. You can freely download it at: www.benetl.net This version brings new controls and messages in the GUI. This version brings improvements and a bug correction in GUI. You should update. You can learn more about ETL tools at: http://en.wikipedia.org/wiki/Extract,_transform,_load Thanks for your interest. Regards, -- Benoît Carpentier www.benetl.net Founder of Benetl and Java project manager -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
libmysqlclient.so.16 no version information available
Arg! This abomination 5.5 is causing more headaches, postfix will not run, I've heard dovecot may not either, amongst others postconf: /usr/lib/libmysqlclient.so.16: no version information available (required by postcon /etc/init.d/postfix start * Starting Postfix Mail Transport Agent postfix postconf: /usr/lib/libmysqlclient.so.16: no version information available (required by postconf) /usr/sbin/postconf: /usr/lib/libmysqlclient.so.16: no version information available (required by /usr/sbin/postconf) /usr/sbin/postconf: /usr/lib/libmysqlclient.so.16: no version information available (required by /usr/sbin/postconf) [fail] *sigh* Why was this removed, or is this another side affect of that amazing winblozy P.O.S cmake? signature.asc Description: This is a digitally signed message part
Re: libmysqlclient.so.16 no version information available
You need mysql-5.1 compat-libs package or rebuild applications against 5.5 for feddora/rhel type compat-mysql51 in google there are packages from remi since he builds 5.5 this is nothing new and was the same with 5.1 while applications was linked against 5.0 Am 31.01.2011 09:24, schrieb Noel Butler: Arg! This abomination 5.5 is causing more headaches, postfix will not run, I've heard dovecot may not either, amongst others postconf: /usr/lib/libmysqlclient.so.16: no version information available (required by postcon /etc/init.d/postfix start * Starting Postfix Mail Transport Agent postfix postconf: /usr/lib/libmysqlclient.so.16: no version information available (required by postconf) /usr/sbin/postconf: /usr/lib/libmysqlclient.so.16: no version information available (required by /usr/sbin/postconf) /usr/sbin/postconf: /usr/lib/libmysqlclient.so.16: no version information available (required by /usr/sbin/postconf) [fail] *sigh* Why was this removed, or is this another side affect of that amazing winblozy P.O.S cmake? -- Mit besten Grüßen, Reindl Harald the lounge interactive design GmbH A-1060 Vienna, Hofmühlgasse 17 CTO / software-development / cms-solutions p: +43 (1) 595 3999 33, m: +43 (676) 40 221 40 icq: 154546673, http://www.thelounge.net/ signature.asc Description: OpenPGP digital signature
Re: libmysqlclient.so.16 no version information available
On Mon, 2011-01-31 at 10:52 +0100, Reindl Harald wrote: You need mysql-5.1 compat-libs package or rebuild applications against 5.5 for feddora/rhel type compat-mysql51 in google there are packages from remi since he builds 5.5 this is nothing new and was the same with 5.1 while applications was linked against 5.0 HUH? These are all source builds, I did not have this problem previously, I don't use package maintainers versions. I have source builds of mysql, postfix, dovecot, apache, php, bind - pretty much all the common main daemons, i don't trust distro butchers , err, i mean maintainers, for these critical apps. thanks anyway. Am 31.01.2011 09:24, schrieb Noel Butler: Arg! This abomination 5.5 is causing more headaches, postfix will not run, I've heard dovecot may not either, amongst others postconf: /usr/lib/libmysqlclient.so.16: no version information available (required by postcon /etc/init.d/postfix start * Starting Postfix Mail Transport Agent postfix postconf: /usr/lib/libmysqlclient.so.16: no version information available (required by postconf) /usr/sbin/postconf: /usr/lib/libmysqlclient.so.16: no version information available (required by /usr/sbin/postconf) /usr/sbin/postconf: /usr/lib/libmysqlclient.so.16: no version information available (required by /usr/sbin/postconf) [fail] *sigh* Why was this removed, or is this another side affect of that amazing winblozy P.O.S cmake? signature.asc Description: This is a digitally signed message part
Re: libmysqlclient.so.16 no version information available
Have you rebuilt all depending applications AFTER rebuild of mysql 5.5? BTW: I also make my own source-builds with optimized flags but not dumb configure make, the better way is to build clean distro-packages and install them with the package-manager, this way you would get not installed the packages as long dependencies are clean Am 31.01.2011 11:38, schrieb Noel Butler: On Mon, 2011-01-31 at 10:52 +0100, Reindl Harald wrote: You need mysql-5.1 compat-libs package or rebuild applications against 5.5 for feddora/rhel type compat-mysql51 in google there are packages from remi since he builds 5.5 this is nothing new and was the same with 5.1 while applications was linked against 5.0 HUH? These are all source builds, I did not have this problem previously, I don't use package maintainers versions. I have source builds of mysql, postfix, dovecot, apache, php, bind - pretty much all the common main daemons, i don't trust distro butchers , err, i mean maintainers, for these critical apps. thanks anyway. Am 31.01.2011 09:24, schrieb Noel Butler: Arg! This abomination 5.5 is causing more headaches, postfix will not run, I've heard dovecot may not either, amongst others postconf: /usr/lib/libmysqlclient.so.16: no version information available (required by postcon /etc/init.d/postfix start * Starting Postfix Mail Transport Agent postfix postconf: /usr/lib/libmysqlclient.so.16: no version information available (required by postconf) /usr/sbin/postconf: /usr/lib/libmysqlclient.so.16: no version information available (required by /usr/sbin/postconf) /usr/sbin/postconf: /usr/lib/libmysqlclient.so.16: no version information available (required by /usr/sbin/postconf) [fail] *sigh* Why was this removed, or is this another side affect of that amazing winblozy P.O.S cmake? -- Mit besten Grüßen, Reindl Harald the lounge interactive design GmbH A-1060 Vienna, Hofmühlgasse 17 CTO / software-development / cms-solutions p: +43 (1) 595 3999 33, m: +43 (676) 40 221 40 icq: 154546673, http://www.thelounge.net/ signature.asc Description: OpenPGP digital signature
Re: libmysqlclient.so.16 no version information available
On Mon, 2011-01-31 at 11:42 +0100, Reindl Harald wrote: Have you rebuilt all depending applications AFTER rebuild of mysql 5.5? yes, built 5.5 a month ago, only today rebuilt postfix (upgraded 2.7.2 to 2.8.0) This is a common problem, google fu indicates others have same problem, some of them claim reverting to 5.5.7 corrects this error, there was major changes from 5.5.7 to 5.5.8, but I don't see the sense in downgrading to what was regarded as unstable mysql version to correct it. just as well this is on a dev testbed and not production, more of a reason production will stay on 5.1 I think. BTW: I also make my own source-builds with optimized flags but not dumb configure make, the better way is to build clean distro-packages and install them with the package-manager, this way you would I totally disagree. but thats the beauty about open source, each to their own. when there is only one version of the lib installed it should not be an issue, I've been building tarballs for 20 years, so do understand how the OS works and how to best use configure :) Am 31.01.2011 11:38, schrieb Noel Butler: On Mon, 2011-01-31 at 10:52 +0100, Reindl Harald wrote: You need mysql-5.1 compat-libs package or rebuild applications against 5.5 for feddora/rhel type compat-mysql51 in google there are packages from remi since he builds 5.5 this is nothing new and was the same with 5.1 while applications was linked against 5.0 HUH? These are all source builds, I did not have this problem previously, I don't use package maintainers versions. I have source builds of mysql, postfix, dovecot, apache, php, bind - pretty much all the common main daemons, i don't trust distro butchers , err, i mean maintainers, for these critical apps. thanks anyway. Am 31.01.2011 09:24, schrieb Noel Butler: Arg! This abomination 5.5 is causing more headaches, postfix will not run, I've heard dovecot may not either, amongst others postconf: /usr/lib/libmysqlclient.so.16: no version information available (required by postcon /etc/init.d/postfix start * Starting Postfix Mail Transport Agent postfix postconf: /usr/lib/libmysqlclient.so.16: no version information available (required by postconf) /usr/sbin/postconf: /usr/lib/libmysqlclient.so.16: no version information available (required by /usr/sbin/postconf) /usr/sbin/postconf: /usr/lib/libmysqlclient.so.16: no version information available (required by /usr/sbin/postconf) [fail] *sigh* Why was this removed, or is this another side affect of that amazing winblozy P.O.S cmake? signature.asc Description: This is a digitally signed message part
Re: libmysqlclient.so.16 no version information available
Noel, all, Noel Butler wrote: Arg! This abomination 5.5 is causing more headaches, postfix will not run, I've heard dovecot may not either, amongst others postconf: /usr/lib/libmysqlclient.so.16: no version information available (required by postcon /etc/init.d/postfix start * Starting Postfix Mail Transport Agent postfix postconf: /usr/lib/libmysqlclient.so.16: no version information available (required by postconf) /usr/sbin/postconf: /usr/lib/libmysqlclient.so.16: no version information available (required by /usr/sbin/postconf) /usr/sbin/postconf: /usr/lib/libmysqlclient.so.16: no version information available (required by /usr/sbin/postconf) [fail] *sigh* Why was this removed, or is this another side affect of that amazing winblozy P.O.S cmake? could you please specify exactly what you feel was removed from 5.5, but present in 5.1? I'd also like to know on which platform postconf runs which commands to check libmysqlclient. I am not aware of a versioning change around libmysqlclient, especially MySQL 5.1 and 5.5 both use the same version 16 for this library (the interface didn't change). This is also the reason why shared-compat packages of MySQL 5.5 do not include the client libraries shipped with 5.1, only those of 5.0 and earlier: The MySQL 5.5 ones can replace those of 5.1 directly. What was changed, however, is that now the client library is only built thread-safe: whereas previous versions had separate libmysqlclient.* and libmysqlclient_r.*, these are now (in 5.5) symbolic links to the same file. It is of course possible that cmake does handle some aspects different from the way make and the autotools did it, but that this difference does not matter to the way we do release builds (or was overcome). Especially, the .la files are not created any more. HTH, Jörg -- Joerg Bruehe, MySQL Build Team, joerg.bru...@oracle.com ORACLE Deutschland B.V. Co. KG, Komturstrasse 18a, D-12099 Berlin Geschaeftsfuehrer: Juergen Kunz, Marcel v.d. Molen, Alexander v.d. Ven Amtsgericht Muenchen: HRA 95603 -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Re: libmysqlclient.so.16 no version information available
Harald, Reindl Harald wrote: You need mysql-5.1 compat-libs package or rebuild applications against 5.5 Your advice is correct in general, but not in this case: 1) Noel builds from source, as he writes later. 2) Both MySQL 5.1 and 5.5 come with version 16 of libmysqlclient, so an application built against MySQL 5.1 can directly use that of 5.5. [[...]] this is nothing new and was the same with 5.1 while applications was linked against 5.0 Right, MySQL 5.0 - 5.1 had the transition 15 - 16 for libmysqlclient[_r].so. Regards, Jörg -- Joerg Bruehe, MySQL Build Team, joerg.bru...@oracle.com ORACLE Deutschland B.V. Co. KG, Komturstrasse 18a, D-12099 Berlin Geschaeftsfuehrer: Juergen Kunz, Marcel v.d. Molen, Alexander v.d. Ven Amtsgericht Muenchen: HRA 95603 -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Re: libmysqlclient.so.16 no version information available
Am 31.01.2011 19:31, schrieb Joerg Bruehe: 2) Both MySQL 5.1 and 5.5 come with version 16 of libmysqlclient, so an application built against MySQL 5.1 can directly use that of 5.5 In theory! Build a mysql 5.5 rpm for fedora 13 and install it No way - Without the compat-package it will not work signature.asc Description: OpenPGP digital signature
Re: Autostart not working for me in 5.5.8 version
Hi Noel, all! Noel Butler wrote: On Thu, 2010-12-16 at 10:08 -0300, Alejandro Bednarik wrote: You are right. In previous version init script have a default value, now is empty. mysql 5.1..53 - basedir=/usr/local/mysql mysql-5.5.8 - basedir=. /me ponders at who the IDIOT is that decided that cmake is the way of mysql now. I mean WTF... It was the ones who realized that two different build mechanisms (autotools for Unix, cmake for Windows) will always cause divergence, when one is maintained with a change and the other isn't. Being database people, we know the importance of consistency ;) [[...]] /me sticks with 5.1 Do as you like, but realize that 5.1 won't see major development in the future and will be put on extended support only in due time. So if anybody encounters differences between 5.1 and 5.5 in such settings which aren't documented (= by intention, or unavoidable), please file bugs to get them fixed. Jörg -- Joerg Bruehe, MySQL Build Team, joerg.bru...@oracle.com ORACLE Deutschland B.V. Co. KG, Komturstrasse 18a, D-12099 Berlin Geschaeftsfuehrer: Juergen Kunz, Marcel v.d. Molen, Alexander v.d. Ven Amtsgericht Muenchen: HRA 95603 -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Re: Autostart not working for me in 5.5.8 version
Hi Joerg, On Mon, 2010-12-20 at 18:59 +0100, Joerg Bruehe wrote: Hi Noel, all! Noel Butler wrote: On Thu, 2010-12-16 at 10:08 -0300, Alejandro Bednarik wrote: You are right. In previous version init script have a default value, now is empty. mysql 5.1..53 - basedir=/usr/local/mysql mysql-5.5.8 - basedir=. /me ponders at who the IDIOT is that decided that cmake is the way of mysql now. I mean WTF... It was the ones who realized that two different build mechanisms (autotools for Unix, cmake for Windows) will always cause divergence, when one is maintained with a change and the other isn't. Being database people, we know the importance of consistency ;) I can tell its done by windowsy people, it has pretty colours :) seriously though , it's almost as bad as trying to figure out what to give postifx hehe And in the real world, many sysadmins have to build the database servers for the database admins, I've made my opinion known about cmake so I'll leave my cursing at that. /me sticks with 5.1 Do as you like, but realize that 5.1 won't see major development in the future and will be put on extended support only in due time. For what we use it for, it's likely fine, (user auth/radius/web/mail etc etc etc) nothing complex. So if anybody encounters differences between 5.1 and 5.5 in such settings which aren't documented (= by intention, or unavoidable), please file bugs to get them fixed. Well, the documentation could be a little more in depth, if you remove method A, and if method B is completely compatible, then there must be detailed information, it is not very good for time management to spend hours looking over the website, yes forge.mysql.com has a handy reference, but the bit about replacing, for instance plugins=max, it is not clear what we need to include, we know what is default, and some examples of to add given the example given, but no reference to the max server, without time consuming research to see what plugins=max includes, compare, then find equivalent DINSTALL_blah=1's to add, I think it is a backwards step, and you're likely to see more cussing as more go to upgrade. Nice thing though, my original my.cnf didnt cause it to bail out upon restart, however I only installed it on one very light use server. want to lay with it a bit before it goes on anything too serious. Cheers attachment: face-smile.png signature.asc Description: This is a digitally signed message part
MySQL 5.5.8 GA's library files have not version information by default?
hi,everyone today, i installed the MySQL 5.5.8 from source tarball,everything looks like OK. and when i try to start PHP-FPM process,the error printed below: [r...@powerpc mysql-5.5.8]# php-fpm php-fpm: /usr/local/mysql/lib/libmysqlclient.so.16: no version information available (required by php-fpm) i do not know how to solve it, does anyone hit it?want help ,thanks Best regards, Sharl.Jimh.Tsin (From China **Obviously Taiwan INCLUDED**) -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Re: Autostart not working for me in 5.5.8 version
You are right. In previous version init script have a default value, now is empty. mysql 5.1..53 - basedir=/usr/local/mysql mysql-5.5.8 - basedir=. Cheers. On Thu, Dec 16, 2010 at 12:42 AM, Yangontha Maung yangontha5...@yahoo.comwrote: Hi, I will answer my own question. I have to add a line in (/etc/my.cnf) as follows:- basedir=/usr/local/mysql I have installed mysql in /usr/local/mysql. But the same was done in previous versions and I do not need to add this. Anyway, now that it is working. rgds, --- On Thu, 12/16/10, Yangontha Maung yangontha5...@yahoo.com wrote: From: Yangontha Maung yangontha5...@yahoo.com Subject: Autostart not working for me in 5.5.8 version To: mysql@lists.mysql.com Date: Thursday, December 16, 2010, 11:14 AM Hi, Please help to set up the autostart of mysql when the Linux server starts. It is not working for me after installing to version 5.5.8. I have been using different versions of mysql for quite some time with different servers, Fedora versions. All these are working for autostart. But for this 5.5.8 I tried on two servers and both are not working for autostart. Please help. The following are my details:=- Installed on Fedora 12 Linux Previously mysql 5.1.48 is working and autorestart is also working. Now installed 5.5.8 Using manual starting is working /usr/local/mysql/bin/mysqld_safe But the auto start is not working. I have done this $ cp /usr/local/mysql/bin/support-files/mysql.server /etc/init.d/mysql $ chmod +x /etc/init.d/mysql $ ln –s /etc/init.d/mysql /etc/rc3.d/S99mysql $ ln –s /etc/init.d/mysql /etc/rc5.d/S99mysql $ ln –s /etc/init.d/mysql /etc/rc0.d/K01mysql thanks and rgds, -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/mysql?unsub=yangontha5...@yahoo.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=alejand...@olx.com -- Infrastructure Team OLX Inc. Buenos Aires - Argentina Phone : 54.11.4775.6696 Mobile : 54.911.50436059 Email: alejand...@olx.com
Autostart not working for me in 5.5.8 version
Hi, Please help to set up the autostart of mysql when the Linux server starts. It is not working for me after installing to version 5.5.8. I have been using different versions of mysql for quite some time with different servers, Fedora versions. All these are working for autostart. But for this 5.5.8 I tried on two servers and both are not working for autostart. Please help. The following are my details:=- Installed on Fedora 12 Linux Previously mysql 5.1.48 is working and autorestart is also working. Now installed 5.5.8 Using manual starting is working /usr/local/mysql/bin/mysqld_safe But the auto start is not working. I have done this $ cp /usr/local/mysql/bin/support-files/mysql.server /etc/init.d/mysql $ chmod +x /etc/init.d/mysql $ ln –s /etc/init.d/mysql /etc/rc3.d/S99mysql $ ln –s /etc/init.d/mysql /etc/rc5.d/S99mysql $ ln –s /etc/init.d/mysql /etc/rc0.d/K01mysql thanks and rgds, -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Re: Autostart not working for me in 5.5.8 version
Hi, I will answer my own question. I have to add a line in (/etc/my.cnf) as follows:- basedir=/usr/local/mysql I have installed mysql in /usr/local/mysql. But the same was done in previous versions and I do not need to add this. Anyway, now that it is working. rgds, --- On Thu, 12/16/10, Yangontha Maung yangontha5...@yahoo.com wrote: From: Yangontha Maung yangontha5...@yahoo.com Subject: Autostart not working for me in 5.5.8 version To: mysql@lists.mysql.com Date: Thursday, December 16, 2010, 11:14 AM Hi, Please help to set up the autostart of mysql when the Linux server starts. It is not working for me after installing to version 5.5.8. I have been using different versions of mysql for quite some time with different servers, Fedora versions. All these are working for autostart. But for this 5.5.8 I tried on two servers and both are not working for autostart. Please help. The following are my details:=- Installed on Fedora 12 Linux Previously mysql 5.1.48 is working and autorestart is also working. Now installed 5.5.8 Using manual starting is working /usr/local/mysql/bin/mysqld_safe But the auto start is not working. I have done this $ cp /usr/local/mysql/bin/support-files/mysql.server /etc/init.d/mysql $ chmod +x /etc/init.d/mysql $ ln –s /etc/init.d/mysql /etc/rc3.d/S99mysql $ ln –s /etc/init.d/mysql /etc/rc5.d/S99mysql $ ln –s /etc/init.d/mysql /etc/rc0.d/K01mysql thanks and rgds, -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/mysql?unsub=yangontha5...@yahoo.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Compile error on MySQL 5.5.7 rc version,help!
hi,everyone: i need your helps,really!! this is my second compiling-failed on building my own MySQL already.previous is version 5.5.6 rc,now is 5.5.7 rc. my build environment is centos 5 x86,full name is Linux PowerPC 2.6.18-194.8.1.el5.028stab070.5 #1 SMP Fri Sep 17 19:10:36 MSD 2010 i686 i686 i386 GNU/Linux. i download the last dev branch of version 5.5.x's source tarball from MySQL's http mirror,then unpack it. this is my configure strings: [r...@powerpc mysql-5.5.7-rc]# ./configure \ --prefix=/usr/local/mysql \ --exec-prefix=/usr/local \ --sysconfdir=/etc/sysconfig/mysql \ --localstatedir=/var/run \ --enable-profiling \ --disable-largefile \ --disable-ipv6 \ --with-charset=utf8 \ --with-extra-charsets=all \ --with-unix-socket-path=/tmp/mysql.sock \ --with-mysqld-user=mysql \ --with-zlib-dir=bundled \ --with-low-memory \ --with-embedded-server \ --without-geometry \ --with-embedded-privilege-control \ --without-docs \ --without-man no error warning reported this step. then going to MAKE it,and the errors below break it. regex -I../../sql -I. -g -O2 -DUNIV_LINUX -MT mi_static.o -MD -MP -MF .deps/mi_static.Tpo -c -o mi_static.o mi_static.c mi_static.c:40: error: conflicting types for ‘myisam_max_temp_length’ ../../include/myisam.h:254: error: previous declaration of ‘myisam_max_temp_length’ was here make[2]: *** [mi_static.o] Error 1 make[2]: Leaving directory `/root/mysql-5.5.7-rc/storage/myisam' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/root/mysql-5.5.7-rc/storage' make: *** [all-recursive] Error 1 what should i do now? thanks for any tips. -- Best regards, Sharl.Jimh.Tsin (From China *Obviously Taiwan INCLUDED*) -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Re: MySQL DB Version
How can we get our MySQL db upgraded to this version or greater ? You can also find these at: http://dev.mysql.com/downloads/ Cheers, Craig -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
MySQL DB Version
Account Number : uk600724 Dear Sir/Madam, The MySQL database version which you have supplied to us is version 5.0.77. However, it would appear that we require version to be at least 5.1.43. How can we get our MySQL db upgraded to this version or greater ? Regards Neil Tompkins
