[ANN] [Qt ORM] QxOrm 1.4.5 and QxEntityEditor 1.2.3 released : support MongoDB database and code source now on GitHub
Hello, *QxOrm library 1.4.5* and *QxEntityEditor application 1.2.3* just released : https://www.qxorm.com/ *QxOrm library 1.4.5 changes log :* * - Support MongoDB database : QxOrm library becomes a C++/Qt Object Document Mapper ODM library !- For more details about MongoDB integration, see QxOrm manual (https://www.qxorm.com/qxorm_en/manual.html#manual_95 <https://www.qxorm.com/qxorm_en/manual.html#manual_95>) and new sample project available in ./test/qxBlogMongoDB/ directory- QxOrm library is now available on GitHub (official repository) : https://github.com/QxOrm/QxOrm <https://github.com/QxOrm/QxOrm>- Fix an issue in qx::IxSqlQueryBuilder class when QxOrm library is used in a multi-thread environment- Support latest version of boost (1.66)- Update boost portable binary serialization classes to version 5.1 (provided by https://archive.codeplex.com/?p=epa <https://archive.codeplex.com/?p=epa>)- Fix an issue building SQL query for Oracle database (doesn't support AS keyword for table alias)- Improve qx::QxClassX::registerAllClasses() function : possibility to initialize all relations (useful to work with introspection engine)- Improve qx::IxPersistable interface : provide new methods toJson() / fromJson()- Improve documentation/website : change http://www.qxorm.com <http://www.qxorm.com/> by https://www.qxorm.com <http://www.qxorm.com/> everywhere- Fix fetching relations with soft delete putting SQL condition in the JOIN part instead of WHERE part- Fix SQL generator for Oracle database : use new limit/pagination syntax (version Oracle > 12.1)- Improve SQL generator interface : add 'onBeforeSqlPrepare()' method to modify/log SQL queries in custom classes- Add an option in qx::QxSqlDatabase class to format SQL query (pretty-printing) before logging it (can be customized creating a qx::dao::detail::IxSqlGenerator sub-class)- Fix an issue with boost/std::optional (to manage NULL database values) and some databases : if optional is empty, then create a NULL QVariant based on QVariant::Type- Add an option in qx::QxSqlDatabase class to insert square brackets (or any other delimiters) in SQL queries for table name and/or column name (to support specific database keywords)- Improve introspection engine : add getType() method in qx::IxDataMember interface to get C++ type of a property dynamically- Improve qx::QxSqlDatabase singleton settings class to make easier working with several databases : now there are 3 levels of settings : global >> per thread >> per database (see 'bJustForCurrentThread' and 'pJustForThisDatabase' optional parameters in all set() methods)- Fix QxOrm.pri for MinGW compiler on Windows : an issue could occurred to export some symbols from shared library (some Qt signals for example)- Add an option in qx::QxSqlDatabase singleton class to display only slow SQL queries (see setTraceSqlOnlySlowQueriesDatabase() and setTraceSqlOnlySlowQueriesTotal() methods)* *QxEntityEditor application 1.2.3 changes log :* *- Fix a crash which appears sometimes with complex database schema to draw relationships (orthogonal way)- Improve QxEntityEditor command line parameters : possibility to import/export without using GUI (useful to manage a Jenkins server for example)- For more details about command line parameters, go to QxEntityEditor documentation : https://www.qxorm.com/qxorm_en/manual_qxee.html#qxee_command_line <https://www.qxorm.com/qxorm_en/manual_qxee.html#qxee_command_line>* You can download latest version of QxOrm library and QxEntityEditor application on QxOrm website : https://www.qxorm.com/ Regards, Lionel Marty - QxOrm library
ANN: Database Workbench 5.2 now includes PostgreSQL support
Upscene Productions is proud to announce the availability of the next version of the popular multi-DBMS development tool: " Database Workbench 5.2 " This release includes support for PostgreSQL and adds several other features. Database Workbench 5 comes in multiple editions with different pricing models, there's always a version that suits you! "Version 5 included many new features", says Martijn Tonies, founder of Upscene Productions. "It added code editor features, has diagramming improvements, multiple editions, is fully HiDPI aware and offers tunnelling for MySQL and MariaDB connections. The most recent version adds support for PostgreSQL, as requested by many of our customers." For more information, see What's new in Database Workbench 5? ( http://www.upscene.com/database_workbench/whatsnew ) Database Workbench supports MySQL, MariaDB, Firebird, Oracle, MS SQL Server, SQL Anywhere, NexusDB, PostgreSQL and InterBase, comes in multiple editions and is licensed based on selectable modules. It includes tools for database design, database maintenance, testing, data transfer, data import & export, database migration, database compare and numerous other tools. About Database Workbench Database Workbench is a database developer tool, over 12 years in the making and is being used by thousands of developers across the globe who have come to rely on it every day. From database design, implementation, to testing and debugging, it will aid you in your daily database work. About Upscene Productions Based in The Netherlands, Europe, this small but dedicated company has been providing database developers with useful tools for over 14 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.
Re: commands out of sync, you can't run this command now'
Am 08.01.2016 um 10:14 schrieb Nitin Mehta: Looks like some kind of locking mechanism in the application. Should not be a database issue. no true - this is a native mysql error message! honestly both of you should have used Google http://dev.mysql.com/doc/refman/5.7/en/commands-out-of-sync.html http://stackoverflow.com/questions/15798762/mysqli-commands-out-of-sync-you-cant-run-this-command-now On Friday, January 8, 2016 10:47 AM, geetanjali mehra <mailtogeetanj...@gmail.com> wrote: Hi all, Suddenly I have started getting below error from our web site: 'commands out of sync, you can't run this command now' This error is generated sometimes when opening a page ,and immediately after refreshing the page, error gone. Can you please help me to troubleshoot this issue, so that above error disappears permanently? Is it a database issue or application side issue? signature.asc Description: OpenPGP digital signature
Re: commands out of sync, you can't run this command now'
On 1/8/2016 3:14, Nitin Mehta wrote: Looks like some kind of locking mechanism in the application. Should not be a database issue. On Friday, January 8, 2016 10:47 AM, geetanjali mehra <mailtogeetanj...@gmail.com> wrote: Hi all, Suddenly I have started getting below error from our web site: 'commands out of sync, you can't run this command now' This error is generated sometimes when opening a page ,and immediately after refreshing the page, error gone. Can you please help me to troubleshoot this issue, so that above error disappears permanently? Is it a database issue or application side issue? http://dev.mysql.com/doc/refman/5.7/en/commands-out-of-sync.html PB - Best Regards, Geetanjali Mehra Senior Database Administrator -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
commands out of sync, you can't run this command now'
Hi all, Suddenly I have started getting below error from our web site: 'commands out of sync, you can't run this command now' This error is generated sometimes when opening a page ,and immediately after refreshing the page, error gone. Can you please help me to troubleshoot this issue, so that above error disappears permanently? Is it a database issue or application side issue? Best Regards, Geetanjali Mehra Senior Database Administrator
Re: database developer tool Database Workbench 5 now available
Hello Jan, list, From: Martijn Tonies (Upscene Productions) m.ton...@upscene.com Database Workbench now comes in multiple editions with different pricing models, there's always a version that suits you! Unless you don't do Winblows. Please put Windows dependency clearly in your announcements and on your website. I couldn't find it anywhere, until I attempted a download, and got a useless .EXE file. The announcement said: ... and works fine under Wine on Linux. Several of our customers are long-time Linux users and are very happy with Database Workbench. See also: http://www.upscene.com/company/support/database_workbench_5_on_wine_ubuntu14 Hope this helps. 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: database developer tool Database Workbench 5 now available
From: m.ton...@upscene.com To: j...@ecoreality.org; mysql@lists.mysql.com Subject: Re: database developer tool Database Workbench 5 now available Date: Fri, 5 Sep 2014 07:57:37 +0200 Hello Jan, list, From: Martijn Tonies (Upscene Productions) m.ton...@upscene.com Database Workbench now comes in multiple editions with different pricing models, there's always a version that suits you! Unless you don't do Winblows. Please put Windows dependency clearly in your announcements and on your website. I couldn't find it anywhere, until I attempted a download, and got a useless .EXE file. MGMy development is identical ..Development on Windows..Production on Linux MGWhen google routes me to Vladimir Putins site for Official Windows Mysql Stack you download god knows what MGsolution is to give the customer an in-between solution such as mysqld, mysqladmin and mysql shell scripts that will work under Windows cygwin MGThe Database Workbench version5 MySQL plugin README should detail *a seamless installation* for Windows cygwin MGif I have to make changes to my.ini or etc/init.d the readme should be specific on what those changes should be MGReadme should also be specific on how to successfully test mysql ports (presumably 3306)..i assume netstat -a | grep 3306? MGThanks The announcement said: ... and works fine under Wine on Linux. Several of our customers are long-time Linux users and are very happy with Database Workbench. See also: http://www.upscene.com/company/support/database_workbench_5_on_wine_ubuntu14 Hope this helps. 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: database developer tool Database Workbench 5 now available
MGMy development is identical ..Development on Windows..Production on Linux MGWhen google routes me to Vladimir Putins site for Official Windows Mysql Stack you download god knows what MGsolution is to give the customer an in-between solution such as mysqld, mysqladmin and mysql shell scripts that will work under Windows cygwin MGThe Database Workbench version5 MySQL plugin README should detail *a seamless installation* for Windows cygwin MGif I have to make changes to my.ini or etc/init.d the readme should be specific on what those changes should be MGReadme should also be specific on how to successfully test mysql ports (presumably 3306)..i assume netstat -a | grep 3306? MGThanks Martin, I have no idea what the above means -- Database Workbench is a client side Windows based database design and development tool, no need to Cygwin or modify my.ini 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
ANN: database developer tool Database Workbench 5 now available
Upscene releases Database Workbench 5 Upscene Productions is proud to announce the availability of the next major version of the popular multi-DBMS development tool: Database Workbench 5 There have been numerous improvements to existing tools and the new, more consistent user interface is better than ever and works fine under Wine on Linux. Database Workbench now comes in multiple editions with different pricing models, there's always a version that suits you! There is so much new in Database Workbench 5, I don't know where to start, says Martijn Tonies, founder of Upscene Productions. This release adds code editor features, has diagramming improvements, comes in multiple editions, is fully HiDPI aware and offers tunneling for MySQL and MariaDB connections. It all was a lot of work, but it was worth it! We worked closely with out customer and implemented many of their requests and for new users, we offer multiple editions to suit their development needs. From design to productivity, there's new features and improvements in almost everything! For more information, see What's new in Database Workbench 5? ( http://www.upscene.com/database_workbench/whatsnew ) Database Workbench supports MySQL, MariaDB, Firebird, Oracle, MS SQL Server, SQL Anywhere, NexusDB and InterBase, comes in multiple editions and is licensed based on selectable modules. It includes tools for database design, database maintenance, testing, data transfer, data import export, database migration, database compare and numerous other tools. About Database Workbench Database Workbench is a database developer tool, over 10 years in the making and is being used by thousands of developers across the globe who have come to rely on it every day. From database design, implementation, to testing and debugging, it will aid you in your daily database work. About Upscene Productions Based in The Netherlands, Europe, this small but dedicated company has been providing database developers with useful tools for over 12 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.
Re: ANN: database developer tool Database Workbench 5 now available
From: Martijn Tonies (Upscene Productions) m.ton...@upscene.com Database Workbench now comes in multiple editions with different pricing models, there's always a version that suits you! Unless you don't do Winblows. Please put Windows dependency clearly in your announcements and on your website. I couldn't find it anywhere, until I attempted a download, and got a useless .EXE file. The record is clear that left to their own devices, the automobile manufacturers lack the wisdom or the will or both to switch decisively to the production of inexpensive, compact, energy-saving cars appropriate to our present needs. -- Donald E. Weeden 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: Database Workbench 4.4.7, the multi-DBMS IDE now available!
ANN: Database Workbench 4.4.7, the multi-DBMS IDE now available! Ladies, gentlemen, Upscene Productions is proud to announce the next version of the popular Windows-based multi-DBMS development tool: Database Workbench 4.4.7 Pro For more information, see http://www.upscene.com/go/?go=newsid=20140617 Database Workbench supports: - Borland InterBase ( 6.x and up ) - Firebird ( 1.x and up ) - MS SQL Server/MSDE ( 7 and up ) - MySQL 4.x and up - Oracle Database ( 8i and up ) - Sybase SQL Anywhere ( 9 and up ) - NexusDB ( 3.0 and up ) Thank you for your support, Martijn Tonies Database Workbench - the database developer tool for professionals Upscene Productions http://www.upscene.com
ANN: Database Workbench 4.4.6, the multi-DBMS IDE now available!
ANN: Database Workbench 4.4.6, the multi-DBMS IDE now available! Ladies, gentlemen, Upscene Productions is proud to announce the next version of the popular Windows-based multi-DBMS development tool: Database Workbench 4.4.6 Pro For more information, see http://www.upscene.com/go/?go=newsid=20140429 The FREE Lite Editions will be released at a later stage. Database Workbench supports: - Borland InterBase ( 6.x and up ) - Firebird ( 1.x and up ) - MS SQL Server/MSDE ( 7 and up ) - MySQL 4.x and up - Oracle Database ( 8i and up ) - Sybase SQL Anywhere ( 9 and up ) - NexusDB ( 3.0 and up ) Thank you for your support, Martijn Tonies Database Workbench - the database developer tool for professionals Upscene Productions http://www.upscene.com
ANN: Database Workbench 4.4.4, the multi-DBMS IDE now available!
ANN: Database Workbench 4.4.4, the multi-DBMS IDE now available! Ladies, gentlemen, Upscene Productions is proud to announce the next version of the popular Windows-based multi-DBMS development tool: Database Workbench 4.4.4 Pro For more information, see http://www.upscene.com/go/?go=newsid=20140127 The FREE Lite Editions will be released at a later stage. Database Workbench supports: - Borland InterBase ( 6.x and up ) - Firebird ( 1.x and up ) - MS SQL Server/MSDE ( 7 and up ) - MySQL 4.x and up - Oracle Database ( 8i and up ) - Sybase SQL Anywhere ( 9 and up ) - NexusDB ( 3.0 and up ) Thank you for your support, Martijn Tonies Database Workbench - the database developer tool for professionals Upscene Productions http://www.upscene.com
ANN: Database Workbench 4.4.3, the multi-DBMS IDE now available!
ANN: Database Workbench 4.4.3, the multi-DBMS IDE now available! Ladies, gentlemen, Upscene Productions is proud to announce the next version of the popular Windows-based multi-DBMS development tool: Database Workbench 4.4.3 Pro This release fixes a blocking problem after a recent Windows XP security update. There's a 15% autumn discount until the end of November! For more information, see http://www.upscene.com/go/?go=newsid=20131127 The FREE Lite Editions are also updated, this includes several enhancements compared to the previous available Lite Editions. Database Workbench supports: - Borland InterBase ( 6.x and up ) - Firebird ( 1.x and up ) - MS SQL Server/MSDE ( 7 and up ) - MySQL 4.x and up - Oracle Database ( 8i and up ) - Sybase SQL Anywhere ( 9 and up ) - NexusDB ( 3.0 and up ) Thank you for your support, Martijn Tonies Database Workbench - the database developer tool for professionals Upscene Productions http://www.upscene.com
ANN: Database Workbench 4.4.2, the multi-DBMS IDE now available!
Ladies, gentlemen, Upscene Productions is proud to announce the next version of the popular Windows-based multi-DBMS development tool: Database Workbench 4.4.2 Pro There's a 15% autumn discount until the end of November! This release includes enhancements and fixes several bugs as reported by our users. For more information, see http://www.upscene.com/go/?go=newsid=20131024 The FREE Lite Editions will follow later. Database Workbench supports: - Borland InterBase ( 6.x and up ) - Firebird ( 1.x and up ) - MS SQL Server/MSDE ( 7 and up ) - MySQL 4.x and up - Oracle Database ( 8i and up ) - Sybase SQL Anywhere ( 9 and up ) - NexusDB ( 3.0 and up ) Thank you for your support, Martijn Tonies Database Workbench - the database developer tool for professionals Upscene Productions http://www.upscene.com
ANN: Database Workbench 4.4.1, the multi-DBMS IDE now available!
Ladies, gentlemen, Upscene Productions is proud to announce the next version of the popular Windows-based multi-DBMS development tool: Database Workbench 4.4.1 Pro This release includes new features and fixes several bugs as reported by the users. For more information, see http://www.upscene.com/go/?go=newsid=20130819 The FREE Lite Editions will follow later. Database Workbench supports: - Borland InterBase ( 6.x and up ) - Firebird ( 1.x and up ) - MS SQL Server/MSDE ( 7 and up ) - MySQL 4.x and up - Oracle Database ( 8i and up ) - Sybase SQL Anywhere ( 9 and up ) - NexusDB ( 3.0 and up ) Thank you for your support, Martijn Tonies Database Workbench - the database developer tool for professionals 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: Database Workbench 4.4.0, free Lite Editions now available!
ANN: Database Workbench 4.4.0, free Lite Editions now available! Ladies, gentlemen, Upscene Productions is proud to announce the next version of the popular Windows-based multi-DBMS development tool: Database Workbench 4.4.0 Lite Today we are making the free Lite Editions available for version 4.4.0 For more information, see http://www.upscene.com/go/?go=newsid=20130717 Database Workbench supports: - Borland InterBase ( 6.x - XE ) - Firebird ( 1.x, 2.x ) - MS SQL Server/MSDE ( 7, 2000, 2005, 2008 ) - MySQL 4.x, 5.x - Oracle Database ( 8i, 9i, 10g, 11g ) - Sybase SQL Anywhere ( 9, 10, 11 and 12 ) - NexusDB ( 3.0 and up ) The Lite Editions are available for: - InterBase - Firebird - MySQL Thank you for your support, Martijn Tonies Database Workbench - the database developer tool for professionals 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: NOW() is stuck...
hi, does the value change at all like below ? mysql show global variables like 'timestamp'; +---++ | Variable_name | Value | +---++ | timestamp | 1372404355 | +---++ 1 row in set (0.00 sec) mysql show global variables like 'timestamp'; +---++ | Variable_name | Value | +---++ | timestamp | 1372404371 | +---++ 1 row in set (0.00 sec) re, wh Am 27.06.2013 20:19, schrieb Andy Wallace: Benjamin - Unfortunately: mysql show global variables like 'timestamp'; +---++ | Variable_name | Value | +---++ | timestamp | 1372238834 | +---++ 1 row in set (0.00 sec) And: mysql set global timestamp = 0; ERROR 1228 (HY000): Variable 'timestamp' is a SESSION variable and can't be used with SET GLOBAL This does indeed persist across sessions. Any command line connection I make to the database shows the bad value for NOW(). I also tweaked the application code to include NOW() in an existing query, and the value returned to my PHP code is also the bad value. Thanks for looking, andy On 6/27/13 11:10 AM, Stillman, Benjamin wrote: It persists across sessions? Does this return anything: show global variables like 'timestamp'; Hopefully it returns: Empty set (0.00 sec) I vaguely remember reading about a bug in 5.1.4x with something to do with a global timestamp. I thought it only showed one though, and that you couldn't set it. If the above returned a timestamp and not an empty set, try: set global timestamp = 0; That should return something like this: ERROR 1228 (HY000): Variable 'timestamp' is a SESSION variable and can't be used with SET GLOBAL But if it returns: Query OK, 0 rows affected (0.00 sec) And then your queries return correct timestamps, you've found a bug. I'd hope that it would fail, but the only thing I can think of is if it's being set as a global variable. If this does fix your problem, and if you're using replication, you may have an issue with your replicated data. Replication uses timestamp extensively. On 6/27/13 1:44 PM, Andy Wallace awall...@ihouseweb.com wrote: But the question is how. I have nothing in the code that does it, or this would have been true for months instead of just the last 24 hours. In addition, this is currently set globally - no matter what connection to the database, it all comes up with this value. Which means that all my time-based queries no longer work correctly. Does your message suggest that setting it to 0 might clear the problem? On 6/27/13 10:31 AM, Stillman, Benjamin wrote: Timestamp is a session variable, so it must have been set to something other than 0 (1372228034 epoch is the date you're showing) in your current session. mysql set timestamp = 1372228034; Query OK, 0 rows affected (0.00 sec) mysql select now(), sysdate(); +-+-+ | now() | sysdate() | +-+-+ | 2013-06-26 02:27:14 | 2013-06-27 13:20:48 | +-+-+ 1 row in set (0.00 sec) mysql set timestamp = 0; Query OK, 0 rows affected (0.00 sec) mysql select now(), sysdate(); +-+-+ | now() | sysdate() | +-+-+ | 2013-06-27 13:21:34 | 2013-06-27 13:21:34 | +-+-+ 1 row in set (0.00 sec) Cliff's notes: set timestamp = 0; On 6/26/13 6:10 PM, Andy Wallace awall...@ihouseweb.com wrote: We've been having some issues with one of our MySQL servers lately, and currently the dang thing is stuck. For at least the last hour, NOW() is returning the same value: mysql select now(); +-+ | now() | +-+ | 2013-06-26 02:27:14 | +-+ The system variable timestamp also has that same time value stored in it. How can we kick this loose so that the values are more current with real time? (it is currently 3:08PM here, despite our MySQL instance thinking it's 2am. The system time on the machine is correct: $ date Wed Jun 26 15:08:56 PDT 2013 This is MySQL 5.1.46 running on solaris2.10. Any ideas short of restarting the MySQL engine? I'm willing to do that, but would much rather wait and not do it in the middle of the day. Thanks, Andy -- Andy Wallace iHOUSEweb, Inc. awall...@ihouseweb.com (866) 645-7700 ext 219 -- Sometimes it pays to stay in bed on Monday, rather than spending the rest of the week debugging Monday's code. - Christopher Thompson -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
Re: NOW() is stuck...
Avoid FreeBSD, Unless they did some real big magic on the scheduler of 9. Claudio On Jun 28, 2013 6:12 PM, Andy Wallace awall...@ihouseweb.com wrote: Nope, it was locked on a single value for about 36 hours, until we restarted the engine last night. Now it's running fine, and we're setting up a testbed to evaluate MySQL 5.6 and FreeBSD 9 (?) for replacing our current Solaris 10/MySQL 5.1.46 setup. On 6/28/13 12:44 AM, walter harms wrote: hi, does the value change at all like below ? mysql show global variables like 'timestamp'; +---++ | Variable_name | Value | +---++ | timestamp | 1372404355 | +---++ 1 row in set (0.00 sec) mysql show global variables like 'timestamp'; +---++ | Variable_name | Value | +---++ | timestamp | 1372404371 | +---++ 1 row in set (0.00 sec) re, wh Am 27.06.2013 20:19, schrieb Andy Wallace: Benjamin - Unfortunately: mysql show global variables like 'timestamp'; +---++ | Variable_name | Value | +---++ | timestamp | 1372238834 | +---++ 1 row in set (0.00 sec) And: mysql set global timestamp = 0; ERROR 1228 (HY000): Variable 'timestamp' is a SESSION variable and can't be used with SET GLOBAL This does indeed persist across sessions. Any command line connection I make to the database shows the bad value for NOW(). I also tweaked the application code to include NOW() in an existing query, and the value returned to my PHP code is also the bad value. Thanks for looking, andy On 6/27/13 11:10 AM, Stillman, Benjamin wrote: It persists across sessions? Does this return anything: show global variables like 'timestamp'; Hopefully it returns: Empty set (0.00 sec) I vaguely remember reading about a bug in 5.1.4x with something to do with a global timestamp. I thought it only showed one though, and that you couldn't set it. If the above returned a timestamp and not an empty set, try: set global timestamp = 0; That should return something like this: ERROR 1228 (HY000): Variable 'timestamp' is a SESSION variable and can't be used with SET GLOBAL But if it returns: Query OK, 0 rows affected (0.00 sec) And then your queries return correct timestamps, you've found a bug. I'd hope that it would fail, but the only thing I can think of is if it's being set as a global variable. If this does fix your problem, and if you're using replication, you may have an issue with your replicated data. Replication uses timestamp extensively. On 6/27/13 1:44 PM, Andy Wallace awall...@ihouseweb.com wrote: But the question is how. I have nothing in the code that does it, or this would have been true for months instead of just the last 24 hours. In addition, this is currently set globally - no matter what connection to the database, it all comes up with this value. Which means that all my time-based queries no longer work correctly. Does your message suggest that setting it to 0 might clear the problem? On 6/27/13 10:31 AM, Stillman, Benjamin wrote: Timestamp is a session variable, so it must have been set to something other than 0 (1372228034 epoch is the date you're showing) in your current session. mysql set timestamp = 1372228034; Query OK, 0 rows affected (0.00 sec) mysql select now(), sysdate(); +-+---**--+ | now() | sysdate() | +-+---**--+ | 2013-06-26 02:27:14 | 2013-06-27 13:20:48 | +-+---**--+ 1 row in set (0.00 sec) mysql set timestamp = 0; Query OK, 0 rows affected (0.00 sec) mysql select now(), sysdate(); +-+---**--+ | now() | sysdate() | +-+---**--+ | 2013-06-27 13:21:34 | 2013-06-27 13:21:34 | +-+---**--+ 1 row in set (0.00 sec) Cliff's notes: set timestamp = 0; On 6/26/13 6:10 PM, Andy Wallace awall...@ihouseweb.com wrote: We've been having some issues with one of our MySQL servers lately, and currently the dang thing is stuck. For at least the last hour, NOW() is returning the same value: mysql select now(); +-+ | now() | +-+ | 2013-06-26 02:27:14 | +-+ The system variable timestamp also has that same time value stored in it. How can we kick this loose so that the values are more current with real time? (it is currently 3:08PM here, despite our MySQL instance thinking it's 2am. The system time on the machine is correct: $ date Wed Jun 26 15:08:56 PDT 2013 This is MySQL 5.1.46 running on solaris2.10. Any ideas short of restarting
Re: NOW() is stuck...
Nope, it was locked on a single value for about 36 hours, until we restarted the engine last night. Now it's running fine, and we're setting up a testbed to evaluate MySQL 5.6 and FreeBSD 9 (?) for replacing our current Solaris 10/MySQL 5.1.46 setup. On 6/28/13 12:44 AM, walter harms wrote: hi, does the value change at all like below ? mysql show global variables like 'timestamp'; +---++ | Variable_name | Value | +---++ | timestamp | 1372404355 | +---++ 1 row in set (0.00 sec) mysql show global variables like 'timestamp'; +---++ | Variable_name | Value | +---++ | timestamp | 1372404371 | +---++ 1 row in set (0.00 sec) re, wh Am 27.06.2013 20:19, schrieb Andy Wallace: Benjamin - Unfortunately: mysql show global variables like 'timestamp'; +---++ | Variable_name | Value | +---++ | timestamp | 1372238834 | +---++ 1 row in set (0.00 sec) And: mysql set global timestamp = 0; ERROR 1228 (HY000): Variable 'timestamp' is a SESSION variable and can't be used with SET GLOBAL This does indeed persist across sessions. Any command line connection I make to the database shows the bad value for NOW(). I also tweaked the application code to include NOW() in an existing query, and the value returned to my PHP code is also the bad value. Thanks for looking, andy On 6/27/13 11:10 AM, Stillman, Benjamin wrote: It persists across sessions? Does this return anything: show global variables like 'timestamp'; Hopefully it returns: Empty set (0.00 sec) I vaguely remember reading about a bug in 5.1.4x with something to do with a global timestamp. I thought it only showed one though, and that you couldn't set it. If the above returned a timestamp and not an empty set, try: set global timestamp = 0; That should return something like this: ERROR 1228 (HY000): Variable 'timestamp' is a SESSION variable and can't be used with SET GLOBAL But if it returns: Query OK, 0 rows affected (0.00 sec) And then your queries return correct timestamps, you've found a bug. I'd hope that it would fail, but the only thing I can think of is if it's being set as a global variable. If this does fix your problem, and if you're using replication, you may have an issue with your replicated data. Replication uses timestamp extensively. On 6/27/13 1:44 PM, Andy Wallace awall...@ihouseweb.com wrote: But the question is how. I have nothing in the code that does it, or this would have been true for months instead of just the last 24 hours. In addition, this is currently set globally - no matter what connection to the database, it all comes up with this value. Which means that all my time-based queries no longer work correctly. Does your message suggest that setting it to 0 might clear the problem? On 6/27/13 10:31 AM, Stillman, Benjamin wrote: Timestamp is a session variable, so it must have been set to something other than 0 (1372228034 epoch is the date you're showing) in your current session. mysql set timestamp = 1372228034; Query OK, 0 rows affected (0.00 sec) mysql select now(), sysdate(); +-+-+ | now() | sysdate() | +-+-+ | 2013-06-26 02:27:14 | 2013-06-27 13:20:48 | +-+-+ 1 row in set (0.00 sec) mysql set timestamp = 0; Query OK, 0 rows affected (0.00 sec) mysql select now(), sysdate(); +-+-+ | now() | sysdate() | +-+-+ | 2013-06-27 13:21:34 | 2013-06-27 13:21:34 | +-+-+ 1 row in set (0.00 sec) Cliff's notes: set timestamp = 0; On 6/26/13 6:10 PM, Andy Wallace awall...@ihouseweb.com wrote: We've been having some issues with one of our MySQL servers lately, and currently the dang thing is stuck. For at least the last hour, NOW() is returning the same value: mysql select now(); +-+ | now() | +-+ | 2013-06-26 02:27:14 | +-+ The system variable timestamp also has that same time value stored in it. How can we kick this loose so that the values are more current with real time? (it is currently 3:08PM here, despite our MySQL instance thinking it's 2am. The system time on the machine is correct: $ date Wed Jun 26 15:08:56 PDT 2013 This is MySQL 5.1.46 running on solaris2.10. Any ideas short of restarting the MySQL engine? I'm willing to do that, but would much rather wait and not do it in the middle of the day. Thanks, Andy -- Andy Wallace iHOUSEweb, Inc. awall...@ihouseweb.com (866) 645-7700 ext 219 -- Sometimes it pays to stay in bed on Monday, rather than spending the rest of the week
Re: NOW() is stuck...
Hmm. Can't sleep, but also can't work a mail client, apparently :-) The thought was related to being in a transaction, but I tested it in the meantime, and it's not that. Ignore :-) - Original Message - From: Johan De Meersman vegiv...@tuxera.be To: Andy Wallace awall...@ihouseweb.com, mysql list mysql@lists.mysql.com Sent: Thursday, 27 June, 2013 1:36:31 AM Subject: Re: NOW() is stuck... Random I-can't-sleep thought: you wouldn't be testint this in a single -- 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: NOW() is stuck...
Problem is that I don't set the timestamp variable anywhere (except yesterday as a test to try and fix the problem). This is stuff that has been working correctly for many months. We had some network/dns and load issues over the last couple of days, and the mysql clock is frozen at: mysql select now(); +-+ | now() | +-+ | 2013-06-26 02:27:14 | +-+ While the machine/system date is: $ date Thu Jun 27 09:15:25 PDT 2013 I had actually planned to restart the mysql instance on this server last night, but there was a miscommunication, and that will have to wait for tonight. Once suggestion I got was to explicitly set the global timezone value, but can't do that because we didn't load the timezone tables. Guess we have to wait for tonight. thanks, guys Andy On 6/26/13 6:34 PM, Eric Bergen wrote: This is the expected behavior if you set the timestamp variable in your session. This is the same mechanism that replication uses to execute transactions on the slave with the correct time. Setting timestamp back to default or reopening your connection will fix it. MariaDB [(none)] set timestamp=1372296737; Query OK, 0 rows affected (0.00 sec) MariaDB [(none)] select now(); select sleep(5); select now(); +-+ | now() | +-+ | 2013-06-26 21:32:17 | +-+ 1 row in set (0.00 sec) +--+ | sleep(5) | +--+ |0 | +--+ 1 row in set (5.00 sec) +-+ | now() | +-+ | 2013-06-26 21:32:17 | +-+ 1 row in set (0.00 sec) MariaDB [(none)] set timestamp=default; Query OK, 0 rows affected (0.00 sec) MariaDB [(none)] select now(); +-+ | now() | +-+ | 2013-06-26 21:33:53 | +-+ 1 row in set (0.00 sec) MariaDB [(none)] select now(); +-+ | now() | +-+ | 2013-06-26 21:33:54 | +-+ 1 row in set (0.00 sec) On Wed, Jun 26, 2013 at 4:18 PM, John Meyer johnme...@pueblocomputing.com wrote: Well, if you want to get unstuck in time, maybe you need to call Billy Pilgrim ;-) Andy Wallace wrote: We've been having some issues with one of our MySQL servers lately, and currently the dang thing is stuck. For at least the last hour, NOW() is returning the same value: mysql select now(); +-+ | now() | +-+ | 2013-06-26 02:27:14 | +-+ The system variable timestamp also has that same time value stored in it. How can we kick this loose so that the values are more current with real time? (it is currently 3:08PM here, despite our MySQL instance thinking it's 2am. The system time on the machine is correct: $ date Wed Jun 26 15:08:56 PDT 2013 This is MySQL 5.1.46 running on solaris2.10. Any ideas short of restarting the MySQL engine? I'm willing to do that, but would much rather wait and not do it in the middle of the day. Thanks, Andy -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql -- Andy Wallace iHOUSEweb, Inc. awall...@ihouseweb.com (866) 645-7700 ext 219 -- Sometimes it pays to stay in bed on Monday, rather than spending the rest of the week debugging Monday's code. - Christopher Thompson -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
Re: NOW() is stuck...
But the question is how. I have nothing in the code that does it, or this would have been true for months instead of just the last 24 hours. In addition, this is currently set globally - no matter what connection to the database, it all comes up with this value. Which means that all my time-based queries no longer work correctly. Does your message suggest that setting it to 0 might clear the problem? On 6/27/13 10:31 AM, Stillman, Benjamin wrote: Timestamp is a session variable, so it must have been set to something other than 0 (1372228034 epoch is the date you're showing) in your current session. mysql set timestamp = 1372228034; Query OK, 0 rows affected (0.00 sec) mysql select now(), sysdate(); +-+-+ | now() | sysdate() | +-+-+ | 2013-06-26 02:27:14 | 2013-06-27 13:20:48 | +-+-+ 1 row in set (0.00 sec) mysql set timestamp = 0; Query OK, 0 rows affected (0.00 sec) mysql select now(), sysdate(); +-+-+ | now() | sysdate() | +-+-+ | 2013-06-27 13:21:34 | 2013-06-27 13:21:34 | +-+-+ 1 row in set (0.00 sec) Cliff's notes: set timestamp = 0; On 6/26/13 6:10 PM, Andy Wallace awall...@ihouseweb.com wrote: We've been having some issues with one of our MySQL servers lately, and currently the dang thing is stuck. For at least the last hour, NOW() is returning the same value: mysql select now(); +-+ | now() | +-+ | 2013-06-26 02:27:14 | +-+ The system variable timestamp also has that same time value stored in it. How can we kick this loose so that the values are more current with real time? (it is currently 3:08PM here, despite our MySQL instance thinking it's 2am. The system time on the machine is correct: $ date Wed Jun 26 15:08:56 PDT 2013 This is MySQL 5.1.46 running on solaris2.10. Any ideas short of restarting the MySQL engine? I'm willing to do that, but would much rather wait and not do it in the middle of the day. Thanks, Andy -- Andy Wallace iHOUSEweb, Inc. awall...@ihouseweb.com (866) 645-7700 ext 219 -- Sometimes it pays to stay in bed on Monday, rather than spending the rest of the week debugging Monday's code. - Christopher Thompson -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql Notice: This communication may contain privileged and/or confidential information. If you are not the intended recipient, please notify the sender by email, and immediately delete the message and any attachments without copying or disclosing them. LBI may, for any reason, intercept, access, use, and disclose any information that is communicated by or through, or which is stored on, its networks, applications, services, and devices. -- Andy Wallace iHOUSEweb, Inc. awall...@ihouseweb.com (866) 645-7700 ext 219 -- Sometimes it pays to stay in bed on Monday, rather than spending the rest of the week debugging Monday's code. - Christopher Thompson -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
Re: NOW() is stuck...
Does show variables like 'init_connect'; return anything? On Thu, Jun 27, 2013 at 11:19 AM, Andy Wallace awall...@ihouseweb.com wrote: Benjamin - Unfortunately: mysql show global variables like 'timestamp'; +---++ | Variable_name | Value | +---++ | timestamp | 1372238834 | +---++ 1 row in set (0.00 sec) And: mysql set global timestamp = 0; ERROR 1228 (HY000): Variable 'timestamp' is a SESSION variable and can't be used with SET GLOBAL This does indeed persist across sessions. Any command line connection I make to the database shows the bad value for NOW(). I also tweaked the application code to include NOW() in an existing query, and the value returned to my PHP code is also the bad value. Thanks for looking, andy On 6/27/13 11:10 AM, Stillman, Benjamin wrote: It persists across sessions? Does this return anything: show global variables like 'timestamp'; Hopefully it returns: Empty set (0.00 sec) I vaguely remember reading about a bug in 5.1.4x with something to do with a global timestamp. I thought it only showed one though, and that you couldn't set it. If the above returned a timestamp and not an empty set, try: set global timestamp = 0; That should return something like this: ERROR 1228 (HY000): Variable 'timestamp' is a SESSION variable and can't be used with SET GLOBAL But if it returns: Query OK, 0 rows affected (0.00 sec) And then your queries return correct timestamps, you've found a bug. I'd hope that it would fail, but the only thing I can think of is if it's being set as a global variable. If this does fix your problem, and if you're using replication, you may have an issue with your replicated data. Replication uses timestamp extensively. On 6/27/13 1:44 PM, Andy Wallace awall...@ihouseweb.com wrote: But the question is how. I have nothing in the code that does it, or this would have been true for months instead of just the last 24 hours. In addition, this is currently set globally - no matter what connection to the database, it all comes up with this value. Which means that all my time-based queries no longer work correctly. Does your message suggest that setting it to 0 might clear the problem? On 6/27/13 10:31 AM, Stillman, Benjamin wrote: Timestamp is a session variable, so it must have been set to something other than 0 (1372228034 epoch is the date you're showing) in your current session. mysql set timestamp = 1372228034; Query OK, 0 rows affected (0.00 sec) mysql select now(), sysdate(); +-+-+ | now() | sysdate() | +-+-+ | 2013-06-26 02:27:14 | 2013-06-27 13:20:48 | +-+-+ 1 row in set (0.00 sec) mysql set timestamp = 0; Query OK, 0 rows affected (0.00 sec) mysql select now(), sysdate(); +-+-+ | now() | sysdate() | +-+-+ | 2013-06-27 13:21:34 | 2013-06-27 13:21:34 | +-+-+ 1 row in set (0.00 sec) Cliff's notes: set timestamp = 0; On 6/26/13 6:10 PM, Andy Wallace awall...@ihouseweb.com wrote: We've been having some issues with one of our MySQL servers lately, and currently the dang thing is stuck. For at least the last hour, NOW() is returning the same value: mysql select now(); +-+ | now() | +-+ | 2013-06-26 02:27:14 | +-+ The system variable timestamp also has that same time value stored in it. How can we kick this loose so that the values are more current with real time? (it is currently 3:08PM here, despite our MySQL instance thinking it's 2am. The system time on the machine is correct: $ date Wed Jun 26 15:08:56 PDT 2013 This is MySQL 5.1.46 running on solaris2.10. Any ideas short of restarting the MySQL engine? I'm willing to do that, but would much rather wait and not do it in the middle of the day. Thanks, Andy -- Andy Wallace iHOUSEweb, Inc. awall...@ihouseweb.com (866) 645-7700 ext 219 -- Sometimes it pays to stay in bed on Monday, rather than spending the rest of the week debugging Monday's code. - Christopher Thompson -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql Notice: This communication may contain privileged and/or confidential information. If you are not the intended recipient, please notify the sender by email, and immediately delete the message and any attachments without copying or disclosing them. LBI may, for any reason, intercept, access, use, and disclose any information that is communicated by or through, or which is stored
Re: NOW() is stuck...
It persists across sessions? Does this return anything: show global variables like 'timestamp'; Hopefully it returns: Empty set (0.00 sec) I vaguely remember reading about a bug in 5.1.4x with something to do with a global timestamp. I thought it only showed one though, and that you couldn't set it. If the above returned a timestamp and not an empty set, try: set global timestamp = 0; That should return something like this: ERROR 1228 (HY000): Variable 'timestamp' is a SESSION variable and can't be used with SET GLOBAL But if it returns: Query OK, 0 rows affected (0.00 sec) And then your queries return correct timestamps, you've found a bug. I'd hope that it would fail, but the only thing I can think of is if it's being set as a global variable. If this does fix your problem, and if you're using replication, you may have an issue with your replicated data. Replication uses timestamp extensively. On 6/27/13 1:44 PM, Andy Wallace awall...@ihouseweb.com wrote: But the question is how. I have nothing in the code that does it, or this would have been true for months instead of just the last 24 hours. In addition, this is currently set globally - no matter what connection to the database, it all comes up with this value. Which means that all my time-based queries no longer work correctly. Does your message suggest that setting it to 0 might clear the problem? On 6/27/13 10:31 AM, Stillman, Benjamin wrote: Timestamp is a session variable, so it must have been set to something other than 0 (1372228034 epoch is the date you're showing) in your current session. mysql set timestamp = 1372228034; Query OK, 0 rows affected (0.00 sec) mysql select now(), sysdate(); +-+-+ | now() | sysdate() | +-+-+ | 2013-06-26 02:27:14 | 2013-06-27 13:20:48 | +-+-+ 1 row in set (0.00 sec) mysql set timestamp = 0; Query OK, 0 rows affected (0.00 sec) mysql select now(), sysdate(); +-+-+ | now() | sysdate() | +-+-+ | 2013-06-27 13:21:34 | 2013-06-27 13:21:34 | +-+-+ 1 row in set (0.00 sec) Cliff's notes: set timestamp = 0; On 6/26/13 6:10 PM, Andy Wallace awall...@ihouseweb.com wrote: We've been having some issues with one of our MySQL servers lately, and currently the dang thing is stuck. For at least the last hour, NOW() is returning the same value: mysql select now(); +-+ | now() | +-+ | 2013-06-26 02:27:14 | +-+ The system variable timestamp also has that same time value stored in it. How can we kick this loose so that the values are more current with real time? (it is currently 3:08PM here, despite our MySQL instance thinking it's 2am. The system time on the machine is correct: $ date Wed Jun 26 15:08:56 PDT 2013 This is MySQL 5.1.46 running on solaris2.10. Any ideas short of restarting the MySQL engine? I'm willing to do that, but would much rather wait and not do it in the middle of the day. Thanks, Andy -- Andy Wallace iHOUSEweb, Inc. awall...@ihouseweb.com (866) 645-7700 ext 219 -- Sometimes it pays to stay in bed on Monday, rather than spending the rest of the week debugging Monday's code. - Christopher Thompson -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql Notice: This communication may contain privileged and/or confidential information. If you are not the intended recipient, please notify the sender by email, and immediately delete the message and any attachments without copying or disclosing them. LBI may, for any reason, intercept, access, use, and disclose any information that is communicated by or through, or which is stored on, its networks, applications, services, and devices. -- Andy Wallace iHOUSEweb, Inc. awall...@ihouseweb.com (866) 645-7700 ext 219 -- Sometimes it pays to stay in bed on Monday, rather than spending the rest of the week debugging Monday's code. - Christopher Thompson -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql Notice: This communication may contain privileged and/or confidential information. If you are not the intended recipient, please notify the sender by email, and immediately delete the message and any attachments without copying or disclosing them. LBI may, for any reason, intercept, access, use, and disclose any information that is communicated by or through, or which is stored on, its networks, applications, services, and devices. -- MySQL General Mailing List For list archives: http
Re: NOW() is stuck...
Timestamp is a session variable, so it must have been set to something other than 0 (1372228034 epoch is the date you're showing) in your current session. mysql set timestamp = 1372228034; Query OK, 0 rows affected (0.00 sec) mysql select now(), sysdate(); +-+-+ | now() | sysdate() | +-+-+ | 2013-06-26 02:27:14 | 2013-06-27 13:20:48 | +-+-+ 1 row in set (0.00 sec) mysql set timestamp = 0; Query OK, 0 rows affected (0.00 sec) mysql select now(), sysdate(); +-+-+ | now() | sysdate() | +-+-+ | 2013-06-27 13:21:34 | 2013-06-27 13:21:34 | +-+-+ 1 row in set (0.00 sec) Cliff's notes: set timestamp = 0; On 6/26/13 6:10 PM, Andy Wallace awall...@ihouseweb.com wrote: We've been having some issues with one of our MySQL servers lately, and currently the dang thing is stuck. For at least the last hour, NOW() is returning the same value: mysql select now(); +-+ | now() | +-+ | 2013-06-26 02:27:14 | +-+ The system variable timestamp also has that same time value stored in it. How can we kick this loose so that the values are more current with real time? (it is currently 3:08PM here, despite our MySQL instance thinking it's 2am. The system time on the machine is correct: $ date Wed Jun 26 15:08:56 PDT 2013 This is MySQL 5.1.46 running on solaris2.10. Any ideas short of restarting the MySQL engine? I'm willing to do that, but would much rather wait and not do it in the middle of the day. Thanks, Andy -- Andy Wallace iHOUSEweb, Inc. awall...@ihouseweb.com (866) 645-7700 ext 219 -- Sometimes it pays to stay in bed on Monday, rather than spending the rest of the week debugging Monday's code. - Christopher Thompson -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql Notice: This communication may contain privileged and/or confidential information. If you are not the intended recipient, please notify the sender by email, and immediately delete the message and any attachments without copying or disclosing them. LBI may, for any reason, intercept, access, use, and disclose any information that is communicated by or through, or which is stored on, its networks, applications, services, and devices. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
Re: NOW() is stuck...
Sort of: mysql show variables like 'init_connect'; +---+---+ | Variable_name | Value | +---+---+ | init_connect | | +---+---+ On 6/27/13 11:23 AM, Eric Bergen wrote: Does show variables like 'init_connect'; return anything? On Thu, Jun 27, 2013 at 11:19 AM, Andy Wallace awall...@ihouseweb.com wrote: Benjamin - Unfortunately: mysql show global variables like 'timestamp'; +---++ | Variable_name | Value | +---++ | timestamp | 1372238834 | +---++ 1 row in set (0.00 sec) And: mysql set global timestamp = 0; ERROR 1228 (HY000): Variable 'timestamp' is a SESSION variable and can't be used with SET GLOBAL This does indeed persist across sessions. Any command line connection I make to the database shows the bad value for NOW(). I also tweaked the application code to include NOW() in an existing query, and the value returned to my PHP code is also the bad value. Thanks for looking, andy On 6/27/13 11:10 AM, Stillman, Benjamin wrote: It persists across sessions? Does this return anything: show global variables like 'timestamp'; Hopefully it returns: Empty set (0.00 sec) I vaguely remember reading about a bug in 5.1.4x with something to do with a global timestamp. I thought it only showed one though, and that you couldn't set it. If the above returned a timestamp and not an empty set, try: set global timestamp = 0; That should return something like this: ERROR 1228 (HY000): Variable 'timestamp' is a SESSION variable and can't be used with SET GLOBAL But if it returns: Query OK, 0 rows affected (0.00 sec) And then your queries return correct timestamps, you've found a bug. I'd hope that it would fail, but the only thing I can think of is if it's being set as a global variable. If this does fix your problem, and if you're using replication, you may have an issue with your replicated data. Replication uses timestamp extensively. On 6/27/13 1:44 PM, Andy Wallace awall...@ihouseweb.com wrote: But the question is how. I have nothing in the code that does it, or this would have been true for months instead of just the last 24 hours. In addition, this is currently set globally - no matter what connection to the database, it all comes up with this value. Which means that all my time-based queries no longer work correctly. Does your message suggest that setting it to 0 might clear the problem? On 6/27/13 10:31 AM, Stillman, Benjamin wrote: Timestamp is a session variable, so it must have been set to something other than 0 (1372228034 epoch is the date you're showing) in your current session. mysql set timestamp = 1372228034; Query OK, 0 rows affected (0.00 sec) mysql select now(), sysdate(); +-+-+ | now() | sysdate() | +-+-+ | 2013-06-26 02:27:14 | 2013-06-27 13:20:48 | +-+-+ 1 row in set (0.00 sec) mysql set timestamp = 0; Query OK, 0 rows affected (0.00 sec) mysql select now(), sysdate(); +-+-+ | now() | sysdate() | +-+-+ | 2013-06-27 13:21:34 | 2013-06-27 13:21:34 | +-+-+ 1 row in set (0.00 sec) Cliff's notes: set timestamp = 0; On 6/26/13 6:10 PM, Andy Wallace awall...@ihouseweb.com wrote: We've been having some issues with one of our MySQL servers lately, and currently the dang thing is stuck. For at least the last hour, NOW() is returning the same value: mysql select now(); +-+ | now() | +-+ | 2013-06-26 02:27:14 | +-+ The system variable timestamp also has that same time value stored in it. How can we kick this loose so that the values are more current with real time? (it is currently 3:08PM here, despite our MySQL instance thinking it's 2am. The system time on the machine is correct: $ date Wed Jun 26 15:08:56 PDT 2013 This is MySQL 5.1.46 running on solaris2.10. Any ideas short of restarting the MySQL engine? I'm willing to do that, but would much rather wait and not do it in the middle of the day. Thanks, Andy -- Andy Wallace iHOUSEweb, Inc. awall...@ihouseweb.com (866) 645-7700 ext 219 -- Sometimes it pays to stay in bed on Monday, rather than spending the rest of the week debugging Monday's code. - Christopher Thompson -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql Notice: This communication may contain privileged and/or confidential information. If you are not the intended recipient, please notify the sender by email, and immediately delete the message and any attachments without copying or disclosing them. LBI may, for any reason
Re: NOW() is stuck...
Benjamin - Unfortunately: mysql show global variables like 'timestamp'; +---++ | Variable_name | Value | +---++ | timestamp | 1372238834 | +---++ 1 row in set (0.00 sec) And: mysql set global timestamp = 0; ERROR 1228 (HY000): Variable 'timestamp' is a SESSION variable and can't be used with SET GLOBAL This does indeed persist across sessions. Any command line connection I make to the database shows the bad value for NOW(). I also tweaked the application code to include NOW() in an existing query, and the value returned to my PHP code is also the bad value. Thanks for looking, andy On 6/27/13 11:10 AM, Stillman, Benjamin wrote: It persists across sessions? Does this return anything: show global variables like 'timestamp'; Hopefully it returns: Empty set (0.00 sec) I vaguely remember reading about a bug in 5.1.4x with something to do with a global timestamp. I thought it only showed one though, and that you couldn't set it. If the above returned a timestamp and not an empty set, try: set global timestamp = 0; That should return something like this: ERROR 1228 (HY000): Variable 'timestamp' is a SESSION variable and can't be used with SET GLOBAL But if it returns: Query OK, 0 rows affected (0.00 sec) And then your queries return correct timestamps, you've found a bug. I'd hope that it would fail, but the only thing I can think of is if it's being set as a global variable. If this does fix your problem, and if you're using replication, you may have an issue with your replicated data. Replication uses timestamp extensively. On 6/27/13 1:44 PM, Andy Wallace awall...@ihouseweb.com wrote: But the question is how. I have nothing in the code that does it, or this would have been true for months instead of just the last 24 hours. In addition, this is currently set globally - no matter what connection to the database, it all comes up with this value. Which means that all my time-based queries no longer work correctly. Does your message suggest that setting it to 0 might clear the problem? On 6/27/13 10:31 AM, Stillman, Benjamin wrote: Timestamp is a session variable, so it must have been set to something other than 0 (1372228034 epoch is the date you're showing) in your current session. mysql set timestamp = 1372228034; Query OK, 0 rows affected (0.00 sec) mysql select now(), sysdate(); +-+-+ | now() | sysdate() | +-+-+ | 2013-06-26 02:27:14 | 2013-06-27 13:20:48 | +-+-+ 1 row in set (0.00 sec) mysql set timestamp = 0; Query OK, 0 rows affected (0.00 sec) mysql select now(), sysdate(); +-+-+ | now() | sysdate() | +-+-+ | 2013-06-27 13:21:34 | 2013-06-27 13:21:34 | +-+-+ 1 row in set (0.00 sec) Cliff's notes: set timestamp = 0; On 6/26/13 6:10 PM, Andy Wallace awall...@ihouseweb.com wrote: We've been having some issues with one of our MySQL servers lately, and currently the dang thing is stuck. For at least the last hour, NOW() is returning the same value: mysql select now(); +-+ | now() | +-+ | 2013-06-26 02:27:14 | +-+ The system variable timestamp also has that same time value stored in it. How can we kick this loose so that the values are more current with real time? (it is currently 3:08PM here, despite our MySQL instance thinking it's 2am. The system time on the machine is correct: $ date Wed Jun 26 15:08:56 PDT 2013 This is MySQL 5.1.46 running on solaris2.10. Any ideas short of restarting the MySQL engine? I'm willing to do that, but would much rather wait and not do it in the middle of the day. Thanks, Andy -- Andy Wallace iHOUSEweb, Inc. awall...@ihouseweb.com (866) 645-7700 ext 219 -- Sometimes it pays to stay in bed on Monday, rather than spending the rest of the week debugging Monday's code. - Christopher Thompson -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql Notice: This communication may contain privileged and/or confidential information. If you are not the intended recipient, please notify the sender by email, and immediately delete the message and any attachments without copying or disclosing them. LBI may, for any reason, intercept, access, use, and disclose any information that is communicated by or through, or which is stored on, its networks, applications, services, and devices. -- Andy Wallace iHOUSEweb, Inc. awall...@ihouseweb.com (866) 645-7700 ext 219 -- Sometimes it pays to stay in bed on Monday, rather than spending the rest of the week debugging Monday's code
Re: NOW() is stuck...
Hi, On 06/27/2013 08:19 PM, Andy Wallace wrote: Benjamin - Unfortunately: mysql show global variables like 'timestamp'; +---++ | Variable_name | Value | +---++ | timestamp | 1372238834 | +---++ 1 row in set (0.00 sec) And: mysql set global timestamp = 0; ERROR 1228 (HY000): Variable 'timestamp' is a SESSION variable and can't be used with SET GLOBAL Then, as Benjamin said, you have found the bug. 'GLOBAL timestamp' should not exist http://bugs.mysql.com/bug.php?id=49686 Your GLOBAL (ghost) instance of this variable sets the SESSION one at every client connection. But you are sort of trapped because there is no syntax to manipulate that GLOBAL instance. Also, sadly the manual page does not explain what happens if you set it to DEFAULT: http://dev.mysql.com/doc/refman/5.1/en/server-system-variables.html Cheers -- Claudio
Re: NOW() is stuck...
Well, that begs the question - will restarting the MySQL server instance tonight fix the current problem? We do have a plan in place to test and eventually deploy a more recent version of MySQL (5.6?), but for now, I have to support 1000's of customers. My fingers are crossed. On 6/27/13 12:22 PM, Claudio Nanni wrote: Hi, On 06/27/2013 08:19 PM, Andy Wallace wrote: Benjamin - Unfortunately: mysql show global variables like 'timestamp'; +---++ | Variable_name | Value | +---++ | timestamp | 1372238834 | +---++ 1 row in set (0.00 sec) And: mysql set global timestamp = 0; ERROR 1228 (HY000): Variable 'timestamp' is a SESSION variable and can't be used with SET GLOBAL Then, as Benjamin said, you have found the bug. 'GLOBAL timestamp' should not exist http://bugs.mysql.com/bug.php?id=49686 Your GLOBAL (ghost) instance of this variable sets the SESSION one at every client connection. But you are sort of trapped because there is no syntax to manipulate that GLOBAL instance. Also, sadly the manual page does not explain what happens if you set it to DEFAULT: http://dev.mysql.com/doc/refman/5.1/en/server-system-variables.html Cheers -- Andy Wallace iHOUSEweb, Inc. awall...@ihouseweb.com (866) 645-7700 ext 219 -- Sometimes it pays to stay in bed on Monday, rather than spending the rest of the week debugging Monday's code. - Christopher Thompson -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
Re: NOW() is stuck...
Just out of curiosity, is the hardware stationed, or traveling close to the speed of light (i.e., 18,000 miles per second)? Sorry I could not help it N. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
Re: NOW() is stuck...
Ok, I appreciate the Einsteinian and Vonnegut humor... just wanted to say. Still have the problem though. 8-( On 6/27/13 9:51 AM, Nick Khamis wrote: Just out of curiosity, is the hardware stationed, or traveling close to the speed of light (i.e., 18,000 miles per second)? Sorry I could not help it N. -- Andy Wallace iHOUSEweb, Inc. awall...@ihouseweb.com (866) 645-7700 ext 219 -- Sometimes it pays to stay in bed on Monday, rather than spending the rest of the week debugging Monday's code. - Christopher Thompson -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
NOW() is stuck...
We've been having some issues with one of our MySQL servers lately, and currently the dang thing is stuck. For at least the last hour, NOW() is returning the same value: mysql select now(); +-+ | now() | +-+ | 2013-06-26 02:27:14 | +-+ The system variable timestamp also has that same time value stored in it. How can we kick this loose so that the values are more current with real time? (it is currently 3:08PM here, despite our MySQL instance thinking it's 2am. The system time on the machine is correct: $ date Wed Jun 26 15:08:56 PDT 2013 This is MySQL 5.1.46 running on solaris2.10. Any ideas short of restarting the MySQL engine? I'm willing to do that, but would much rather wait and not do it in the middle of the day. Thanks, Andy -- Andy Wallace iHOUSEweb, Inc. awall...@ihouseweb.com (866) 645-7700 ext 219 -- Sometimes it pays to stay in bed on Monday, rather than spending the rest of the week debugging Monday's code. - Christopher Thompson -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
RE: NOW() is stuck...
Submit a bug: http://bugs.mysql.com Alas, you probably cannot provide a reproducible test case. Still, someone might start at the code and discover a possible cause. -Original Message- From: Andy Wallace [mailto:awall...@ihouseweb.com] Sent: Wednesday, June 26, 2013 3:10 PM To: mysql list Subject: NOW() is stuck... We've been having some issues with one of our MySQL servers lately, and currently the dang thing is stuck. For at least the last hour, NOW() is returning the same value: mysql select now(); +-+ | now() | +-+ | 2013-06-26 02:27:14 | +-+ The system variable timestamp also has that same time value stored in it. How can we kick this loose so that the values are more current with real time? (it is currently 3:08PM here, despite our MySQL instance thinking it's 2am. The system time on the machine is correct: $ date Wed Jun 26 15:08:56 PDT 2013 This is MySQL 5.1.46 running on solaris2.10. Any ideas short of restarting the MySQL engine? I'm willing to do that, but would much rather wait and not do it in the middle of the day. Thanks, Andy -- Andy Wallace iHOUSEweb, Inc. awall...@ihouseweb.com (866) 645-7700 ext 219 -- Sometimes it pays to stay in bed on Monday, rather than spending the rest of the week debugging Monday's code. - Christopher Thompson -- 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: NOW() is stuck...
Well, if you want to get unstuck in time, maybe you need to call Billy Pilgrim ;-) Andy Wallace wrote: We've been having some issues with one of our MySQL servers lately, and currently the dang thing is stuck. For at least the last hour, NOW() is returning the same value: mysql select now(); +-+ | now() | +-+ | 2013-06-26 02:27:14 | +-+ The system variable timestamp also has that same time value stored in it. How can we kick this loose so that the values are more current with real time? (it is currently 3:08PM here, despite our MySQL instance thinking it's 2am. The system time on the machine is correct: $ date Wed Jun 26 15:08:56 PDT 2013 This is MySQL 5.1.46 running on solaris2.10. Any ideas short of restarting the MySQL engine? I'm willing to do that, but would much rather wait and not do it in the middle of the day. Thanks, Andy -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
Re: NOW() is stuck...
This is the expected behavior if you set the timestamp variable in your session. This is the same mechanism that replication uses to execute transactions on the slave with the correct time. Setting timestamp back to default or reopening your connection will fix it. MariaDB [(none)] set timestamp=1372296737; Query OK, 0 rows affected (0.00 sec) MariaDB [(none)] select now(); select sleep(5); select now(); +-+ | now() | +-+ | 2013-06-26 21:32:17 | +-+ 1 row in set (0.00 sec) +--+ | sleep(5) | +--+ |0 | +--+ 1 row in set (5.00 sec) +-+ | now() | +-+ | 2013-06-26 21:32:17 | +-+ 1 row in set (0.00 sec) MariaDB [(none)] set timestamp=default; Query OK, 0 rows affected (0.00 sec) MariaDB [(none)] select now(); +-+ | now() | +-+ | 2013-06-26 21:33:53 | +-+ 1 row in set (0.00 sec) MariaDB [(none)] select now(); +-+ | now() | +-+ | 2013-06-26 21:33:54 | +-+ 1 row in set (0.00 sec) On Wed, Jun 26, 2013 at 4:18 PM, John Meyer johnme...@pueblocomputing.com wrote: Well, if you want to get unstuck in time, maybe you need to call Billy Pilgrim ;-) Andy Wallace wrote: We've been having some issues with one of our MySQL servers lately, and currently the dang thing is stuck. For at least the last hour, NOW() is returning the same value: mysql select now(); +-+ | now() | +-+ | 2013-06-26 02:27:14 | +-+ The system variable timestamp also has that same time value stored in it. How can we kick this loose so that the values are more current with real time? (it is currently 3:08PM here, despite our MySQL instance thinking it's 2am. The system time on the machine is correct: $ date Wed Jun 26 15:08:56 PDT 2013 This is MySQL 5.1.46 running on solaris2.10. Any ideas short of restarting the MySQL engine? I'm willing to do that, but would much rather wait and not do it in the middle of the day. Thanks, Andy -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql -- Eric Bergen eric.ber...@gmail.com http://www.ebergen.net -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
ANN: Database Workbench 4.4.0, the multi-DBMS IDE now available!
ANN: Database Workbench 4.4.0, the multi-DBMS IDE now available! Ladies, gentlemen, Upscene Productions is proud to announce the next version of the popular Windows-based multi-DBMS development tool: Database Workbench 4.4.0 Pro This release includes new features and fixes several bugs as reported by the users. For more information, see http://www.upscene.com/go/?go=newsid=20130423 The FREE Lite Editions will follow later. Database Workbench supports: - Borland InterBase ( 6.x and up ) - Firebird ( 1.x and up ) - MS SQL Server/MSDE ( 7 and up ) - MySQL 4.x and up - Oracle Database ( 8i and up ) - Sybase SQL Anywhere ( 9 and up ) - NexusDB ( 3.0 and up ) Thank you for your support, Martijn Tonies Database Workbench - the database developer tool for professionals 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: Database Workbench 4.3.2, free Lite Editions now available!
ANN: Database Workbench 4.3.2, free Lite Editions now available! Ladies, gentlemen, Upscene Productions is proud to announce the next version of the popular Windows-based multi-DBMS development tool: Database Workbench 4.3.2 Lite Today we are making the free Lite Editions available for version 4.3.2 For more information, see http://www.upscene.com/go/?go=newsid=20130204 Database Workbench supports: - Borland InterBase ( 6.x - XE ) - Firebird ( 1.x, 2.x ) - MS SQL Server/MSDE ( 7, 2000, 2005, 2008 ) - MySQL 4.x, 5.x - Oracle Database ( 8i, 9i, 10g, 11g ) - Sybase SQL Anywhere ( 9, 10, 11 and 12 ) - NexusDB ( 3.0 and up ) The Lite Editions are available for: - InterBase - Firebird - MySQL Thank you for your support, Martijn Tonies Database Workbench - the database developer tool for professionals 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: Database Workbench 4.3.2, the multi-DBMS IDE now available!
ANN: Database Workbench 4.3.2, the multi-DBMS IDE now available! Ladies, gentlemen, Upscene Productions is proud to announce the next version of the popular Windows-based multi-DBMS development tool: Database Workbench 4.3.2 Pro This release fixes several bugs as reported by the users. For more information, see http://www.upscene.com/go/?go=newsid=20121112 The FREE Lite Editions will follow later. Database Workbench supports: - Borland InterBase ( 6.x and up ) - Firebird ( 1.x and up ) - MS SQL Server/MSDE ( 7 and up ) - MySQL 4.x and up - Oracle Database ( 8i and up ) - Sybase SQL Anywhere ( 9 and up ) - NexusDB ( 3.0 and up ) Thank you for your support, Martijn Tonies Database Workbench - the database developer tool for professionals 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: Database Workbench 4.3.1, free Lite Editions now available!
ANN: Database Workbench 4.3.1, free Lite Editions now available! Ladies, gentlemen, Upscene Productions is proud to announce the next version of the popular Windows-based multi-DBMS development tool: Database Workbench 4.3.1 Lite Today we are making the free Lite Editions available for version 4.3.1 For more information, see http://www.upscene.com/go/?go=newsid=20120925 Database Workbench supports: - Borland InterBase ( 6.x - XE ) - Firebird ( 1.x, 2.x ) - MS SQL Server/MSDE ( 7, 2000, 2005, 2008 ) - MySQL 4.x, 5.x - Oracle Database ( 8i, 9i, 10g, 11g ) - Sybase SQL Anywhere ( 9, 10, 11 and 12 ) - NexusDB ( 3.0 and up ) The Lite Editions are available for: - InterBase - Firebird - MySQL Thank you for your support, Martijn Tonies Database Workbench - the database developer tool for professionals 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
New Fast Server Now Available at GoGrid.com
Parallel Universe* is now available as part of Linux OS images at www.GoGrid.com. GoGrid.com is a dedicated/cloud server hosing site. -- *Parallel Universe is a new extension to MySQL server architecture, created to provide fast parallel query capability. Speed is achieved by processing tables in parallel, utilizing multiple core/CPU of server hardware. Because of fast query processing being available to data analysis, it is an ideal data warehouse server. With Parallel Universe, you'll also be able to deploy less costly server hardware for the same query load/task. Parallel Universe is released under the GPL license and fully compatible with MySQL and Percona servers. Also available at www.paralleluniverse-inc.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
ANN: Database Workbench 4.3.1, the multi-DBMS IDE now available!
ANN: Database Workbench 4.3.1, the multi-DBMS IDE now available! Ladies, gentlemen, Upscene Productions is proud to announce the next version of the popular Windows-based multi-DBMS development tool: Database Workbench 4.3.1 Pro This release fixes a few issues with MySQL support. For more information, see http://www.upscene.com/go/?go=newsid=20120820 The FREE Lite Editions will follow later. Changes include: - NEW: Stored Procedure Trigger debugger for MySQL - NEW: incremental data search in SQL, Table View Editor - FIXED: Oracle Debugger fixes - FIXED: NexusDB error when testing Stored Functions - FIXED: MySQL module not properly displaying stored procedures/functions without mysql.procs access and much more... Database Workbench supports: - Borland InterBase ( 6.x - XE ) - Firebird ( 1.x, 2.x ) - MS SQL Server/MSDE ( 7, 2000, 2005, 2008 ) - MySQL 4.x, 5.x - Oracle Database ( 8i, 9i, 10g, 11g ) - Sybase SQL Anywhere ( 9, 10, 11 and 12 ) - NexusDB ( 3.0 and up ) Thank you for your support, Martijn Tonies Database Workbench - the database developer tool for professionals 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: Database Workbench 4.3.0, the multi-DBMS IDE now available!
ANN: Database Workbench 4.3.0, the multi-DBMS IDE now available! Ladies, gentlemen, Upscene Productions is proud to announce the next version of the popular Windows-based multi-DBMS development tool: Database Workbench 4.3.0 Pro For more information, see http://www.upscene.com/go/?go=newsid=20120813 The FREE Lite Editions will follow later. Changes include: - NEW: Stored Procedure Trigger debugger for MySQL - NEW: incremental data search in SQL, Table View Editor - FIXED: Oracle Debugger fixes - FIXED: NexusDB error when testing Stored Functions - FIXED: MySQL module not properly displaying stored procedures/functions without mysql.procs access and much more... For a full list of fixes in this release, see: http://www.upscene.com/go/?go=trackerv=4.3.0id=3 Database Workbench supports: - Borland InterBase ( 6.x - XE ) - Firebird ( 1.x, 2.x ) - MS SQL Server/MSDE ( 7, 2000, 2005, 2008 ) - MySQL 4.x, 5.x - Oracle Database ( 8i, 9i, 10g, 11g ) - Sybase SQL Anywhere ( 9, 10, 11 and 12 ) - NexusDB ( 3.0 and up ) Thank you for your support, Martijn Tonies Database Workbench - the database developer tool for professionals 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: Database Workbench 4.2.4, free Lite Editions now available!
ANN: Database Workbench 4.2.4, free Lite Editions now available! Ladies, gentlemen, Upscene Productions is proud to announce the next version of the popular Windows-based multi-DBMS development tool: Database Workbench 4.2.4 Pro Today we are making the free Lite Editions available for version 4.2.4 For more information, see http://www.upscene.com/go/?go=newsid=20120601 For a full list of fixes in this release, see: http://www.upscene.com/go/?go=trackerv=4.2.4id=3 Database Workbench supports: - Borland InterBase ( 6.x - XE ) - Firebird ( 1.x, 2.x ) - MS SQL Server/MSDE ( 7, 2000, 2005, 2008 ) - MySQL 4.x, 5.x - Oracle Database ( 8i, 9i, 10g, 11g ) - Sybase SQL Anywhere ( 9, 10, 11 and 12 ) - NexusDB ( 3.0 and up ) The Lite Editions are available for: - InterBase - Firebird - MySQL Thank you for your support, Martijn Tonies Database Workbench - the database developer tool for professionals 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: engine is now innoDB instead of MyISAM.
Did the upgrade actually change the Engine on _existing_ tables? I thought the setting in my.cnf only applied to _new_ tables that do _not_ have an engine explicitly specified. True, it is not totally safe to blindly change Engines; there can be performance 'surprises'. This document outlines many of them: http://mysql.rjweb.org/doc.php/myisam2innodb In the long run there are advantages in using InnoDB instead of MyISAM. I suggest you put the change on your roadmap. The new default came with MySQL 5.5 (IIRC); not with Enterprise specifically. -Original Message- From: Claudio Nanni [mailto:claudio.na...@gmail.com] Sent: Sunday, April 29, 2012 6:31 AM To: Brown, Charles Cc: mysql@lists.mysql.com Subject: RE: engine is now innoDB instead of MyISAM. Charles, I think going back to MyISAM as default is a good idea. All you have to do is: Export all databases .Shutdown the cluster MySQL .Add one parameter to your old my.cnf , default-storage-engine=myisam .add cluster specific parameters to your my.cnf , they should be a couple .Put back your my.cnf on all SQL nodes .restart the cluster .reimport your dump , which should drop all Innodb tables I'm on a bus now I can't check better ;) Cheers Claudio On Apr 29, 2012 2:50 PM, Brown, Charles cbr...@bmi.com wrote: Hello Claudio, ** ** Thanks for quick response and the whitepaper. What precipitated my research and questions is a complain I received from one of my developer that after following our MySQL Cluster migration, tables are now defaulting to innodb ( how can he tell) and performance is poor. I'm very much concerned worried because my cnf doesn't reflect any parameter changes or tuning opportunities for innodb - I'm using all defaults since we are not using innodb storage engine. Our MySQL implementation is very simple and limited. Ours model most large IT shops meaning it provides nothing but a nice, fancy glossary front end ( meaning placed outside the cooperate fire wall). Inside this cooperate firewall resides myriads of industry strength databases and data structures. The white paper warns not to expect much from MySQL Cluster until it's optimized. Very little was said about Myisam. Most of the discussions were centered on innordb and NDB. Thus my objective is clearly laid out. I may have to convert all tables back to MyISAM or invest time in tuning. Your thoughts ? ** ** Lastly, can I bring over old performance parameters found in my.cnf. These are parameters that have sustain me over the years. Now, I'm doing MySql Cluster are they any more relevant. ** ** Best regards, ** ** ** ** ** ** *From:* Claudio Nanni [mailto:claudio.na...@gmail.com] *Sent:* Sunday, April 29, 2012 4:29 AM *To:* Brown, Charles *Cc:* mysql@lists.mysql.com *Subject:* Re: engine is now innoDB instead of MyISAM. ** ** Charles, ** ** the pleasure is all mine in meeting such a kind person as you are. ** ** To reply to your question, I would recommend to read frst a basic document about MySQL Cluster, like the whitepaper (http://kae.li/iiisv) so that you have an overview of the infrastructure. ** ** Consider that only the SQL node(that is just a regular MySQL instance) and the Management console have a client command to access the node and the command is different, the regular 'mysql' client command is used to access the SQL node (which as said is just a regular MySQL instance with added NDB support), and to access the management console the command is 'ndb_mgm'.** ** ** ** You cannot access the Data nodes with a client command, those nodes communicate with other cluster nodes but not with the user. ** ** Please feel free to ask any further question. ** ** Thanks ** ** Claudio ** ** 2012/4/29 Brown, Charles cbr...@bmi.com Hello Claudio, In all honesty, the chances of coming into contact with an individual like you who has a grounded knowledge and an ability to articulate thoughts is perhaps a once in a life time experience. However, I meant MySQL Cluster as a product . How can one identify these three different types of nodes. Are there any useful diagnostics command that I can issue in order to identify which node is Data, Management or SQL node. Please assist me. See below for the logon messages Welcome to the MySQL monitor. Commands end with ; or \g. Your MySQL connection id is 374141 Server version: 5.5.19-ndb-7.2.4-gpl MySQL Cluster Community Server (GPL)* *** Copyright (c) 2000, 2011, Oracle and/or its affiliates. All rights reserved. Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective
Re: engine is now innoDB instead of MyISAM.
Charles, the pleasure is all mine in meeting such a kind person as you are. To reply to your question, I would recommend to read frst a basic document about MySQL Cluster, like the whitepaper (http://kae.li/iiisv) so that you have an overview of the infrastructure. Consider that only the SQL node(that is just a regular MySQL instance) and the Management console have a client command to access the node and the command is different, the regular 'mysql' client command is used to access the SQL node (which as said is just a regular MySQL instance with added NDB support), and to access the management console the command is 'ndb_mgm'. You cannot access the Data nodes with a client command, those nodes communicate with other cluster nodes but not with the user. Please feel free to ask any further question. Thanks Claudio 2012/4/29 Brown, Charles cbr...@bmi.com Hello Claudio, ** ** In all honesty, the chances of coming into contact with an individual like you who has a grounded knowledge and an ability to articulate thoughts is perhaps a once in a life time experience. However, I meant “MySQL Cluster as a product” . How can one identify these three different types of nodes. Are there any useful diagnostics command that I can issue in order to identify which node is Data, Management or SQL node. Please assist me. See below for the logon messages ** ** Welcome to the MySQL monitor. Commands end with ; or \g. Your MySQL connection id is 374141 Server version: 5.5.19-ndb-7.2.4-gpl MySQL Cluster Community Server (GPL)* *** ** ** Copyright (c) 2000, 2011, Oracle and/or its affiliates. All rights reserved. ** ** Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners. ** ** Type 'help;' or '\h' for help. Type '\c' to clear the current input statement. ** ** mysql ** ** ** ** ** ** ** ** *From:* Claudio Nanni [mailto:claudio.na...@gmail.com] *Sent:* Saturday, April 28, 2012 2:48 PM *To:* Brown, Charles *Cc:* mysql@lists.mysql.com *Subject:* Re: engine is now innoDB instead of MyISAM. ** ** Charles, ** ** first, my opinion is that if you are paying Oracle you should get answers from them about this, and then of course is good to have a second opinion here. ** ** Related to your specific question you should specify what you mean with 'clustering' which is a generic term, if with it you mean MySQL Cluster product then you have to know that this implementation of database cluster is based on a specific storage engine called Network DataBase (NDB), so you can't choose another engine for it. The default storage engine in the SQL nodes of a MySQL Cluster can be any storage engine and whether it be MyISAM, InnoDB, NDB and it's a design decision, but only NDB tables will benefit from the clustering capabilities. ** ** I hope I got your question right and that this shed a bit more light for you. ** ** Cheers ** ** Claudio ** ** 2012/4/28 Brown, Charles cbr...@bmi.com The question is, is it advisable to change the default engine of a cluster setting to Myisam? Does anyone have an opinion or experience on this issue? Do I have choice when it comes to clustering on which type engine supports clustering. Thanks -Original Message- From: Reindl Harald [mailto:h.rei...@thelounge.net] Sent: Saturday, April 28, 2012 3:01 AM To: mysql@lists.mysql.com Subject: Re: engine is now innoDB instead of MyISAM. Am 28.04.2012 09:00, schrieb Brown: We recently switched from MySQL community to Mysql clustered using Oracle supported MySQl. The problem is, during our testing phase, we observed the default engine is now innoDB instead of MyISAM. Any thoughts on that? We're not getting the performance that we expected - any thoughts or advices out there will be greatly appreciated. my.cnf: default-storage-engine = myisam you cann not compare MyISAm and InnoDB for the same workloads that's why my.cnf exists and we usually define each known setting to prevent chnages in the behavior of applications by software-updates the same for php.ini This message is intended only for the use of the Addressee and may contain information that is PRIVILEGED and CONFIDENTIAL. If you are not the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please erase all copies of the message and its attachments and notify us immediately. Thank you. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql ** ** -- Claudio
RE: engine is now innoDB instead of MyISAM.
Hello Claudio, Thanks for quick response and the whitepaper. What precipitated my research and questions is a complain I received from one of my developer that after following our MySQL Cluster migration, tables are now defaulting to innodb ( how can he tell) and performance is poor. I'm very much concerned worried because my cnf doesn't reflect any parameter changes or tuning opportunities for innodb - I'm using all defaults since we are not using innodb storage engine. Our MySQL implementation is very simple and limited. Ours model most large IT shops meaning it provides nothing but a nice, fancy glossary front end ( meaning placed outside the cooperate fire wall). Inside this cooperate firewall resides myriads of industry strength databases and data structures. The white paper warns not to expect much from MySQL Cluster until it's optimized. Very little was said about Myisam. Most of the discussions were centered on innordb and NDB. Thus my objective is clearly laid out. I may have to convert all tables back to MyISAM or invest time in tuning. Your thoughts ? Lastly, can I bring over old performance parameters found in my.cnf. These are parameters that have sustain me over the years. Now, I'm doing MySql Cluster are they any more relevant. Best regards, From: Claudio Nanni [mailto:claudio.na...@gmail.com] Sent: Sunday, April 29, 2012 4:29 AM To: Brown, Charles Cc: mysql@lists.mysql.com Subject: Re: engine is now innoDB instead of MyISAM. Charles, the pleasure is all mine in meeting such a kind person as you are. To reply to your question, I would recommend to read frst a basic document about MySQL Cluster, like the whitepaper (http://kae.li/iiisv) so that you have an overview of the infrastructure. Consider that only the SQL node(that is just a regular MySQL instance) and the Management console have a client command to access the node and the command is different, the regular 'mysql' client command is used to access the SQL node (which as said is just a regular MySQL instance with added NDB support), and to access the management console the command is 'ndb_mgm'. You cannot access the Data nodes with a client command, those nodes communicate with other cluster nodes but not with the user. Please feel free to ask any further question. Thanks Claudio 2012/4/29 Brown, Charles cbr...@bmi.commailto:cbr...@bmi.com Hello Claudio, In all honesty, the chances of coming into contact with an individual like you who has a grounded knowledge and an ability to articulate thoughts is perhaps a once in a life time experience. However, I meant MySQL Cluster as a product . How can one identify these three different types of nodes. Are there any useful diagnostics command that I can issue in order to identify which node is Data, Management or SQL node. Please assist me. See below for the logon messages Welcome to the MySQL monitor. Commands end with ; or \g. Your MySQL connection id is 374141 Server version: 5.5.19-ndb-7.2.4-gpl MySQL Cluster Community Server (GPL) Copyright (c) 2000, 2011, Oracle and/or its affiliates. All rights reserved. Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners. Type 'help;' or '\h' for help. Type '\c' to clear the current input statement. mysql From: Claudio Nanni [mailto:claudio.na...@gmail.commailto:claudio.na...@gmail.com] Sent: Saturday, April 28, 2012 2:48 PM To: Brown, Charles Cc: mysql@lists.mysql.commailto:mysql@lists.mysql.com Subject: Re: engine is now innoDB instead of MyISAM. Charles, first, my opinion is that if you are paying Oracle you should get answers from them about this, and then of course is good to have a second opinion here. Related to your specific question you should specify what you mean with 'clustering' which is a generic term, if with it you mean MySQL Cluster product then you have to know that this implementation of database cluster is based on a specific storage engine called Network DataBase (NDB), so you can't choose another engine for it. The default storage engine in the SQL nodes of a MySQL Cluster can be any storage engine and whether it be MyISAM, InnoDB, NDB and it's a design decision, but only NDB tables will benefit from the clustering capabilities. I hope I got your question right and that this shed a bit more light for you. Cheers Claudio 2012/4/28 Brown, Charles cbr...@bmi.commailto:cbr...@bmi.com The question is, is it advisable to change the default engine of a cluster setting to Myisam? Does anyone have an opinion or experience on this issue? Do I have choice when it comes to clustering on which type engine supports clustering. Thanks -Original Message- From: Reindl Harald [mailto:h.rei...@thelounge.netmailto:h.rei...@thelounge.net] Sent: Saturday, April 28, 2012 3:01 AM To: mysql@lists.mysql.commailto:mysql@lists.mysql.com Subject: Re: engine is now innoDB instead
Re: engine is now innoDB instead of MyISAM.
Am 29.04.2012 14:50, schrieb Brown: is a complain I received from one of my developer that after following our MySQL Cluster migration, tables are now defaulting to innodb (how can he tell) as already said: the builtin default has changed an you have to configure MyISAM as default yourself with default-storage-engine = myisam and yes, InnoDB can be a big problem if your application is only tested against MyISAM because it works completly different inside signature.asc Description: OpenPGP digital signature
RE: engine is now innoDB instead of MyISAM.
Charles, I think going back to MyISAM as default is a good idea. All you have to do is: Export all databases .Shutdown the cluster MySQL .Add one parameter to your old my.cnf , default-storage-engine=myisam .add cluster specific parameters to your my.cnf , they should be a couple .Put back your my.cnf on all SQL nodes .restart the cluster .reimport your dump , which should drop all Innodb tables I'm on a bus now I can't check better ;) Cheers Claudio On Apr 29, 2012 2:50 PM, Brown, Charles cbr...@bmi.com wrote: Hello Claudio, ** ** Thanks for quick response and the whitepaper. What precipitated my research and questions is a complain I received from one of my developer that after following our MySQL Cluster migration, tables are now defaulting to innodb ( how can he tell) and performance is poor. I’m very much concerned worried because my cnf doesn’t reflect any parameter changes or tuning opportunities for innodb – I’m using all defaults since we are not using innodb storage engine. Our MySQL implementation is very simple and limited. Ours model most large IT shops meaning it provides nothing but a nice, fancy glossary front end ( meaning placed outside the cooperate fire wall). Inside this cooperate firewall resides myriads of industry strength databases and data structures. The white paper warns not to expect much from MySQL Cluster until it’s optimized. Very little was said about Myisam. Most of the discussions were centered on innordb and NDB. Thus my objective is clearly laid out. I may have to convert all tables back to MyISAM or invest time in tuning. Your thoughts ? ** ** Lastly, can I bring over old performance parameters found in my.cnf. These are parameters that have sustain me over the years. Now, I’m doing MySql Cluster are they any more relevant. ** ** Best regards, ** ** ** ** ** ** *From:* Claudio Nanni [mailto:claudio.na...@gmail.com] *Sent:* Sunday, April 29, 2012 4:29 AM *To:* Brown, Charles *Cc:* mysql@lists.mysql.com *Subject:* Re: engine is now innoDB instead of MyISAM. ** ** Charles, ** ** the pleasure is all mine in meeting such a kind person as you are. ** ** To reply to your question, I would recommend to read frst a basic document about MySQL Cluster, like the whitepaper (http://kae.li/iiisv) so that you have an overview of the infrastructure. ** ** Consider that only the SQL node(that is just a regular MySQL instance) and the Management console have a client command to access the node and the command is different, the regular 'mysql' client command is used to access the SQL node (which as said is just a regular MySQL instance with added NDB support), and to access the management console the command is 'ndb_mgm'.** ** ** ** You cannot access the Data nodes with a client command, those nodes communicate with other cluster nodes but not with the user. ** ** Please feel free to ask any further question. ** ** Thanks ** ** Claudio ** ** 2012/4/29 Brown, Charles cbr...@bmi.com Hello Claudio, In all honesty, the chances of coming into contact with an individual like you who has a grounded knowledge and an ability to articulate thoughts is perhaps a once in a life time experience. However, I meant “MySQL Cluster as a product” . How can one identify these three different types of nodes. Are there any useful diagnostics command that I can issue in order to identify which node is Data, Management or SQL node. Please assist me. See below for the logon messages Welcome to the MySQL monitor. Commands end with ; or \g. Your MySQL connection id is 374141 Server version: 5.5.19-ndb-7.2.4-gpl MySQL Cluster Community Server (GPL)* *** Copyright (c) 2000, 2011, Oracle and/or its affiliates. All rights reserved. Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners. Type 'help;' or '\h' for help. Type '\c' to clear the current input statement. mysql *From:* Claudio Nanni [mailto:claudio.na...@gmail.com] *Sent:* Saturday, April 28, 2012 2:48 PM *To:* Brown, Charles *Cc:* mysql@lists.mysql.com *Subject:* Re: engine is now innoDB instead of MyISAM. Charles, first, my opinion is that if you are paying Oracle you should get answers from them about this, and then of course is good to have a second opinion here. Related to your specific question you should specify what you mean with 'clustering' which is a generic term, if with it you mean MySQL Cluster product then you have to know that this implementation of database cluster is based on a specific storage engine called Network DataBase (NDB), so you can't choose another engine
Re: engine is now innoDB instead of MyISAM.
Well said. Thanks so much. Sent from my iPhone On Apr 29, 2012, at 8:02 AM, Reindl Harald h.rei...@thelounge.net wrote: Am 29.04.2012 14:50, schrieb Brown: is a complain I received from one of my developer that after following our MySQL Cluster migration, tables are now defaulting to innodb (how can he tell) as already said: the builtin default has changed an you have to configure MyISAM as default yourself with default-storage-engine = myisam and yes, InnoDB can be a big problem if your application is only tested against MyISAM because it works completly different inside This message is intended only for the use of the Addressee and may contain information that is PRIVILEGED and CONFIDENTIAL. If you are not the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please erase all copies of the message and its attachments and notify us immediately. Thank you. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
engine is now innoDB instead of MyISAM.
Hello all, We recently switched from MySQL community to Mysql clustered using Oracle supported MySQl. The problem is, during our testing phase, we observed the default engine is now innoDB instead of MyISAM. Any thoughts on that? We're not getting the performance that we expected - any thoughts or advices out there will be greatly appreciated. Thanks This message is intended only for the use of the Addressee and may contain information that is PRIVILEGED and CONFIDENTIAL. If you are not the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please erase all copies of the message and its attachments and notify us immediately. Thank you. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
Re: engine is now innoDB instead of MyISAM.
Am 28.04.2012 09:00, schrieb Brown: We recently switched from MySQL community to Mysql clustered using Oracle supported MySQl. The problem is, during our testing phase, we observed the default engine is now innoDB instead of MyISAM. Any thoughts on that? We're not getting the performance that we expected - any thoughts or advices out there will be greatly appreciated. my.cnf: default-storage-engine = myisam you cann not compare MyISAm and InnoDB for the same workloads that's why my.cnf exists and we usually define each known setting to prevent chnages in the behavior of applications by software-updates the same for php.ini signature.asc Description: OpenPGP digital signature
RE: engine is now innoDB instead of MyISAM.
The question is, is it advisable to change the default engine of a cluster setting to Myisam? Does anyone have an opinion or experience on this issue? Do I have choice when it comes to clustering on which type engine supports clustering. Thanks -Original Message- From: Reindl Harald [mailto:h.rei...@thelounge.net] Sent: Saturday, April 28, 2012 3:01 AM To: mysql@lists.mysql.com Subject: Re: engine is now innoDB instead of MyISAM. Am 28.04.2012 09:00, schrieb Brown: We recently switched from MySQL community to Mysql clustered using Oracle supported MySQl. The problem is, during our testing phase, we observed the default engine is now innoDB instead of MyISAM. Any thoughts on that? We're not getting the performance that we expected - any thoughts or advices out there will be greatly appreciated. my.cnf: default-storage-engine = myisam you cann not compare MyISAm and InnoDB for the same workloads that's why my.cnf exists and we usually define each known setting to prevent chnages in the behavior of applications by software-updates the same for php.ini This message is intended only for the use of the Addressee and may contain information that is PRIVILEGED and CONFIDENTIAL. If you are not the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please erase all copies of the message and its attachments and notify us immediately. Thank you. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
Re: engine is now innoDB instead of MyISAM.
Charles, first, my opinion is that if you are paying Oracle you should get answers from them about this, and then of course is good to have a second opinion here. Related to your specific question you should specify what you mean with 'clustering' which is a generic term, if with it you mean MySQL Cluster product then you have to know that this implementation of database cluster is based on a specific storage engine called Network DataBase (NDB), so you can't choose another engine for it. The default storage engine in the SQL nodes of a MySQL Cluster can be any storage engine and whether it be MyISAM, InnoDB, NDB and it's a design decision, but only NDB tables will benefit from the clustering capabilities. I hope I got your question right and that this shed a bit more light for you. Cheers Claudio 2012/4/28 Brown, Charles cbr...@bmi.com The question is, is it advisable to change the default engine of a cluster setting to Myisam? Does anyone have an opinion or experience on this issue? Do I have choice when it comes to clustering on which type engine supports clustering. Thanks -Original Message- From: Reindl Harald [mailto:h.rei...@thelounge.net] Sent: Saturday, April 28, 2012 3:01 AM To: mysql@lists.mysql.com Subject: Re: engine is now innoDB instead of MyISAM. Am 28.04.2012 09:00, schrieb Brown: We recently switched from MySQL community to Mysql clustered using Oracle supported MySQl. The problem is, during our testing phase, we observed the default engine is now innoDB instead of MyISAM. Any thoughts on that? We're not getting the performance that we expected - any thoughts or advices out there will be greatly appreciated. my.cnf: default-storage-engine = myisam you cann not compare MyISAm and InnoDB for the same workloads that's why my.cnf exists and we usually define each known setting to prevent chnages in the behavior of applications by software-updates the same for php.ini This message is intended only for the use of the Addressee and may contain information that is PRIVILEGED and CONFIDENTIAL. If you are not the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please erase all copies of the message and its attachments and notify us immediately. Thank you. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql -- Claudio
Re: Database Workbench 4.2.3, the multi-DBMS IDE now available!
Hello Daevid, Any plans to add sqlite to your list of supported DBs there? I develop Android and use LAMP as the server backend. Currently I use SQLYog as I have for like 10 years. But I would really like one GUI to work on both the android sqlite and the mysql backend since they usually tie together. Full native SQLite is not planned. You probably can access it as a read only datasource, run queries etc, via ODBC, I haven't tested that. 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
ANN: Database Workbench 4.2.3, the multi-DBMS IDE now available!
ANN: Database Workbench 4.2.3, the multi-DBMS IDE now available! Ladies, gentlemen, Upscene Productions is proud to announce the next version of the popular Windows-based multi-DBMS development tool: Database Workbench 4.2.3 Pro For more information, see http://www.upscene.com/go/?go=newsid=20120323 Today's release includes the FREE Lite Editions. For a full list of fixes in this release, see: http://www.upscene.com/go/?go=trackerv=4.2.3id=3 http://www.upscene.com/go/?go=trackerv=4.2.2id=3 http://www.upscene.com/go/?go=trackerv=4.2.1id=3 http://www.upscene.com/go/?go=trackerv=4.2.0id=3 Database Workbench supports: - Borland InterBase ( 6.x - XE ) - Firebird ( 1.x, 2.x ) - MS SQL Server/MSDE ( 7, 2000, 2005, 2008 ) - MySQL 4.x, 5.x - Oracle Database ( 8i, 9i, 10g, 11g ) - Sybase SQL Anywhere ( 9, 10, 11 and 12 ) - NexusDB ( 3.0 and up ) Thank you for your support, Martijn Tonies Database Workbench - the database developer tool for professionals 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: Database Workbench 4.2.3, the multi-DBMS IDE now available!
Any plans to add sqlite to your list of supported DBs there? I develop Android and use LAMP as the server backend. Currently I use SQLYog as I have for like 10 years. But I would really like one GUI to work on both the android sqlite and the mysql backend since they usually tie together. -Original Message- From: Martijn Tonies [mailto:m.ton...@upscene.com] Sent: Friday, March 23, 2012 2:10 AM To: mysql@lists.mysql.com; firebird-to...@yahoogroups.com Subject: ANN: Database Workbench 4.2.3, the multi-DBMS IDE now available! ANN: Database Workbench 4.2.3, the multi-DBMS IDE now available! Ladies, gentlemen, Upscene Productions is proud to announce the next version of the popular Windows-based multi-DBMS development tool: Database Workbench 4.2.3 Pro For more information, see http://www.upscene.com/go/?go=newsid=20120323 Today's release includes the FREE Lite Editions. For a full list of fixes in this release, see: http://www.upscene.com/go/?go=trackerv=4.2.3id=3 http://www.upscene.com/go/?go=trackerv=4.2.2id=3 http://www.upscene.com/go/?go=trackerv=4.2.1id=3 http://www.upscene.com/go/?go=trackerv=4.2.0id=3 Database Workbench supports: - Borland InterBase ( 6.x - XE ) - Firebird ( 1.x, 2.x ) - MS SQL Server/MSDE ( 7, 2000, 2005, 2008 ) - MySQL 4.x, 5.x - Oracle Database ( 8i, 9i, 10g, 11g ) - Sybase SQL Anywhere ( 9, 10, 11 and 12 ) - NexusDB ( 3.0 and up ) Thank you for your support, Martijn Tonies Database Workbench - the database developer tool for professionals 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 -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
ANN: Database Workbench 4.2.1, the multi-DBMS IDE now available!
ANN: Database Workbench 4.2.1, the multi-DBMS IDE now available! Ladies, gentlemen, Upscene Productions is proud to announce the next version of the popular Windows-based multi-DBMS development tool: Database Workbench 4.2.1 Pro This release includes the FREE Lite versions for InterBase, Firebird and MySQL. For more information, see http://www.upscene.com/go/?go=newsid=20120209 For a full list of fixes in this release, see: http://www.upscene.com/go/?go=trackerv=4.2.1id=3 http://www.upscene.com/go/?go=trackerv=4.2.0id=3 Database Workbench supports: - Borland InterBase ( 4.x - XE ) - Firebird ( 1.x, 2.x ) - MS SQL Server/MSDE ( 7, 2000, 2005, 2008, MSDE 1 2, SQL Express ) - MySQL 4.x, 5.x - Oracle Database ( 8i, 9i, 10g, 11g ) - Sybase SQL Anywhere ( 9, 10, 11 and 12 ) - NexusDB ( 3.0 and up ) Thank you for your support, Martijn Tonies Database Workbench - the database developer tool for professionals 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
Database Workbench 4.2.0, the multi-DBMS IDE now available!
ANN: Database Workbench 4.2.0, the multi-DBMS IDE now available! Ladies, gentlemen, Upscene Productions is proud to announce the next version of the popular multi-DBMS Windows-based development tool: Database Workbench 4.2.0 Pro This release includes the FREE Lite versions for InterBase, Firebird and MySQL. There's a 40% discount available until the 1st of January 2012! For more information, see http://www.upscene.com/go/?go=newsid=20111212 For a full list of fixes in this release, see: http://www.upscene.com/go/?go=trackerv=4.2.0id=3 Database Workbench supports: - Borland InterBase ( 4.x - XE ) - Firebird ( 1.x, 2.x ) - MS SQL Server/MSDE ( 7, 2000, 2005, 2008, MSDE 1 2, SQL Express ) - MySQL 4.x, 5.x - Oracle Database ( 8i, 9i, 10g, 11g ) - Sybase SQL Anywhere ( 9, 10, 11 and 12 ) - NexusDB ( 3.0 and up ) Thank you for your support, Martijn Tonies Database Workbench - the database developer tool for professionals 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: Database Workbench 4.1.3, the multi-DBMS IDE now available!
Hi all, No SQLite support? http://www.sqlite.org/ Seems curious you wouldn't have this yet, especially given its popularity on both embedded systems and Android to say the least. Indeed, no native SQLite support. Lots of other systems are popular and not supported. The reason for this is that the tool is not generic and tries to get the most of all. Apparently Winblows-only. It sure would be nice if people would note platform requirements in their announcement, rather than forcing people to dig through their websites for such info. I guess I should know better; if it doesn't list platform requirements, the developer hasn't thought beyond the dominant paradigm. You sure have a point, I'll list it in the future. However, I should note that Database Workbench users have succesfully used it under Wine. 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?unsub=arch...@jab.org
Re: ANN: Database Workbench 4.1.3, the multi-DBMS IDE now available!
Apparently Winblows-only. It sure would be nice if people would note platform requirements in their announcement, rather than forcing people to dig through their websites for such info. I guess I should know better; if it doesn't list platform requirements, the developer hasn't thought beyond the dominant paradigm. You have a very real relationship with God, a Force that responds to your every thought. Not that you are telling God how to run the universe; you are simply aligning with the Force for your good, or not aligning with it. The more aligned you are, the better your life goes. Unlike what you may have been told by fearful teachers, all God wants is for you to be happy. When that is all you want for yourself, that is what you will have. -- Alan Cohen Jan Steinman, EcoReality Co-op -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
ANN: Database Workbench 4.1.3, the multi-DBMS IDE now available!
ANN: Database Workbench 4.1.3, the multi-DBMS IDE now available! Ladies, gentlemen, Upscene Productions is proud to announce the next version of the popular multi-DBMS development tool: Database Workbench 4.1.3 Pro This release includes the FREE Lite versions for InterBase, Firebird and MySQL. For more information, see http://www.upscene.com/go/?go=newsid=20110816 For a full list of fixes in this release, see: http://www.upscene.com/go/?go=trackerv=4.1.3id=3 Database Workbench supports: - Borland InterBase ( 4.x - XE ) - Firebird ( 1.x, 2.x ) - MS SQL Server/MSDE ( 7, 2000, 2005, 2008, MSDE 1 2, SQL Express ) - MySQL 4.x, 5.x - Oracle Database ( 8i, 9i, 10g, 11g ) - Sybase SQL Anywhere ( 9, 10, 11 and 12 ) - NexusDB ( 3.0 and up ) Thank you for your support, Martijn Tonies Database Workbench - the database developer tool for professionals 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?unsub=arch...@jab.org
RE: Database Workbench 4.1.3, the multi-DBMS IDE now available!
No SQLite support? http://www.sqlite.org/ Seems curious you wouldn't have this yet, especially given its popularity on both embedded systems and Android to say the least. -Original Message- From: Martijn Tonies [mailto:m.ton...@upscene.com] Sent: Tuesday, August 16, 2011 6:56 AM To: mysql@lists.mysql.com Cc: firebird-to...@yahoogroups.com Subject: ANN: Database Workbench 4.1.3, the multi-DBMS IDE now available! ANN: Database Workbench 4.1.3, the multi-DBMS IDE now available! Ladies, gentlemen, Upscene Productions is proud to announce the next version of the popular multi-DBMS development tool: Database Workbench 4.1.3 Pro This release includes the FREE Lite versions for InterBase, Firebird and MySQL. For more information, see http://www.upscene.com/go/?go=newsid=20110816 For a full list of fixes in this release, see: http://www.upscene.com/go/?go=trackerv=4.1.3id=3 Database Workbench supports: - Borland InterBase ( 4.x - XE ) - Firebird ( 1.x, 2.x ) - MS SQL Server/MSDE ( 7, 2000, 2005, 2008, MSDE 1 2, SQL Express ) - MySQL 4.x, 5.x - Oracle Database ( 8i, 9i, 10g, 11g ) - Sybase SQL Anywhere ( 9, 10, 11 and 12 ) - NexusDB ( 3.0 and up ) -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Re: upgraded from 5.1-5.5. now getting a mysqldump ERROR 1142: SELECT,LOCK TABL command denied to user 'root'@'localhost' for table 'cond_instances' when using LOCK TABLES. a bug or my config?
I haven't bothered to look for the bug, but it seems to me to be quite reasonable default behaviour to lock the whole lot when you're dumping transactional tables - it ensures you dump all tables from the same consistent view. I would rather take this up with the ZRM people - it should just work. 3.3 came out last week, you may want to have a look at wether it's already been adressed there. Harald's solution is, as usual, technically superior; but he keeps having trouble understanding people not wanting to change their entire setup because their solution isn't optimal :-) -- 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: upgraded from 5.1-5.5. now getting a mysqldump ERROR 1142: SELECT,LOCK TABL command denied to user 'root'@'localhost' for table 'cond_instances' when using LOCK TABLES. a bug or my config?
On Mon, 06 Jun 2011 12:44 +0200, Johan De Meersman vegiv...@tuxera.be wrote: I haven't bothered to look for the bug, but it seems to me to be quite reasonable default behaviour to lock the whole lot when you're dumping transactional tables - it ensures you dump all tables from the same consistent view. thanks for the comment. I would rather take this up with the ZRM people - it should just work. this, http://bugs.mysql.com/bug.php?id=61414 suggests the same. so, i've already started that discussion as well, http://forums.zmanda.com/showthread.php?t=3703 Excluding 'performance_schema' appears to eliminate the error. And it seems does NOT cause a reliability-of-the-backup problem. 3.3 came out last week, you may want to have a look at wether it's already been adressed there. I believe that's an Amanda 3.3 release you're referring to. ZRM is still at 2.2, http://www.zmanda.com/download-zrm.php ZRM for MySQL, Version 2.2 is the Latest Stable Release and, i've MySQL-zrm-2.2.0-1.noarch installed. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Re: upgraded from 5.1-5.5. now getting a mysqldump ERROR 1142: SELECT,LOCK TABL command denied to user 'root'@'localhost' for table 'cond_instances' when using LOCK TABLES. a bug or my config?
- Original Message - From: ag...@airpost.net Excluding 'performance_schema' appears to eliminate the error. And it seems does NOT cause a reliability-of-the-backup problem. Hah, no, backing that up is utterly pointless. Never noticed it doing that. It's basically a virtual schema that contains realtime information about the database, intended to replace a lot of show tables parsing and similar mayhem with simple select statements. I believe that's an Amanda 3.3 release you're referring to. ZRM is still at 2.2, No, I do mean 3.3. Apparently the free downloadable version is quite a bit behind the commercial one. Maybe that's why I never noticed it backing up the performance schema, too :-) They're not really that expensive, either, it might well be worth it to grab licenses and support. -- 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: upgraded from 5.1-5.5. now getting a mysqldump ERROR 1142: SELECT,LOCK TABL command denied to user 'root'@'localhost' for table 'cond_instances' when using LOCK TABLES. a bug or my config?
On Mon, 06 Jun 2011 18:54 +0200, Johan De Meersman vegiv...@tuxera.be wrote: Excluding 'performance_schema' appears to eliminate the error. And it seems does NOT cause a reliability-of-the-backup problem. Hah, no, backing that up is utterly pointless. that's a useful/final confirmation. thx. No, I do mean 3.3. Apparently the free downloadable version is quite a bit behind the commercial one. Maybe that's why I never noticed it backing up the performance schema, too :-) i didn't catch that ZRM's commercial version was at 3.3! thx. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
upgraded from 5.1-5.5. now getting a mysqldump ERROR 1142: SELECT,LOCK TABL command denied to user 'root'@'localhost' for table 'cond_instances' when using LOCK TABLES. a bug or my config?
i use ZRM to do backups of my databases. with v5.1.x, this works fine, mysql-zrm-scheduler --now --backup-set manual --backup-level 0 to execute a manual backup. i recently upgraded from v5.1.x - v5.5.12, mysqladmin -V mysqladmin Ver 8.42 Distrib 5.5.12, for Linux on i686 now, at exec of that backup cmd, i see an ERROR @ console, ... manual:backup:INFO: PHASE START: Creating raw backup manual:backup:INFO: Command used for raw backup is /usr/share/mysql-zrm/plugins/socket-copy.pl --mysqlhotcopy=/usr/bin --host=localhost --port=3306 --socket=/var/cache/mysql/mysql.sock --quiet mysql /var/mysql-bkup/manual/20110605131003 /var/cache/tmp/bZvaQFwQY2 21 manual:backup:INFO: raw-databases=mysql manual:backup:INFO: PHASE END: Creating raw backup manual:backup:INFO: PHASE START: Creating logical backup manual:backup:WARNING: The database(s) drupal6 performance_schema will be backed up in logical mode since they contain tables that use a transactional engine. manual:backup:INFO: Command used for logical backup is /usr/bin/mysqldump --opt --extended-insert --create-options --default-character-set=utf8 --routines --host=localhost --port=3306 --socket=/var/cache/mysql/mysql.sock --databases drupal6 performance_schema /var/mysql-bkup/manual/20110605131003/backup.sql mysqldump: Got error: 1142: SELECT,LOCK TABL command denied to user 'root'@'localhost' for table 'cond_instances' when using LOCK TABLES -- manual:backup:ERROR: mysqldump did not succeed. Command used is /usr/bin/mysqldump --opt --extended-insert --create-options --default-character-set=utf8 --routines --host=localhost --port=3306 --socket=/var/cache/mysql/mysql.sock --databases drupal6 performance_schema /var/mysql-bkup/manual/20110605131003/backup.sqlmanual:backup:INFO: PHASE START: Cleanup manual:backup:INFO: backup-status=Backup failed ... reading up on the error at, http://bugs.mysql.com/bug.php?id=33762 http://bugs.mysql.com/bug.php?id=49633 it looks to do with mysqldump itself. i modified in /etc/my.cnf ... [mysqldump] quick quote-names max_allowed_packet = 8M + skip-lock-tables ... but that doesn't seem to make any difference. something's changed between 5.1.x 5.5.x. what do i need to modify to get past this error? -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Re: upgraded from 5.1-5.5. now getting a mysqldump ERROR 1142: SELECT,LOCK TABL command denied to user 'root'@'localhost' for table 'cond_instances' when using LOCK TABLES. a bug or my config?
have you checked you permissions-table if all privileges are active for root and have you started ymsql_upgrade after all updates? Am 05.06.2011 22:20, schrieb ag...@airpost.net: i use ZRM to do backups of my databases. with v5.1.x, this works fine, mysql-zrm-scheduler --now --backup-set manual --backup-level 0 to execute a manual backup. i recently upgraded from v5.1.x - v5.5.12, mysqladmin -V mysqladmin Ver 8.42 Distrib 5.5.12, for Linux on i686 now, at exec of that backup cmd, i see an ERROR @ console, ... manual:backup:INFO: PHASE START: Creating raw backup manual:backup:INFO: Command used for raw backup is /usr/share/mysql-zrm/plugins/socket-copy.pl --mysqlhotcopy=/usr/bin --host=localhost --port=3306 --socket=/var/cache/mysql/mysql.sock --quiet mysql /var/mysql-bkup/manual/20110605131003 /var/cache/tmp/bZvaQFwQY2 21 manual:backup:INFO: raw-databases=mysql manual:backup:INFO: PHASE END: Creating raw backup manual:backup:INFO: PHASE START: Creating logical backup manual:backup:WARNING: The database(s) drupal6 performance_schema will be backed up in logical mode since they contain tables that use a transactional engine. manual:backup:INFO: Command used for logical backup is /usr/bin/mysqldump --opt --extended-insert --create-options --default-character-set=utf8 --routines --host=localhost --port=3306 --socket=/var/cache/mysql/mysql.sock --databases drupal6 performance_schema /var/mysql-bkup/manual/20110605131003/backup.sql mysqldump: Got error: 1142: SELECT,LOCK TABL command denied to user 'root'@'localhost' for table 'cond_instances' when using LOCK TABLES -- manual:backup:ERROR: mysqldump did not succeed. Command used is /usr/bin/mysqldump --opt --extended-insert --create-options --default-character-set=utf8 --routines --host=localhost --port=3306 --socket=/var/cache/mysql/mysql.sock --databases drupal6 performance_schema /var/mysql-bkup/manual/20110605131003/backup.sqlmanual:backup:INFO: PHASE START: Cleanup manual:backup:INFO: backup-status=Backup failed ... reading up on the error at, http://bugs.mysql.com/bug.php?id=33762 http://bugs.mysql.com/bug.php?id=49633 it looks to do with mysqldump itself. i modified in /etc/my.cnf ... [mysqldump] quick quote-names max_allowed_packet = 8M + skip-lock-tables ... but that doesn't seem to make any difference. something's changed between 5.1.x 5.5.x. what do i need to modify to get past this error? -- 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/ http://www.thelounge.net/signature.asc.what.htm signature.asc Description: OpenPGP digital signature
Re: upgraded from 5.1-5.5. now getting a mysqldump ERROR 1142: SELECT,LOCK TABL command denied to user 'root'@'localhost' for table 'cond_instances' when using LOCK TABLES. a bug or my config?
hi, On Sun, 05 Jun 2011 22:24 +0200, Reindl Harald h.rei...@thelounge.net wrote: have you checked you permissions-table if all privileges are active for root i've got, mysql show grants for 'root'@'localhost'; ++ | Grants for root@localhost | ++ | GRANT ALL PRIVILEGES ON *.* TO 'root'@'localhost' IDENTIFIED BY PASSWORD '*3...4' WITH GRANT OPTION | | GRANT PROXY ON ''@'' TO 'root'@'localhost' WITH GRANT OPTION | ++ and, mysql show grants for 'drupal_admin'@'localhost'; +--+ | Grants for drupal_admin@localhost | +--+ | GRANT USAGE ON *.* TO 'drupal_admin'@'localhost' IDENTIFIED BY PASSWORD '*D...D' | | GRANT SELECT, INSERT, UPDATE, DELETE, CREATE, DROP, INDEX, ALTER, CREATE TEMPORARY TABLES, LOCK TABLES ON `drupal6`.* TO 'drupal_admin'@'localhost' | +--+ 17 rows in set (0.00 sec) are these sufficient? these permissions worked fine as far as i could tell for the v5.1.x install i had. and have you started ymsql_upgrade after all updates? yes, i'd already executed 'mysql_upgrade', following the instructions here: http://dev.mysql.com/doc/refman/5.5/en/upgrading-from-previous-series.html checking, mysql_upgrade Looking for 'mysql' as: mysql Looking for 'mysqlcheck' as: mysqlcheck This installation of MySQL is already upgraded to 5.5.12, use --force if you still need to run mysql_upgrade -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Re: upgraded from 5.1-5.5. now getting a mysqldump ERROR 1142: SELECT,LOCK TABL command denied to user 'root'@'localhost' for table 'cond_instances' when using LOCK TABLES. a bug or my config?
the grant statements does nobody interest maybe use phpmyadmin for a clearer display mysql select * from mysql.user where user='root' limit 1; +---+--+---+-+-+-+-+-+---+-+---+--+---++-+++--++---+--+--+-+--+--++-++--++--++--++-+--+---+-+-+--++---+ | Host | User | Password | Select_priv | Insert_priv | Update_priv | Delete_priv | Create_priv | Drop_priv | Reload_priv | Shutdown_priv | Process_priv | File_priv | Grant_priv | References_priv | Index_priv | Alter_priv | Show_db_priv | Super_priv | Create_tmp_table_priv | Lock_tables_priv | Execute_priv | Repl_slave_priv | Repl_client_priv | Create_view_priv | Show_view_priv | Create_routine_priv | Alter_routine_priv | Create_user_priv | Event_priv | Trigger_priv | Create_tablespace_priv | ssl_type | ssl_cipher | x509_issuer | x509_subject | max_questions | max_updates | max_connections | max_user_connections | plugin | authentication_string | +---+--+---+-+-+-+-+-+---+-+---+--+---++-+++--++---+--+--+-+--+--++-++--++--++--++-+--+---+-+-+--++---+ | localhost | root | * | Y | Y | Y | Y | Y | Y | Y | Y | Y| Y | Y | Y | Y | Y | Y | Y | Y | Y| Y | Y | Y | Y| Y | Y | Y | Y| Y | Y| Y | || | | 0 | 0 | 0 |0 || | +---+--+---+-+-+-+-+-+---+-+---+--+---++-+++--++---+--+--+-+--+--++-++--++--++--++-+--+---+-+-+--++---+ 1 row in set (0.00 sec) Am 05.06.2011 23:05, schrieb ag...@airpost.net: hi, On Sun, 05 Jun 2011 22:24 +0200, Reindl Harald h.rei...@thelounge.net wrote: have you checked you permissions-table if all privileges are active for root i've got, mysql show grants for 'root'@'localhost'; ++ | Grants for root@localhost | ++ | GRANT ALL PRIVILEGES ON *.* TO 'root'@'localhost' IDENTIFIED BY PASSWORD '*3...4' WITH GRANT OPTION | | GRANT PROXY ON ''@'' TO 'root'@'localhost' WITH GRANT OPTION | ++ signature.asc Description: OpenPGP digital signature
Re: upgraded from 5.1-5.5. now getting a mysqldump ERROR 1142: SELECT,LOCK TABL command denied to user 'root'@'localhost' for table 'cond_instances' when using LOCK TABLES. a bug or my config?
fwiw, others are seeing this. e.g., in addition to the two bugs i'd already referenced, http://www.directadmin.com/forum/showthread.php?p=202053 and one http://qa.lampcms.com/q122897/Can-t-backup-mysql-table-with-mysqldump-SELECT-LOCK-TABL-command claims a solution Add --skip-add-locks to your mysqldump command which, having added as i mentioned above, to the [mysqldump] section of /etc/my.cnf, does NOT make a difference for me. On Sun, 05 Jun 2011 23:19 +0200, Reindl Harald h.rei...@thelounge.net wrote: the grant statements does nobody interest mysql select * from mysql.user where user='root' limit 1; and, my result for your cmd, mysql select * from mysql.user where user='root' limit 1; +---+--+---+-+-+-+-+-+---+-+---+--+---++-+++--++---+--+--+-+--+--++-++--++--++--++-+--+---+-+-+--++---+ | Host | User | Password | Select_priv | Insert_priv | Update_priv | Delete_priv | Create_priv | Drop_priv | Reload_priv | Shutdown_priv | Process_priv | File_priv | Grant_priv | References_priv | Index_priv | Alter_priv | Show_db_priv | Super_priv | Create_tmp_table_priv | Lock_tables_priv | Execute_priv | Repl_slave_priv | Repl_client_priv | Create_view_priv | Show_view_priv | Create_routine_priv | Alter_routine_priv | Create_user_priv | Event_priv | Trigger_priv | Create_tablespace_priv | ssl_type | ssl_cipher | x509_issuer | x509_subject | max_questions | max_updates | max_connections | max_user_connections | plugin | authentication_string | +---+--+---+-+-+-+-+-+---+-+---+--+---++-+++--++---+--+--+-+--+--++-++--++--++--++-+--+---+-+-+--++---+ | localhost | root | *3..4 | Y | Y | Y | Y | Y | Y | Y | Y | Y| Y | Y | Y | Y | Y | Y| Y | Y | Y| Y| Y | Y| Y| Y | Y | Y | Y| Y | Y | Y | || | | 0 | 0 | 0 | 0 || NULL | +---+--+---+-+-+-+-+-+---+-+---+--+---++-+++--++---+--+--+-+--+--++-++--++--++--++-+--+---+-+-+--++---+ 1 row in set (0.06 sec) -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Re: upgraded from 5.1-5.5. now getting a mysqldump ERROR 1142: SELECT,LOCK TABL command denied to user 'root'@'localhost' for table 'cond_instances' when using LOCK TABLES. a bug or my config?
hm - bad i would use a replication slave and stop him for consistent backups because dumb locks are not really a good solution independent if this works normally Am 05.06.2011 23:26, schrieb ag...@airpost.net: fwiw, others are seeing this. e.g., in addition to the two bugs i'd already referenced, http://www.directadmin.com/forum/showthread.php?p=202053 and one http://qa.lampcms.com/q122897/Can-t-backup-mysql-table-with-mysqldump-SELECT-LOCK-TABL-command claims a solution Add --skip-add-locks to your mysqldump command which, having added as i mentioned above, to the [mysqldump] section of /etc/my.cnf, does NOT make a difference for me. On Sun, 05 Jun 2011 23:19 +0200, Reindl Harald h.rei...@thelounge.net wrote: the grant statements does nobody interest mysql select * from mysql.user where user='root' limit 1; and, my result for your cmd, mysql select * from mysql.user where user='root' limit 1; +---+--+---+-+-+-+-+-+---+-+---+--+---++-+++--++---+--+--+-+--+--++-++--++--++--++-+--+---+-+-+--++---+ | Host | User | Password | Select_priv | Insert_priv | Update_priv | Delete_priv | Create_priv | Drop_priv | Reload_priv | Shutdown_priv | Process_priv | File_priv | Grant_priv | References_priv | Index_priv | Alter_priv | Show_db_priv | Super_priv | Create_tmp_table_priv | Lock_tables_priv | Execute_priv | Repl_slave_priv | Repl_client_priv | Create_view_priv | Show_view_priv | Create_routine_priv | Alter_routine_priv | Create_user_priv | Event_priv | Trigger_priv | Create_tablespace_priv | ssl_type | ssl_cipher | x509_issuer | x509_subject | max_questions | max_updates | max_connections | max_user_connections | plugin | authentication_string | +---+--+---+-+-+-+-+-+---+-+---+--+---++-+++--++---+--+--+-+--+--++-++--++--++--++-+--+---+-+-+--++---+ | localhost | root | *3..4 | Y | Y | Y | Y | Y | Y | Y | Y | Y| Y | Y | Y | Y | Y | Y| Y | Y | Y| Y| Y | Y| Y| Y | Y | Y | Y| Y | Y | Y | || | | 0 | 0 | 0 | 0 || NULL | +---+--+---+-+-+-+-+-+---+-+---+--+---++-+++--++---+--+--+-+--+--++-++--++--++--++-+--+---+-+-+--++---+ 1 row in set (0.06 sec) -- 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/ http://www.thelounge.net/signature.asc.what.htm signature.asc Description: OpenPGP digital signature
Re: upgraded from 5.1-5.5. now getting a mysqldump ERROR 1142: SELECT,LOCK TABL command denied to user 'root'@'localhost' for table 'cond_instances' when using LOCK TABLES. a bug or my config?
BTW WHY is everybody ansering to the list AND the author of the last post? this reults in get every message twice :-( Am 05.06.2011 23:26, schrieb ag...@airpost.net: fwiw, others are seeing this. e.g., in addition to the two bugs i'd already referenced, http://www.directadmin.com/forum/showthread.php?p=202053 and one http://qa.lampcms.com/q122897/Can-t-backup-mysql-table-with-mysqldump-SELECT-LOCK-TABL-command claims a solution Add --skip-add-locks to your mysqldump command which, having added as i mentioned above, to the [mysqldump] section of /etc/my.cnf, does NOT make a difference for me. On Sun, 05 Jun 2011 23:19 +0200, Reindl Harald h.rei...@thelounge.net wrote: the grant statements does nobody interest mysql select * from mysql.user where user='root' limit 1; and, my result for your cmd, mysql select * from mysql.user where user='root' limit 1; +---+--+---+-+-+-+-+-+---+-+---+--+---++-+++--++---+--+--+-+--+--++-++--++--++--++-+--+---+-+-+--++---+ | Host | User | Password | Select_priv | Insert_priv | Update_priv | Delete_priv | Create_priv | Drop_priv | Reload_priv | Shutdown_priv | Process_priv | File_priv | Grant_priv | References_priv | Index_priv | Alter_priv | Show_db_priv | Super_priv | Create_tmp_table_priv | Lock_tables_priv | Execute_priv | Repl_slave_priv | Repl_client_priv | Create_view_priv | Show_view_priv | Create_routine_priv | Alter_routine_priv | Create_user_priv | Event_priv | Trigger_priv | Create_tablespace_priv | ssl_type | ssl_cipher | x509_issuer | x509_subject | max_questions | max_updates | max_connections | max_user_connections | plugin | authentication_string | +---+--+---+-+-+-+-+-+---+-+---+--+---++-+++--++---+--+--+-+--+--++-++--++--++--++-+--+---+-+-+--++---+ | localhost | root | *3..4 | Y | Y | Y | Y | Y | Y | Y | Y | Y| Y | Y | Y | Y | Y | Y| Y | Y | Y| Y| Y | Y| Y| Y | Y | Y | Y| Y | Y | Y | || | | 0 | 0 | 0 | 0 || NULL | +---+--+---+-+-+-+-+-+---+-+---+--+---++-+++--++---+--+--+-+--+--++-++--++--++--++-+--+---+-+-+--++---+ 1 row in set (0.06 sec) -- 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/ http://www.thelounge.net/signature.asc.what.htm signature.asc Description: OpenPGP digital signature
Re: upgraded from 5.1-5.5. now getting a mysqldump ERROR 1142: SELECT,LOCK TABL command denied to user 'root'@'localhost' for table 'cond_instances' when using LOCK TABLES. a bug or my config?
On Sun, 05 Jun 2011 23:30 +0200, Reindl Harald h.rei...@thelounge.net wrote: BTW WHY is everybody ansering to the list AND the author of the last post? this reults in get every message twice :-( Reply - sends to ONLY the From == h.rei...@thelounge.net Reply to all sends to BOTH the From == h.rei...@thelounge.net AND the list. I suppose if the list manager software, or your client were configured differently ... -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Re: upgraded from 5.1-5.5. now getting a mysqldump ERROR 1142: SELECT,LOCK TABL command denied to user 'root'@'localhost' for table 'cond_instances' when using LOCK TABLES. a bug or my config?
On Sun, 05 Jun 2011 23:29 +0200, Reindl Harald h.rei...@thelounge.net wrote: i would use a replication slave and stop him for consistent backups because dumb locks are not really a good solution independent if this works normally unfortunately, i have no idea what that means. something's apparently broken with mysqldump -- enough so that lots of people are seeing and reporting this same error after the 5.1 - 5.5 upgrade. why would setting up a replication slave be necessary or a good solution to the problem? -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Re: upgraded from 5.1-5.5. now getting a mysqldump ERROR 1142: SELECT,LOCK TABL command denied to user 'root'@'localhost' for table 'cond_instances' when using LOCK TABLES. a bug or my config?
Am 05.06.2011 23:49, schrieb ag...@airpost.net: On Sun, 05 Jun 2011 23:29 +0200, Reindl Harald h.rei...@thelounge.net wrote: i would use a replication slave and stop him for consistent backups because dumb locks are not really a good solution independent if this works normally unfortunately, i have no idea what that means. something's apparently broken with mysqldump -- enough so that lots of people are seeing and reporting this same error after the 5.1 - 5.5 upgrade. why would setting up a replication slave be necessary or a good solution to the problem? because there is no lock on any production table? have fun using mysqldump with really hughe databases :-) a replication slave is synchron, you can stop the slave, copy the whole datadir and after starting the slave it will make all changes from the binary log signature.asc Description: OpenPGP digital signature
Re: upgraded from 5.1-5.5. now getting a mysqldump ERROR 1142: SELECT,LOCK TABL command denied to user 'root'@'localhost' for table 'cond_instances' when using LOCK TABLES. a bug or my config?
i still have no idea why this is necessary. there seems to be a but, problem, misconfiguration, etc. wouldn't it make some sense to try to FIX it, rather than setting up a completely different server? perhaps someone with an idea of the problem and its solution will be able to chime in. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Re: upgraded from 5.1-5.5. now getting a mysqldump ERROR 1142: SELECT,LOCK TABL command denied to user 'root'@'localhost' for table 'cond_instances' when using LOCK TABLES. a bug or my config?
Am 05.06.2011 23:55, schrieb ag...@airpost.net: i still have no idea why this is necessary. take it or not it is a professional solution which works for databses with 20 GB every day here with rsync without interrupt/lock mysqld a second and it is much faster there seems to be a but, problem, misconfiguration, etc. wouldn't it make some sense to try to FIX it, rather than setting up a completely different server? it takes 5 minutes starting a replication salve on the same machine with its own socket/port perhaps someone with an idea of the problem and its solution will be able to chime in. wait until it is fixed or think about a better solution which will work in the future signature.asc Description: OpenPGP digital signature
ANN: Database Workbench 4.1.2, the multi-DBMS IDE now available!
ANN: Database Workbench 4.1.2, the multi-DBMS IDE now available! Ladies, gentlemen, Upscene Productions is proud to announce the next version of the popular multi-DBMS development tool: Database Workbench 4.1.2 Pro This release includes the FREE Lite versions for InterBase, Firebird and MySQL. For more information, see http://www.upscene.com/go/?go=newsid=20110330 For a full list of fixes in 4.1 releases, see: http://www.upscene.com/go/?go=trackerv=4.1.2id=1 http://www.upscene.com/go/?go=trackerv=4.1.1id=1 http://www.upscene.com/go/?go=trackerv=4.1.0id=1 Database Workbench supports: - Borland InterBase ( 4.x - XE ) - Firebird ( 1.x, 2.x ) - MS SQL Server/MSDE ( 7, 2000, 2005, 2008, MSDE 1 2, SQL Express ) - MySQL 4.x, 5.x - Oracle Database ( 8i, 9i, 10g, 11g ) - Sybase SQL Anywhere ( 9, 10, 11 and 12 ) - NexusDB ( 3.0 and up ) Thank you for your support, Martijn Tonies Database Workbench - the database developer tool for professionals 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?unsub=arch...@jab.org
MySQL Enterprise support now at Oracle?
Wow! We paid for MySQL enterprise plus enterprise support back in the good old days before ORACLE bought MySQL. I just sacrificed the sacred chicken and sprinkled the blood around my computer and went to sign up for support at support.oracle.com. After wading through the crappy Flash interface and telling them my dog's mother's maiden name and all, 3 hours later I got an email saying I was Approved. I feel better. I read a few of the numerous tutorials on HOW TO USE THEIR HELP THING and I still don't understand it. I did a search for MySQL on their site and got NOTHING. Have they dropped all support for MySQL? Is there somewhere else we should go to pay for one on one support for things like my little join query problem? Has anyone else had a good experience with Oracle's MySQL support? Maybe this is a bad dream and I'll wake up soon. Thanks, Jim McNeely -- 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 Enterprise support now at Oracle?
Shawn Green works for Oracle and has been very helpful, and I am happy to eat a little bit of shoe leather! Thanks Shawn! Jim On Mar 10, 2011, at 11:11 AM, Jim McNeely wrote: Wow! We paid for MySQL enterprise plus enterprise support back in the good old days before ORACLE bought MySQL. I just sacrificed the sacred chicken and sprinkled the blood around my computer and went to sign up for support at support.oracle.com. After wading through the crappy Flash interface and telling them my dog's mother's maiden name and all, 3 hours later I got an email saying I was Approved. I feel better. I read a few of the numerous tutorials on HOW TO USE THEIR HELP THING and I still don't understand it. I did a search for MySQL on their site and got NOTHING. Have they dropped all support for MySQL? Is there somewhere else we should go to pay for one on one support for things like my little join query problem? Has anyone else had a good experience with Oracle's MySQL support? Maybe this is a bad dream and I'll wake up soon. Thanks, Jim McNeely -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=j...@newcenturydata.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: MySQL Enterprise support now at Oracle?
On Thu, Mar 10, 2011 at 5:05 PM, Jim McNeely j...@newcenturydata.com wrote: Shawn Green works for Oracle and has been very helpful, and I am happy to eat a little bit of shoe leather! Thanks Shawn! Jim Check the archives for Shawn's posts. IMNSHO, they are unparalleled in clarity and depth and breadth of useful information. David
ANN: Database Workbench 4.1.1, the multi-DBMS IDE now available!
ANN: Database Workbench 4.1.1, the multi-DBMS IDE now available! Ladies, gentlemen, Upscene Productions is proud to announce the next version of the popular multi-DBMS development tool: Database Workbench 4.1.1 Pro This release includes the FREE Lite versions for InterBase, Firebird and MySQL. This release fixes a possible crash and some other issues. For more information, see http://www.upscene.com/go/?go=newsid=20110216 For a full list of fixes in version 4.1.1 and 4.1.0, see: http://www.upscene.com/go/?go=trackerv=4.1.1id=1 http://www.upscene.com/go/?go=trackerv=4.1.0id=1 Database Workbench supports: - Borland InterBase ( 4.x - XE ) - Firebird ( 1.x, 2.x ) - MS SQL Server/MSDE ( 7, 2000, 2005, 2008, MSDE 1 2, SQL Express ) - MySQL 4.x, 5.x - Oracle Database ( 8i, 9i, 10g, 11g ) - Sybase SQL Anywhere ( 9, 10, 11 and 12 ) - NexusDB ( 3.0 and up ) Thank you for your support, Martijn Tonies Database Workbench - the database developer tool for professionals 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?unsub=arch...@jab.org
ANN: Database Workbench 4.1.0, the multi-DBMS IDE now available!
Ladies, gentlemen, Upscene Productions is proud to announce the next version of the popular multi-DBMS development tool: Database Workbench 4.1.0 Pro This release includes the FREE Lite versions for InterBase, Firebird and MySQL. Version 4 introduced full Unicode support, 4.1.0 adds new features, latest DBMS support and improved functionality. For more information, see http://www.upscene.com/go/?go=newsid=20101224 For a full list of fixes in version 4.1.0 and previous versions, see: http://www.upscene.com/go/?go=trackerv=4.1.0id=1 http://www.upscene.com/go/?go=trackerv=4.0.3id=1 http://www.upscene.com/go/?go=trackerv=4.0.2id=1 http://www.upscene.com/go/?go=trackerv=4.0.1id=1 http://www.upscene.com/go/?go=trackerv=4.0id=1 Database Workbench supports: - Borland InterBase ( 4.x - XE ) - Firebird ( 1.x, 2.x ) - MS SQL Server/MSDE ( 7, 2000, 2005, 2008, MSDE 1 2, SQL Express ) - MySQL 4.x, 5.x - Oracle Database ( 8i, 9i, 10g, 11g ) - Sybase SQL Anywhere ( 9, 10, 11 and 12 ) - NexusDB ( 3.0 and up ) Thank you for your support, Martijn Tonies Database Workbench - the database developer tool for professionals 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?unsub=arch...@jab.org
Register now for Surge 2010
Registration for Surge Scalability Conference 2010 is open for all attendees! We have an awesome lineup of leaders from across the various communities that support highly scalable architectures, as well as the companies that implement them. Here's a small sampling from our list of speakers: John Allspaw, Etsy Theo Schlossnagle, OmniTI Rasmus Lerdorf, creator of PHP Tom Cook, Facebook Benjamin Black, fast_ip Artur Bergman, Wikia Christopher Brown, Opscode Bryan Cantrill, Joyent Baron Schwartz, Percona Paul Querna, Cloudkick Surge 2010 focuses on real case studies from production environments; the lessons learned from failure and how to re-engineer your way to a successful, highly scalable Internet architecture. The conference takes place at the Tremont Grand Historic Venue on Sept 30 and Oct 1, 2010 in Baltimore, MD. Register now to enjoy the Early Bird discount and guarantee your seat to this year's event! http://omniti.com/surge/2010/register Thanks, -- Jason Dixon OmniTI Computer Consulting, Inc. jdi...@omniti.com 443.325.1357 x.241 -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
ANN: Database Workbench 4.0.3, the multi-DBMS IDE now available!
Ladies, gentlemen, Upscene Productions is proud to announce the next version of the popular multi-DBMS development tool: Database Workbench 4.0.3 Pro This release includes the FREE Lite versions for InterBase, Firebird and MySQL. Version 4 introduced full Unicode support, 4.0.3 fixes some issues found in that initial release and subsequent releases, including the Query was empty-error in some parts of the MySQL module. There have been numerous improvements to existing tools and the user interface making it even better than before. For more information, see http://www.upscene.com/ For a full list of fixes in version 4.0.3 and previous versions, see: http://www.upscene.com/go/?go=trackerv=4.0.3id=1 http://www.upscene.com/go/?go=trackerv=4.0.2id=1 http://www.upscene.com/go/?go=trackerv=4.0.1id=1 http://www.upscene.com/go/?go=trackerv=4.0id=1 Database Workbench supports: - Borland InterBase ( 4.x - 9.x ) - Firebird ( 1.x, 2.x ) - MS SQL Server/MSDE ( 7, 2000, 2005, 2008, MSDE 1 2, SQL Express ) - MySQL 4.x, 5.x - Oracle Database ( 8i, 9i, 10g, 11g ) - Sybase SQL Anywhere ( 9, 10 and 11 ) - NexusDB ( 3.0 and up ) Thank you for your support, Martijn Tonies Database Workbench - the database developer tool for professionals 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?unsub=arch...@jab.org
ANN: New version of Database Workbench, the multi-DBMS IDE now available!
Ladies, gentlemen, Upscene Productions is proud to announce the next version of the popular multi-DBMS development tool: Database Workbench 4.0 Pro With this version we're reached a milestone: Database Workbench is now fully Unicode enabled and offers new tools to increase your productivity. There have been numerous improvements to existing tools and the user interface making it even better than before. For more information, see http://www.upscene.com/ Database Workbench supports: - Borland InterBase ( 4.x - 9.x ) - Firebird ( 1.x, 2.x ) - MS SQL Server/MSDE ( 7, 2000, 2005, 2008, MSDE 1 2, SQL Express ) - MySQL 4.x, 5.x - Oracle Database ( 8i, 9i, 10g, 11g ) - Sybase SQL Anywhere ( 9, 10 and 11 ) - NexusDB ( 3.0 and up ) Thank you for your support, Martijn Tonies Database Workbench - the database developer tool for professionals 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?unsub=arch...@jab.org
What's she doing now
Lincoln feared that the issue of slavery would weaken the northern war effort. Many men throughout the north would fight to save the Union. They would not fight to free the slaves. Although it is often confused with common cold, influenza is a much more severe disease!
MyQuery 3.0 Alpha available now
Sorry for crossposting, but I felt this might be of intrerest to both lists. MyQuery 3.0 is an interactive Windows GUI based query tool for MySQL. Among the features are - Support running scripts from a position, up to a position of just a single query in the script, allowing you to run up to some error, correct the error, and then continue running the script. - Color syntax highlightning by the Scintilla editor control. - Support for script history. - Common files mat be organized in a sepcial Bookmarks menu. - Draging of binary data files into the editor. - Saving of dinary content from results. - Multiple resultsets support, and results may also be saved and not be overwritten. MyQuery 3.0 introduces a bunch of new features, among them: - Multiple editor tabs, allowing editing of several scripts at the time. - Dual connections to the database, to have a separate controlling thread. - Several status monitors, showing GLOBAL and SESSION status, PROCESSLIST and statements. - STATUS list values can displayed / not displayed on a value by value basis, or filtered. - PROCESSLIST data may be sorted. - Status monitors are non-modal. - Dictionary view for tables and routines, again non-modal. - Pasting of CREATE statement from the dictionary views to the editor. MySQL 3.0 is currently Alpha, as some testing still remains, and as it is not yet feature complete. A few more dictionary views and possibly drag-and-drop support for these, as well as some Wizards is among what is planned. MyQuery is GPL and may be downloaded from Sourceforge here: http://sourceforge.net/projects/myquery/ Best regards /Karlsson -- __ ___ ___ __ / |/ /_ __/ __/ __ \/ / Anders Karlsson (and...@mysql.com) / /|_/ / // /\ \/ /_/ / /__ MySQL AB, Sales Engineer /_/ /_/\_, /___/\___\_\___/ Stockholm ___/ www.mysql.com Cellphone: +46 708 608121 Skype: drdatabase -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Re: Copy 70GB ibdata, etc. and server won't start now
On Tue, Jul 14, 2009 at 2:14 AM, Marcus Bointonmar...@synchromedia.co.uk wrote: You should take a look at Percona's xtrabackup utility to do this. It takes a clean snapshot of an innodb database that can be restored on a target machine in a few minutes, though it does crash recovery at backup time which can take a while. Most likely the op only tried to copy the ibdata file(s) and not the iblog files. A big honking waving hand over here saying YES, use xtrabackup. It will be a pretty quick recovery process since the db was shut down cleanly. Note that it will restore ALL tables' data, not just the ibdata and iblog files. Just make sure that your innodb settings in my.cnf match. -- Regards... Todd -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Re: Re: Copy 70GB ibdata, etc. and server won't start now (Action Required)
If a mailbox is protected by one of these types of services: 1) It should be smart enough to see mailing lists and use that as a qualifying address to be allowed through. 2) It should be smart enough to not reply to bulk precedence mail 3) Or the mailbox should never be subscribed to a mailing list. I'm firmly against these types of services, but then again I've never seen one that met the criteria of #1 and #2. Are there any intelligent services out there? #3 will cause people to cry about not being fair and I'm just trying to prevent spam. My answer is no, not being fair is someone expecting me to do their work for them just so they can receive emails from a public list that they joined. Regards... Todd On Wed, Jul 15, 2009 at 10:20 AM, postmas...@boxbe.com wrote: Hello Todd Lyons, I use Boxbe to protect my email address. While I did receive your email about Re: Copy 70GB ibdata, etc. and server won't start now, you are not currently on my email Guest List. I'll be more likely to see your email and future messages if you are on my priority Guest List. Click here to be put directly on my Guest List Thank you, gurunatha...@gmail.com About this Notice This courtesy notice is part of a free service to make email more reliable and useful. Boxbe (www.boxbe.com) uses your existing social network and that of your friends to keep your inbox clean and make sure you receive email from people who matter to you. Say Goodbye to Email Overload www.boxbe.com Final-Recipient: rfc822; gurunatha...@gmail.com Diagnostic-Code: X-Boxbe-Notice; Sender not pre-approved, delivery likely delayed. Follow instructions in above notice Status: 4.7.0 -- Forwarded message -- From: Todd Lyons tly...@ivenue.com To: Date: Wed, 15 Jul 2009 05:28:46 -0700 Subject: Re: Copy 70GB ibdata, etc. and server won't start now -- Regards... Todd -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Re: Copy 70GB ibdata, etc. and server won't start now
You should take a look at Percona's xtrabackup utility to do this. It takes a clean snapshot of an innodb database that can be restored on a target machine in a few minutes, though it does crash recovery at backup time which can take a while. Marcus -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
RE: Copy 70GB ibdata, etc. and server won't start now
-Original Message- From: Gary Smith [mailto:g...@primeexalia.com] Sent: Monday, July 13, 2009 8:54 PM To: Daevid Vincent; mysql@lists.mysql.com Subject: RE: Copy 70GB ibdata, etc. and server won't start now InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html InnoDB: for more information. InnoDB: Error: trying to access page number 2144600306 in space 0, InnoDB: space name ./ibdata1, InnoDB: which is outside the tablespace bounds. InnoDB: Byte offset 0, len 16384, i/o type 10. InnoDB: If you get this error at mysqld startup, please check that InnoDB: your my.cnf matches the ibdata files that you have in the InnoDB: MySQL server. 090714 1:43:18InnoDB: Assertion failure in thread 3083368144 in file fil0fil.c line 3959 InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to http://bugs.mysql.com. InnoDB: If you get repeated assertion failures or crashes, even InnoDB: immediately after the mysqld startup, there may be InnoDB: corruption in the InnoDB tablespace. Please refer to InnoDB: http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html InnoDB: about forcing recovery. First thing that comes to mind is a scenario that happened some time ago when we migrated data from one server to another in a similar way. Server one had the innodb file set to 2gb each file (10 files total). New server was set for 1gb each. It doesn't shrink files so not much was thought about it at the time but our problem was the innodb table settings had to match to the letter. We ended up copying the copy file from the old machine to the new machine (they were running the same version so it really wasn't a problem. The logfiles are the same size so I assume that's configured right? I know that you stated you were running Ubuntu, which is great, but what version of the database did it come from and what version of the database is it going to? +--+ | Old: | +--+ mysql Ver 14.12 Distrib 5.0.51a, for debian-linux-gnu (i486) using readline 5.2 drwx-- 2 mysql mysql 12288 2009-06-26 21:33 agis_core -rw-r--r-- 1 mysql mysql 0 2008-11-24 23:34 debian-5.0.flag -rw-rw 1 mysql mysql 72387395584 2009-07-14 19:18 ibdata1 -rw-rw 1 mysql mysql 5242880 2009-07-14 19:18 ib_logfile0 -rw-rw 1 mysql mysql 5242880 2009-07-14 18:30 ib_logfile1 drwxr-xr-x 2 mysql mysql4096 2008-11-24 23:34 mysql +--+ | New: | +--+ mysql Ver 14.12 Distrib 5.0.75, for debian-linux-gnu (i486) using readline 5.2 drwx-- 2 mysql mysql 12288 2009-07-14 00:36 agis_core -rw-r--r-- 1 mysql mysql 0 2008-11-24 23:34 debian-5.0.flag -rw-rw 1 mysql mysql 70038585344 2009-06-17 04:09 ibdata1 -rw-rw 1 mysql mysql 5242880 2009-07-14 01:43 ib_logfile0 -rw-rw 1 mysql mysql 5242880 2009-06-17 03:22 ib_logfile1 drwxr-xr-x 2 mysql mysql4096 2009-07-14 00:36 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: Copy 70GB ibdata, etc. and server won't start now
Why do the dates on the log files differ by almost a month between Old and New? On Tue, Jul 14, 2009 at 2:23 PM, Daevid Vincent dae...@daevid.com wrote: -Original Message- From: Gary Smith [mailto:g...@primeexalia.com] Sent: Monday, July 13, 2009 8:54 PM To: Daevid Vincent; mysql@lists.mysql.com Subject: RE: Copy 70GB ibdata, etc. and server won't start now InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html InnoDB: for more information. InnoDB: Error: trying to access page number 2144600306 in space 0, InnoDB: space name ./ibdata1, InnoDB: which is outside the tablespace bounds. InnoDB: Byte offset 0, len 16384, i/o type 10. InnoDB: If you get this error at mysqld startup, please check that InnoDB: your my.cnf matches the ibdata files that you have in the InnoDB: MySQL server. 090714 1:43:18InnoDB: Assertion failure in thread 3083368144 in file fil0fil.c line 3959 InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to http://bugs.mysql.com. InnoDB: If you get repeated assertion failures or crashes, even InnoDB: immediately after the mysqld startup, there may be InnoDB: corruption in the InnoDB tablespace. Please refer to InnoDB: http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html InnoDB: about forcing recovery. First thing that comes to mind is a scenario that happened some time ago when we migrated data from one server to another in a similar way. Server one had the innodb file set to 2gb each file (10 files total). New server was set for 1gb each. It doesn't shrink files so not much was thought about it at the time but our problem was the innodb table settings had to match to the letter. We ended up copying the copy file from the old machine to the new machine (they were running the same version so it really wasn't a problem. The logfiles are the same size so I assume that's configured right? I know that you stated you were running Ubuntu, which is great, but what version of the database did it come from and what version of the database is it going to? +--+ | Old: | +--+ mysql Ver 14.12 Distrib 5.0.51a, for debian-linux-gnu (i486) using readline 5.2 drwx-- 2 mysql mysql 12288 2009-06-26 21:33 agis_core -rw-r--r-- 1 mysql mysql 0 2008-11-24 23:34 debian-5.0.flag -rw-rw 1 mysql mysql 72387395584 2009-07-14 19:18 ibdata1 -rw-rw 1 mysql mysql 5242880 2009-07-14 19:18 ib_logfile0 -rw-rw 1 mysql mysql 5242880 2009-07-14 18:30 ib_logfile1 drwxr-xr-x 2 mysql mysql4096 2008-11-24 23:34 mysql +--+ | New: | +--+ mysql Ver 14.12 Distrib 5.0.75, for debian-linux-gnu (i486) using readline 5.2 drwx-- 2 mysql mysql 12288 2009-07-14 00:36 agis_core -rw-r--r-- 1 mysql mysql 0 2008-11-24 23:34 debian-5.0.flag -rw-rw 1 mysql mysql 70038585344 2009-06-17 04:09 ibdata1 -rw-rw 1 mysql mysql 5242880 2009-07-14 01:43 ib_logfile0 -rw-rw 1 mysql mysql 5242880 2009-06-17 03:22 ib_logfile1 drwxr-xr-x 2 mysql mysql4096 2009-07-14 00:36 mysql -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=joh...@pixelated.net -- - Johnny Withers 601.209.4985 joh...@pixelated.net
RE: Copy 70GB ibdata, etc. and server won't start now
Daevid, --The logfiles are the same size so I assume that's configured right? They should be. If you copied the file over, mysql isn't going to increase/decrease the size of the file (because it already exists). I suspect that you didn't save the old my.cnf file. The only other question I have is why is the New file smaller than the original. innodb doesn't shrink files to the best of my knowledge (or at least, it hasn't for me) -- or did you mean that the top one is the new, and the bottom one is the old.. So, looking a little harder at your files, I bet you tried to start myself against the USB device directly, on the first try, it failed, so you copied the data over to the local disk and you have been trying to recover it since. I say that because the time stamp on the usb (new or old ones) but have July 14th as the dates... I think as others have mentioned, the startup recovery flags might be your best bet. From: Daevid Vincent [dae...@daevid.com] Sent: Tuesday, July 14, 2009 12:23 PM To: mysql@lists.mysql.com Cc: Gary Smith Subject: RE: Copy 70GB ibdata, etc. and server won't start now -Original Message- From: Gary Smith [mailto:g...@primeexalia.com] Sent: Monday, July 13, 2009 8:54 PM To: Daevid Vincent; mysql@lists.mysql.com Subject: RE: Copy 70GB ibdata, etc. and server won't start now InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html InnoDB: for more information. InnoDB: Error: trying to access page number 2144600306 in space 0, InnoDB: space name ./ibdata1, InnoDB: which is outside the tablespace bounds. InnoDB: Byte offset 0, len 16384, i/o type 10. InnoDB: If you get this error at mysqld startup, please check that InnoDB: your my.cnf matches the ibdata files that you have in the InnoDB: MySQL server. 090714 1:43:18InnoDB: Assertion failure in thread 3083368144 in file fil0fil.c line 3959 InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to http://bugs.mysql.com. InnoDB: If you get repeated assertion failures or crashes, even InnoDB: immediately after the mysqld startup, there may be InnoDB: corruption in the InnoDB tablespace. Please refer to InnoDB: http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html InnoDB: about forcing recovery. First thing that comes to mind is a scenario that happened some time ago when we migrated data from one server to another in a similar way. Server one had the innodb file set to 2gb each file (10 files total). New server was set for 1gb each. It doesn't shrink files so not much was thought about it at the time but our problem was the innodb table settings had to match to the letter. We ended up copying the copy file from the old machine to the new machine (they were running the same version so it really wasn't a problem. The logfiles are the same size so I assume that's configured right? I know that you stated you were running Ubuntu, which is great, but what version of the database did it come from and what version of the database is it going to? +--+ | Old: | +--+ mysql Ver 14.12 Distrib 5.0.51a, for debian-linux-gnu (i486) using readline 5.2 drwx-- 2 mysql mysql 12288 2009-06-26 21:33 agis_core -rw-r--r-- 1 mysql mysql 0 2008-11-24 23:34 debian-5.0.flag -rw-rw 1 mysql mysql 72387395584 2009-07-14 19:18 ibdata1 -rw-rw 1 mysql mysql 5242880 2009-07-14 19:18 ib_logfile0 -rw-rw 1 mysql mysql 5242880 2009-07-14 18:30 ib_logfile1 drwxr-xr-x 2 mysql mysql4096 2008-11-24 23:34 mysql +--+ | New: | +--+ mysql Ver 14.12 Distrib 5.0.75, for debian-linux-gnu (i486) using readline 5.2 drwx-- 2 mysql mysql 12288 2009-07-14 00:36 agis_core -rw-r--r-- 1 mysql mysql 0 2008-11-24 23:34 debian-5.0.flag -rw-rw 1 mysql mysql 70038585344 2009-06-17 04:09 ibdata1 -rw-rw 1 mysql mysql 5242880 2009-07-14 01:43 ib_logfile0 -rw-rw 1 mysql mysql 5242880 2009-06-17 03:22 ib_logfile1 drwxr-xr-x 2 mysql mysql4096 2009-07-14 00:36 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: Copy 70GB ibdata, etc. and server won't start now
Johnny, I'm less worried about the month in between than the fact that all of the dates for the files on his USB data should be roughly the same. It looks to me like he tried to start it against the data on the USB drive. Another question is, was this an cold backup or hot backup? If this were a hot backup, I could see this problem happening. If it were a could backup, it should work. From: Johnny Withers [joh...@pixelated.net] Sent: Tuesday, July 14, 2009 1:40 PM To: Daevid Vincent Cc: mysql@lists.mysql.com; Gary Smith Subject: Re: Copy 70GB ibdata, etc. and server won't start now Why do the dates on the log files differ by almost a month between Old and New? On Tue, Jul 14, 2009 at 2:23 PM, Daevid Vincent dae...@daevid.commailto:dae...@daevid.com wrote: -Original Message- From: Gary Smith [mailto:g...@primeexalia.commailto:g...@primeexalia.com] Sent: Monday, July 13, 2009 8:54 PM To: Daevid Vincent; mysql@lists.mysql.commailto:mysql@lists.mysql.com Subject: RE: Copy 70GB ibdata, etc. and server won't start now InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html InnoDB: for more information. InnoDB: Error: trying to access page number 2144600306 in space 0, InnoDB: space name ./ibdata1, InnoDB: which is outside the tablespace bounds. InnoDB: Byte offset 0, len 16384, i/o type 10. InnoDB: If you get this error at mysqld startup, please check that InnoDB: your my.cnf matches the ibdata files that you have in the InnoDB: MySQL server. 090714 1:43:18InnoDB: Assertion failure in thread 3083368144 in file fil0fil.c line 3959 InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to http://bugs.mysql.comhttp://bugs.mysql.com/. InnoDB: If you get repeated assertion failures or crashes, even InnoDB: immediately after the mysqld startup, there may be InnoDB: corruption in the InnoDB tablespace. Please refer to InnoDB: http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html InnoDB: about forcing recovery. First thing that comes to mind is a scenario that happened some time ago when we migrated data from one server to another in a similar way. Server one had the innodb file set to 2gb each file (10 files total). New server was set for 1gb each. It doesn't shrink files so not much was thought about it at the time but our problem was the innodb table settings had to match to the letter. We ended up copying the copy file from the old machine to the new machine (they were running the same version so it really wasn't a problem. The logfiles are the same size so I assume that's configured right? I know that you stated you were running Ubuntu, which is great, but what version of the database did it come from and what version of the database is it going to? +--+ | Old: | +--+ mysql Ver 14.12 Distrib 5.0.51a, for debian-linux-gnu (i486) using readline 5.2 drwx-- 2 mysql mysql 12288 2009-06-26 21:33 agis_core -rw-r--r-- 1 mysql mysql 0 2008-11-24 23:34 debian-5.0.flag -rw-rw 1 mysql mysql 72387395584 2009-07-14 19:18 ibdata1 -rw-rw 1 mysql mysql 5242880 2009-07-14 19:18 ib_logfile0 -rw-rw 1 mysql mysql 5242880 2009-07-14 18:30 ib_logfile1 drwxr-xr-x 2 mysql mysql4096 2008-11-24 23:34 mysql +--+ | New: | +--+ mysql Ver 14.12 Distrib 5.0.75, for debian-linux-gnu (i486) using readline 5.2 drwx-- 2 mysql mysql 12288 2009-07-14 00:36 agis_core -rw-r--r-- 1 mysql mysql 0 2008-11-24 23:34 debian-5.0.flag -rw-rw 1 mysql mysql 70038585344 2009-06-17 04:09 ibdata1 -rw-rw 1 mysql mysql 5242880 2009-07-14 01:43 ib_logfile0 -rw-rw 1 mysql mysql 5242880 2009-06-17 03:22 ib_logfile1 drwxr-xr-x 2 mysql mysql4096 2009-07-14 00:36 mysql -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=joh...@pixelated.net -- - Johnny Withers 601.209.4985 joh...@pixelated.netmailto:joh...@pixelated.net
RE: Copy 70GB ibdata, etc. and server won't start now
_ From: Johnny Withers [mailto:joh...@pixelated.net] Sent: Tuesday, July 14, 2009 1:41 PM To: Daevid Vincent Cc: mysql@lists.mysql.com; Gary Smith Subject: Re: Copy 70GB ibdata, etc. and server won't start now Why do the dates on the log files differ by almost a month between Old and New? Because the 70GB snapshot was copied a month ago when we swapped out some hardware and drives and such. So the data on my new box will be a month old, but that's fine. It's for a live demo and doesn't need to be current -- just have stuff to play with. And everytime you muck with the database, it updates the stamp, so these dates are misleading. +--+ | Old: | +--+ mysql Ver 14.12 Distrib 5.0.51a, for debian-linux-gnu (i486) using readline 5.2 drwx-- 2 mysql mysql 12288 2009-06-26 21:33 agis_core -rw-r--r-- 1 mysql mysql 0 2008-11-24 23:34 debian-5.0.flag -rw-rw 1 mysql mysql 72387395584 2009-07-14 19:18 ibdata1 -rw-rw 1 mysql mysql 5242880 2009-07-14 19:18 ib_logfile0 -rw-rw 1 mysql mysql 5242880 2009-07-14 18:30 ib_logfile1 drwxr-xr-x 2 mysql mysql4096 2008-11-24 23:34 mysql +--+ | New: | +--+ mysql Ver 14.12 Distrib 5.0.75, for debian-linux-gnu (i486) using readline 5.2 drwx-- 2 mysql mysql 12288 2009-07-14 00:36 agis_core -rw-r--r-- 1 mysql mysql 0 2008-11-24 23:34 debian-5.0.flag -rw-rw 1 mysql mysql 70038585344 2009-06-17 04:09 ibdata1 -rw-rw 1 mysql mysql 5242880 2009-07-14 01:43 ib_logfile0 -rw-rw 1 mysql mysql 5242880 2009-06-17 03:22 ib_logfile1 drwxr-xr-x 2 mysql mysql4096 2009-07-14 00:36 mysql
RE: Copy 70GB ibdata, etc. and server won't start now
Not sure what you mean start it against the USB drive. I copied from 'old' - USB - 'new' /var/lib/mysql/*. At no time did I run the database pointing at the USB drive (is that even possible? I guess a symlink or something maybe with mods to app armor). The 'old' is growing and changing dates because it is still live and actually in production. This 'new' box is going to be used for a demo at a conference and is therefore a copy from about a month ago and will not grow in size, but the dates will change as I muck with the data on it. From: Gary Smith [mailto:g...@primeexalia.com] Sent: Tuesday, July 14, 2009 2:11 PM To: Johnny Withers; Daevid Vincent Cc: mysql@lists.mysql.com Subject: RE: Copy 70GB ibdata, etc. and server won't start now Johnny, I'm less worried about the month in between than the fact that all of the dates for the files on his USB data should be roughly the same. It looks to me like he tried to start it against the data on the USB drive. Another question is, was this an cold backup or hot backup? If this were a hot backup, I could see this problem happening. If it were a could backup, it should work. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Re: Copy 70GB ibdata, etc. and server won't start now
Another thing you can do is simply erase the innodb logs. If the dbms really was shutdown properly then the logs are useful, they will be recreated again and you can go forward with your demo. Carlos On 7/14/2009 6:23 PM, Daevid Vincent wrote: Not sure what you mean start it against the USB drive. I copied from 'old' - USB - 'new' /var/lib/mysql/*. At no time did I run the database pointing at the USB drive (is that even possible? I guess a symlink or something maybe with mods to app armor). The 'old' is growing and changing dates because it is still live and actually in production. This 'new' box is going to be used for a demo at a conference and is therefore a copy from about a month ago and will not grow in size, but the dates will change as I muck with the data on it. From: Gary Smith [mailto:g...@primeexalia.com] Sent: Tuesday, July 14, 2009 2:11 PM To: Johnny Withers; Daevid Vincent Cc: mysql@lists.mysql.com Subject: RE: Copy 70GB ibdata, etc. and server won't start now Johnny, I'm less worried about the month in between than the fact that all of the dates for the files on his USB data should be roughly the same. It looks to me like he tried to start it against the data on the USB drive. Another question is, was this an cold backup or hot backup? If this were a hot backup, I could see this problem happening. If it were a could backup, it should work. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
