- discuss - lists.mariadb.org

[Maria-discuss] MariaDB Galera Cluster 5.5.25 Alpha now available
by Daniel Bartholomew 06 Sep '12

06 Sep '12

The MariaDB project is pleased to announce the immediate availability of MariaDB Galera Cluster 5.5.25 Alpha. This is an Alpha release. What is it? * A straight merge of MariaDB 5.5.25 with Galera Cluster by Codership * An alpha release which should not be used in production environments * Using the Galera replication methodology, users get: * Synchronous, multi-master replication with guaranteed data consistency. * This solution provides both read & write scalability The links below have more information. Compatibility? MariaDB Galera Cluster is fully data-compatible with MariaDB or MySQL, as it will work with the standard databases created by these products. There are next to none or very minimal application changes that are required to make the solution work. Where can I get it? See the links below. What's next? The plan is for a rapid release cycle to heavily test the performance and usage of MariaDB Galera Cluster in different environments. Please file bugs at: https://mariadb.atlassian.net Quotes: Seppo Jaakola, CEO for Codership "It's great that we are working closely with an upstream provider of a MySQL-compatible binary, MariaDB. We no longer have to spend time coding against out-of-tree changes as we're part of MariaDB. The excellent MariaDB engineering team constantly releases new versions of MariaDB with high quality assurance (QA). Codership will continue to collaborate closely with the MariaDB engineering team to improve the product and make new versions of the MariaDB Galera Cluster available." Michael "Monty" Widenius, CEO for Monty Program Ab "We've received a significant amount of requests for a MariaDB based Galera cluster and today we're proud to deliver that. We're currently preparing ourselves and our partners for a rollout of the GA product and related professional services via SkySQL to run critical systems on top of MariaDB Galera Cluster." The MariaDB Team will together with Codership work on customer requests and demands in the areas of cluster and replication. Please contact us if you are interested in any services we can offer around Galera, MariaDB or MySQL. http://montyprogram.com/contact - - MariaDB Galera Cluster 5.5.25 Links - - - - - - - - - - - - - - - - Release Notes: http://kb.askmonty.org/en/mariadb-galera-5525-release-notes Changelog: http://kb.askmonty.org/en/mariadb-galera-5525-changelog Downloads: http://downloads.mariadb.org/mariadb-galera/5.5.25 YUM Repository Configuration Generator: http://downloads.mariadb.org/mariadb-galera/repositories (APT repositories are not available at this time.) Overview of MariaDB Galera Cluster 5.5: http://kb.askmonty.org/en/what-is-mariadb-galera-cluster More information: http://kb.askmonty.org/en/galera - - Where else to find us - - - - - - - - - - - - - - - - - - - - - - - http://mariadb.org We're also on: Facebook: http://fb.com/MariaDB.dbms Twitter: http://twitter.com/mariadb Google+: http://google.com/+mariadb Follow, friend, and add us to your circles to keep up to date with MariaDB! -- MariaDB: An Enhanced Drop-in Replacement for MySQL

1 0

[Maria-discuss] KB entry on SQLyog and MONyog
by Peter Laursen 31 Aug '12

31 Aug '12

Hi! We would like to update the AskMonty Knowledgebase entry on MONyog and SQLyog appearing here: http://kb.askmonty.org/en/monyog-sqlyog/ It will not be an advertisement but a listing of 15-20 main features of each of the programs. We would have the same 'level of details' for both programs as HeidiSQL has currently. Maybe also it would be better to independent entries for each program? The question is: can we just go ahead and do ourselves or should we share content for discussion/approval here first? Regards Peter Laursen Webyog

3 2

[Maria-discuss] KB Question: Future of MariaDB?
by Daniel Bartholomew 28 Aug '12

28 Aug '12

The following question has been posted to the Knowledgebase: http://kb.askmonty.org/en/future-of-mariadb/ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Future of MariaDB? Where I work, we depend heavily on MySQL. We were recently made aware that Oracle may be slowly closing the source of MySQL; though we are a Sun customer, we depend heavily (and prefer) open source. I mentioned this to my boss and his response was to ask of the future of MariaDB -- because if this project doesn't survive, we're stuck with having to find yet another DB -- in that case, we might have to drink the Oracle koolaid if it comes to that, or move to PostgreSQL (something I've never touched). Commentary on these topics would be interesting to hear. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Thanks. -- Daniel Bartholomew Google+ - http://gplus.to/dbart Twitter - http://twitter.com/daniel_bart MariaDB: An Enhanced Drop-in Replacement for MySQL Website - http://mariadb.org Twitter - http://twitter.com/mariadb Google+ - http://gplus.to/mariadb Facebook - http://fb.com/MariaDB.dbms Knowledgebase - http://kb.askmonty.org Monty Program - http://montyprogram.com

2 1

[Maria-discuss] help tables are obsolete
by Federico Razzoli 18 Aug '12

18 Aug '12

Hello I suppose that you are not going to document MariaDB's features in the help tables. Thought, I think you don't know that the MariaDB 5.5.25 help tables still have MySQL 5.1 contents. This means that: * MySQL 5.5 features (like SIGNAL) are not documented * Existing contents point to MySQL 5.1 documentation. I hope that this feedback is useful. Best greetings, Federico Razzoli

2 1

[Maria-discuss] Debian Wheezy repo for MariaDB?
by Terry 15 Aug '12

15 Aug '12

Hi, Now that Debian Wheezy has gone into a freeze, are there any plans to package MariaDB for Wheezy in the near future? Thanks. -- Terry

2 1

[Maria-discuss] "libmysqlclient.so.18 no version information" issue
by Terry 07 Aug '12

07 Aug '12

Hello, I am a relative newbie learning about Linux/MariaDB. I have a test server running Debian Squeeze 6.0.4 with MariaDB 5.5 installed from the MariaDB Squeeze repository. Everything worked great. I upgraded Squeeze to Wheezy (do have a back up so no issue reverting if necessary). Upgrade went rather smoothly. MariaDB running fine. Everything else working fine. On the first night after the upgrade, cron ran and I received several errors: /usr/lib/libmysqlclient.so.18: no version information available (required by exim4) /usr/lib/libmysqlclient.so.18: no version information available (required by /usr/lib/libmu_auth.so.4) The errors don't seem to cause any problems. I still get the e-mails sent by cron. Exim4 is running fine and I have no problems sending or receiving mail. MariaDB is doing fine and my test websites are performing as expected. Can someone give me a hint about where to start looking for the solutio to this? I've googled this and really couldn't find much info about it. Is this because the MariaDB deb package from the repo was built against Squeeze? If so, would the error be corrected if I downloaded the source and built it against Wheezy? Thanks. -- Terry

2 2

[Maria-discuss] MariaDB 5.5 compile error
by Brian Evans 07 Aug '12

07 Aug '12

Hi, I would like some assistance in figuring out a compile error in MariaDB 5.5 series (tested on 5.5.25). I'm trying to create a minimal (client only) build of 5.5.25. This is the cmake configure command used: cmake --no-warn-unused-cli -C /var/tmp/portage/dev-db/mariadb-5.5.25/work/mariadb-5.5.25_build/gentoo_common_config.cmake -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_INSTALL_PREFIX=/usr -DMYSQL_DATADIR=/var/lib/mysql -DSYSCONFDIR=/etc/mysql -DINSTALL_BINDIR=bin -DINSTALL_DOCDIR=share/doc/mariadb-5.5.25 -DINSTALL_DOCREADMEDIR=share/doc/mariadb-5.5.25 -DINSTALL_INCLUDEDIR=include/mysql -DINSTALL_INFODIR=share/info -DINSTALL_LIBDIR=lib64/mysql -DINSTALL_MANDIR=share/man -DINSTALL_MYSQLDATADIR=/var/lib/mysql -DINSTALL_MYSQLSHAREDIR=share/mysql -DINSTALL_MYSQLTESTDIR=share/mysql/mysql-test -DINSTALL_PLUGINDIR=lib64/mysql/plugin -DINSTALL_SBINDIR=sbin -DINSTALL_SCRIPTDIR=share/mysql/scripts -DINSTALL_SQLBENCHDIR=share/mysql -DINSTALL_SUPPORTFILESDIR=/usr/share/mysql -DWITH_COMMENT=Gentoo Linux mariadb-5.5.25 -DWITHOUT_UNIT_TESTS=1 -DNOT_FOR_DISTRIBUTION=1 -DDEFAULT_CHARSET=latin1 -DDEFAULT_COLLATION=latin1_swedish_ci -DWITHOUT_SERVER=1 -DWITHOUT_EMBEDDED_SERVER=1 -DENABLED_LOCAL_INFILE=1 -DINSTALL_SQLBENCHDIR= -DWITH_SSL=system -DWITH_ZLIB=system -DWITHOUT_LIBWRAP=1 -DWITHOUT_READLINE=1 -DWITHOUT_ARCHIVE_STORAGE_ENGINE=1 -DWITHOUT_BLACKHOLE_STORAGE_ENGINE=1 -DWITHOUT_CSV_STORAGE_ENGINE=1 -DWITHOUT_FEDERATED_STORAGE_ENGINE=1 -DWITHOUT_HEAP_STORAGE_ENGINE=1 -DWITHOUT_INNOBASE_STORAGE_ENGINE=1 -DWITHOUT_MYISAMMRG_STORAGE_ENGINE=1 -DWITHOUT_MYISAM_STORAGE_ENGINE=1 -DWITHOUT_PARTITION_STORAGE_ENGINE=1 -DWITHOUT_INNOBASE_STORAGE_ENGINE=1 -DCMAKE_BUILD_TYPE=RelWithDebInfo -DCMAKE_INSTALL_DO_STRIP=OFF -DCMAKE_USER_MAKE_RULES_OVERRIDE=/var/tmp/portage/dev-db/mariadb-5.5.25/work/mariadb-5.5.25_build/gentoo_rules.cmake /var/tmp/portage/dev-db/mariadb-5.5.25/work/mysql gives the following error during build /var/tmp/portage/dev-db/mariadb-5.5.25/work/mysql/mysys/waiting_threads.c:196:21: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘key_WT_RESOURCE_cond’ make[2]: *** [mysys/CMakeFiles/mysys.dir/waiting_threads.c.o] Error 1 However, if i build the full server, I get no error. cmake configure with no error: cmake --no-warn-unused-cli -C /var/tmp/portage/dev-db/mariadb-5.5.25/work/mariadb-5.5.25_build/gentoo_common_config.cmake -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_INSTALL_PREFIX=/usr -DMYSQL_DATADIR=/var/lib/mysql -DSYSCONFDIR=/etc/mysql -DINSTALL_BINDIR=bin -DINSTALL_DOCDIR=share/doc/mariadb-5.5.25 -DINSTALL_DOCREADMEDIR=share/doc/mariadb-5.5.25 -DINSTALL_INCLUDEDIR=include/mysql -DINSTALL_INFODIR=share/info -DINSTALL_LIBDIR=lib64/mysql -DINSTALL_MANDIR=share/man -DINSTALL_MYSQLDATADIR=/var/lib/mysql -DINSTALL_MYSQLSHAREDIR=share/mysql -DINSTALL_MYSQLTESTDIR=share/mysql/mysql-test -DINSTALL_PLUGINDIR=lib64/mysql/plugin -DINSTALL_SBINDIR=sbin -DINSTALL_SCRIPTDIR=share/mysql/scripts -DINSTALL_SQLBENCHDIR=share/mysql -DINSTALL_SUPPORTFILESDIR=/usr/share/mysql -DWITH_COMMENT=Gentoo Linux mariadb-5.5.25 -DWITHOUT_UNIT_TESTS=1 -DNOT_FOR_DISTRIBUTION=1 -DDEFAULT_CHARSET=latin1 -DDEFAULT_COLLATION=latin1_swedish_ci -DENABLED_LOCAL_INFILE=1 -DEXTRA_CHARSETS=all -DMYSQL_USER=mysql -DMYSQL_UNIX_ADDR=/var/run/mysqld/mysqld.sock -DWITHOUT_READLINE=1 -DWITH_ZLIB=system -DWITHOUT_LIBWRAP=1 -DDISABLE_SHARED=OFF -DWITH_debug=OFF -DWITH_DEBUG=OFF -DWITH_Debug=OFF -DWITH_EMBEDDED_SERVER=OFF -DWITH_profiling=ON -DWITH_PROFILING=ON -DWITH_Profiling=ON -DENABLE_DTRACE=OFF -DWITH_SSL=system -DCMAKE_EXE_LINKER_FLAGS=-ljemalloc -DWITH_SAFEMALLOC=OFF -DWITH_ARCHIVE_STORAGE_ENGINE=1 -DWITH_BLACKHOLE_STORAGE_ENGINE=1 -DWITH_CSV_STORAGE_ENGINE=1 -DWITH_HEAP_STORAGE_ENGINE=1 -DWITH_INNOBASE_STORAGE_ENGINE=1 -DWITH_MYISAMMRG_STORAGE_ENGINE=1 -DWITH_MYISAM_STORAGE_ENGINE=1 -DWITH_PARTITION_STORAGE_ENGINE=1 -DWITH_FEDERATED_STORAGE_ENGINE=ON -DWITH_PBXT_STORAGE_ENGINE=OFF -DWITH_OQGRAPH_STORAGE_ENGINE=OFF -DWITH_SPHINX_STORAGE_ENGINE=OFF -DWITH_FEDERATEDX_STORAGE_ENGINE=ON -DCMAKE_BUILD_TYPE=RelWithDebInfo -DCMAKE_INSTALL_DO_STRIP=OFF -DCMAKE_USER_MAKE_RULES_OVERRIDE=/var/tmp/portage/dev-db/mariadb-5.5.25/work/mariadb-5.5.25_build/gentoo_rules.cmake /var/tmp/portage/dev-db/mariadb-5.5.25/work/mysql gentoo_common_config.cmake contains: SET (LIB_SUFFIX 64 CACHE STRING "library path suffix" FORCE) SET (CMAKE_INSTALL_LIBDIR /usr/lib64 CACHE PATH "Output directory for libraries") I'm at a loss why one way works and the the other doesn't. Thank you.

2 4

[Maria-discuss] Questions about GIS functionality (vs MySQL, InnoDB, PostGIS...)
by Henrik Ingo 06 Aug '12

06 Aug '12

Hi Holyfoot, others I've been reading up on the state of GIS functionality. It would be great if I can get some answers directly from the source! 1) Comparing MariaDB and what's there in MySQL 5.6.1: are these identical but independent implementations? If there are differences, what are they? 2) Apparently PostGIS requires to do all kinds of gymnastics both when installing and when doing version upgrades. MySQL/MariaDB spatial functions are just there to be used, right? 3) Speaking of PostGIS, its manual reveals that their GiST R-tree index actually only works on the bounding rectangles of shapes. Is this the case also for MyISAM/Aria R-tree indexes, or would MariaDB actually filter the result set to only return shapes that are within the search shape for real. And btw, does the search shape have to be a box, or can it be any shape? 4) Lack of InnoDB R-tree indexes... What would it take to do that? Is the current implementation re-usable in any way (ie just store current R-tree indexes into InnoDB pages...) or would it have to be a separate implementation? 5) Euclidean geometrics only... PostGIS and SQLite use the separate GEOS library (and cousins like PROJ.4). Why isn't this used in the MySQL/MariaDB implementation? It seems to me, you could get accurate handling of different (non-euclidean) projections by using these libraries, "for free". henrik -- henrik.ingo(a)avoinelama.fi +358-40-8211286 skype: henrik.ingo irc: hingo www.openlife.cc My LinkedIn profile: http://www.linkedin.com/profile/view?id=9522559

2 3

[Maria-discuss] MariaDB repositories - GPG keys and website distro version references
by Arjen Lentz 02 Aug '12

02 Aug '12

Hi Daniel The repository tool on mariadb.com is awesome! I spotted a few things, hope you find the feedback of use: 1) On Debian/Ubuntu, apt-get will require a valid gpg key in its keyring to accept the packages. As root, you can do gpg --keyserver keyserver.ubuntu.com --recv-keys 1BB943DB gpg --export 1BB943DB | apt-key add - ... the other stuff apt-get update although sudo apt-key adv --recv-keys --keyserver keyserver.ubuntu.com 1BB943DB should also work. This adds your key and after that apt-get update will add the repo info to its package database so packages can be installed/upgraded. That said, the nicer method from Karmic (9.10) is sudo apt-get install python-software-properties sudo add-apt-repository <path> sudo apt-get update where <path> is the url you now represent for adding into the apt software sources. The distro tag (natty, etc) and 'main' get sorted out automatically by default. (so the first method needs to be displayed for 8.04 (Hardy) 2) the repo install info on mariadb.com does not show which new package names become available for installation/upgrade. It'd be great if it were to show a list of "now you can install the server by doing "sudo apt-get install/upgrade ...", if you want just the command line client do ..., for the client libraries do ... 3) the distro names currently don't show version numbers, e.g. Ubuntu Natty is not identified as 11.04 For both Ubuntu and Debian it'd be handy to have the numbers there also as it's clearer for users; some people are fine with the naming, others need the numbers. Cheers, Arjen. -- Arjen Lentz, Exec.Director @ Open Query (http://openquery.com) Australian peace of mind for your MySQL infrastructure. Follow us at http://openquery.com/blog/ & http://twitter.com/openquery

2 1

[Maria-discuss] KB Question: Upgrading MariaDB version
by Daniel Bartholomew 01 Aug '12

01 Aug '12

The following question has been posted to the Knowledgebase: http://kb.askmonty.org/en/upgrading-mariadb-version/ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Upgrading MariaDB version OS: RHEL 6.2 (2.6.32-279.1.1.el6.x86_64) I originally installed MariaDB version mariadb-5.1.61-Linux-x86_64 (using generic linux tarball) and was able to copy data under mariadb install and restarted mariadb. Everything with respect from transition of MySQL to MariaDB worked great. Now I am trying to upgrade MariaDB version mariadb-5.1.61-Linux-x86_64 to mariadb-5.5.25-linux-x86_64 (generic linux tarball). I shutdown the 5.1 MariaDB instance, re-created the link to point to the 5.5 distro. Then I restarted MariaDB instance and attempted to upgrade the database using mysql_upgrade -u root -p It looks it made it through information_schema and mysql databases without issue, but ran into some trouble with the database that I had copied in from original MySQL 5.1 instance (database= sahtest, sahtest.ACCESS_ACCOUNTS, Error: Table 'sahtest.ACCESS_ACCOUNTS' doesn't exist, Status: Operation failed). This error happens for all of the tables in the sahtest database. It also tried to Repair the tables of the sahtest database, failing with same error. mysql_upgrade finishes, so then I connect to mariadb and list databases. sahtest is there. If I say use sahtest; show tables; all the tables are there and look ok. Am I on the right track with how to install and upgrade from 5.1 to 5.5 version of MariaDB? TIA, Scott - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Thanks. -- Daniel Bartholomew Google+ - http://gplus.to/dbart Twitter - http://twitter.com/daniel_bart MariaDB: An Enhanced Drop-in Replacement for MySQL Website - http://mariadb.org Twitter - http://twitter.com/mariadb Google+ - http://gplus.to/mariadb Facebook - http://fb.com/MariaDB.dbms Knowledgebase - http://kb.askmonty.org Monty Program - http://montyprogram.com

1 0

[Maria-discuss] KB Question: InnoDB recovery under Maria
by Daniel Bartholomew 01 Aug '12

01 Aug '12

The following question has been posted to the Knowledgebase: http://kb.askmonty.org/en/innodb-recovery-under-maria/ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - InnoDB recovery under Maria Hi, I have been using MySQL for various embedded situation over the years. I am currently working on a new version of an existing project which I'm also migrating to MariaDB (I think I prefer Monty's style!). OK. Some tables in this database get update from an external source in a complex manner, so I am using InnoDB on these table with a transaction to ensure the operation is either completed or completely abandoned. This is an embedded app, and it can be interupted abruptly, leaving the InnoDB tables blocked. The procedure in this case is to set InnoDB recover to 4, dump the database, manually delete the InnoDB files, restart normally, restore, and then force an update from the external source. I'm hoping I will eventually be able to solve this using Aria tables, but in the meantime is there any way I can automate the process. I don't need to recover the data in the InnoDB tables following a crash, I just need to know that it has happened so I can get a new dataset. Thanks in advance for any help or suggestions. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Thanks. -- Daniel Bartholomew Google+ - http://gplus.to/dbart Twitter - http://twitter.com/daniel_bart MariaDB: An Enhanced Drop-in Replacement for MySQL Website - http://mariadb.org Twitter - http://twitter.com/mariadb Google+ - http://gplus.to/mariadb Facebook - http://fb.com/MariaDB.dbms Knowledgebase - http://kb.askmonty.org Monty Program - http://montyprogram.com

1 0

[Maria-discuss] Did we drop source for IBMDB2I?
by Colin Charles 28 Jul '12

28 Jul '12

Hi! Reading: http://kb.askmonty.org/en/mariadb-versus-mysql-features/ "IBMDB2I. Oracle removed this in MySQL 5.1.55 but we have kept the code in MariaDB until the version 5.5." I'm not so sure. I looked for this engine in a 5.5.25 tarball in storage/ and didn't see it. It is in 5.3 tree trunk, but not 5.5 Is this an oversight? Or have we decided to remove the engine? Thanks -- Colin Charles, http://bytebot.net/blog/ | twitter: @bytebot | skype: colincharles MariaDB: Community developed. Feature enhanced. Backward compatible. Download it at: http://www.mariadb.org/ Open MariaDB/MySQL documentation at the Knowledgebase: http://kb.askmonty.org/

2 1

[Maria-discuss] KB Question: GROUP BY trick has been optimized away
by Daniel Bartholomew 23 Jul '12

23 Jul '12

The following question has been posted to the Knowledgebase: https://kb.askmonty.org/en/group-by-trick-has-been-optimized-away/ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - GROUP BY trick has been optimized away Group-by trick example: Find the most populous city in each state: SELECT state, city, population, COUNT(*) AS num_cities FROM ( SELECT state, city, population FROM us ORDER BY state, population DESC ) p GROUP BY state ORDER BY state; +-------+-------------+------------+------------+ | state | city | population | num_cities | +-------+-------------+------------+------------+ | AK | Anchorage | 276263 | 16 | | AL | Birmingham | 231621 | 58 | | AR | Little Rock | 184217 | 40 | | AZ | Phoenix | 1428509 | 51 | | CA | Los Angeles | 3877129 | 447 | ... That was the output in MySQL 5.1. But with MariaDB 5.5.23, I get: +-------+-------------------+------------+------------+ | state | city | population | num_cities | +-------+-------------------+------------+------------+ | AK | Anchorage | 276263 | 16 | | AL | Alabaster | 26738 | 58 | | AR | Arkadelphia | 11062 | 40 | | AZ | Apache Junction | 34904 | 51 | | CA | Adelanto | 21955 | 447 | ... The EXPLAIN plan do longer shows a subquery, as if the inner ORDER BY has been thrown away. Granted, there is nothing in the definition of MySQL (much less in the SQL standard) that requires that Los Angeles should be bigger than Adelanto. But the replacement code for this 'trick' is quite messy. Am I correct in deducing (from the outside, looking in) that MariaDB's optimizations are the cause of the change? - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Thanks. -- Daniel Bartholomew Google+ - http://gplus.to/dbart Twitter - http://twitter.com/daniel_bart MariaDB: An Enhanced Drop-in Replacement for MySQL Website - http://mariadb.org Twitter - http://twitter.com/mariadb Google+ - http://gplus.to/mariadb Facebook - http://fb.com/MariaDB.dbms Knowledgebase - http://kb.askmonty.org Monty Program - http://montyprogram.com

1 0

[Maria-discuss] KB Question: DROP TABLE Syntax Causing Memory Leak
by Daniel Bartholomew 23 Jul '12

23 Jul '12

The following question has been posted to the Knowledgebase: https://kb.askmonty.org/en/drop-table-syntax-causeing-memory-leak/ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - DROP TABLE Syntax Causing Memory Leak I have a Server with 2 Xeon E5645 total 12cores and 24 threads on a X8DAH+-F-B Motherboard and 96Gigs of Memory and 4 Terabytes of hard drive space. We are running the newest stable release of MariaDB 5.5.25. every night I run a PHP script to bring a large data set roughly 500K records or so into a XtraDB Table I use as a "SWAP" table. I processing,filtering, massaging the data in this table then insert this processed data into other tables where it can be accessed by a web application. At the end of this Script I DROP this "SWAP" table. This Script runs 24 times a day and does not seem to have much issues. But For Some reason seemingly randomly the DROP table Command while checking permissions to drop the Table will lockup the database. I have tried truncate too and it seems to have the same issue. The innodb_buffer_pool_size=35G. Any Ideas what the problem could be or where to start looking? Noctechie - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Thanks. -- Daniel Bartholomew Google+ - http://gplus.to/dbart Twitter - http://twitter.com/daniel_bart MariaDB: An Enhanced Drop-in Replacement for MySQL Website - http://mariadb.org Twitter - http://twitter.com/mariadb Google+ - http://gplus.to/mariadb Facebook - http://fb.com/MariaDB.dbms Knowledgebase - http://kb.askmonty.org Monty Program - http://montyprogram.com

1 0

[Maria-discuss] MariaDB 5.5.25 now available
by Daniel Bartholomew 23 Jun '12

23 Jun '12

The MariaDB project is pleased to announce the immediate availability of MariaDB 5.5.25. This is a stable (GA) release. It includes MariaDB 5.3 and MySQL 5.5.25. - - MariaDB 5.5 Links - - - - - - - - - - - - - - - - - - - - - - - - - Release Notes: http://kb.askmonty.org/en/mariadb-5525-release-notes Changelog: http://kb.askmonty.org/en/mariadb-5525-changelog Downloads: http://downloads.mariadb.org/mariadb/5.5.25 APT and YUM Repository Configuration Generator: http://downloads.mariadb.org/mariadb/repositories/ Overview of MariaDB 5.5: http://kb.askmonty.org/en/what-is-mariadb-55 - - Where else to find us - - - - - - - - - - - - - - - - - - - - - - - We're on: Facebook: http://www.facebook.com/MariaDB.dbms Twitter: http://twitter.com/#!/mariadb Google+: http://gplus.to/mariadb Follow, friend, and add us to your circles to keep up to date with MariaDB! - - User Feedback plugin - - - - - - - - - - - - - - - - - - - - - - - MariaDB includes a User Feedback plugin. This plugin is disabled by default. If enabled, it submits basic, completely anonymous MariaDB usage information. This information is used by the developers to track trends in MariaDB usage to better guide development efforts. If you would like to help make MariaDB better, please add "plugin-load=feedback.so" to your my.cnf file! On Windows, add "feedback=ON" to your my.ini file, or click the checkbox during the installation of the MSI package. See http://kb.askmonty.org/en/user-feedback-plugin for more information. - - MariaDB Crash Course - - - - - - - - - - - - - - - - - - - - - - - The MariaDB-specific book, MariaDB Crash Course, by Ben Forta, is an excellent way to learn more about MariaDB. This book - for beginner to intermediate level users - will get you up and running with MariaDB, even if you've never used a database before. More information is available at: http://forta.com/books/0321799941/ - - Quality - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - The project always strives for quality, but in reality, nothing is perfect. Please take time to report any issues you encounter at: https://bugs.launchpad.net/maria We hope you enjoy MariaDB! -- Daniel Bartholomew MariaDB - http://mariadb.org Monty Program - http://montyprogram.com AskMonty Knowledgebase - http://kb.askmonty.org

1 0

[Maria-discuss] Compiling 5.5.20 on OS X
by Richard Dunn 03 Jun '12

03 Jun '12

I've been compiling MySQL and MariaDB on OS X for quite some time now, but this is the first time that I have ever used CMake to build an application. The 'make' step consistently fails with the following: Linking CXX executable ma_pagecache_consist_1k-t Undefined symbols for architecture x86_64: "_key_PAGECACHE_cache_lock", referenced from: _init_pagecache in libaria.a(ma_pagecache.c.o) ld: symbol(s) not found for architecture x86_64 I assume libaria.a is Maria specific. As a sanity check, I downloaded the MySQL source code for 5.5.21 from the MySQL site and I successfully compiled everything with CMake. Has anyone else successfully compiled a 64 bit 5.5.20 MariaDB on OS X? What am I missing?

5 9

[Maria-discuss] MariaDB 5.5.24 now available
by Daniel Bartholomew 31 May '12

31 May '12

The MariaDB project is pleased to announce the immediate availability of MariaDB 5.5.24. This is a stable (GA) release. It includes MariaDB 5.3.7 and MySQL 5.5.24. This version of MariaDB introduces new RPM packages for RHEL 5, CentOS 5 & 6, and Fedora 16. We have also created YUM repositories for those distributions. Setup instructions are available here: http://kb.askmonty.org/en/installing-mariadb-with-yum/ We are also now offering packages for BSD 9, MacOS X 10.5 (will be available within 24 hours), and Ubuntu 12.04 "Precise" (via our Ubuntu APT repository). - - MariaDB 5.5 Links - - - - - - - - - - - - - - - - - - - - - - - - - Release Notes: http://kb.askmonty.org/en/mariadb-5524-release-notes Changelog: http://kb.askmonty.org/en/mariadb-5524-changelog Downloads: http://downloads.askmonty.org/mariadb/5.5.24 APT and YUM Repository Configuration Generator: http://downloads.askmonty.org/mariadb/repositories/ Overview of MariaDB 5.5: http://kb.askmonty.org/en/what-is-mariadb-55 - - MariaDB Crash Course - - - - - - - - - - - - - - - - - - - - - - - The MariaDB-specific book, MariaDB Crash Course, by Ben Forta, is an excellent way to learn more about MariaDB. This book - for beginner to intermediate level users - will get you up and running with MariaDB, even if you've never used a database before. More information is available at: http://forta.com/books/0321799941/ - - User Feedback plugin - - - - - - - - - - - - - - - - - - - - - - - MariaDB includes a User Feedback plugin. This plugin is disabled by default. If enabled, it submits basic, completely anonymous MariaDB usage information. This information is used by the developers to track trends in MariaDB usage to better guide development efforts. If you would like to help make MariaDB better, please add "plugin-load=feedback.so" to your my.cnf file! On Windows, add "feedback=ON" to your my.ini file, or click the checkbox during the installation of the MSI package. See http://kb.askmonty.org/en/user-feedback-plugin for more information. - - Quality - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - The project always strives for quality, but in reality, nothing is perfect. Please take time to report any issues you encounter at: https://bugs.launchpad.net/maria - - Where else to find us - - - - - - - - - - - - - - - - - - - - - - - We're on Facebook: http://www.facebook.com/MariaDB.dbms We're on Twitter: http://twitter.com/#!/mariadb We're on Google Plus: http://gplus.to/mariadb We hope you enjoy MariaDB! -- Daniel Bartholomew MariaDB - http://mariadb.org Monty Program - http://montyprogram.com AskMonty Knowledgebase - http://kb.askmonty.org

1 0

Re: [Maria-discuss] Maria/Aria unit test failures
by Brian Evans 25 Apr '12

25 Apr '12

On 4/14/2012 1:31 AM, Oleksandr Byelkin wrote: > 11.04.2012 23:51, Brian Evans написал: >> I'm trying to pin down why unit tests fail for the 5.1, 5.2 and 5.3 >> series of the (m)aria engine. >> >> My build tool runs 'make test-unit' and the following errors appear. >> The build tool does strip out some environment variables, but running >> from bash directly doesn't change anything. >> >> Can anyone provide pointers? >> >> Thanks >> >> (This is from MariaDB 5.1.62) >> >> [16:34:05] ../storage/maria/unittest/ma_test_all-t ..................... >> 73/830 >> Failed test '../storage/maria/unittest/../ma_test2 -s -htmp -m10000 >> -e4096 -K ' (loop iteration 8.) at line 316 >> (errcode: 256, test: 83) >> [16:34:05] ../storage/maria/unittest/ma_test_all-t ..................... > > Could you describe condition of running (OS, 32/64 bit and so on). I > can't repeat it so need more information. > > [skip] Sure. This is output from my build tool which lists important libraries and the environment used. OS is Gentoo Linux. Architecture is x86_64. Portage 2.1.10.49 (default/linux/amd64/10.0, gcc-4.5.3, glibc-2.13-r4, 2.6.38-gentoo-r6 x86_64) ================================================================= System uname: Linux-2.6.38-gentoo-r6-x86_64-Intel-R-_Xeon-TM-_CPU_3.40GHz-with-gentoo-2.0.3 Timestamp of tree: Thu, 29 Mar 2012 19:30:01 +0000 app-shells/bash: 4.2_p20 dev-lang/python: 2.7.2-r3, 3.1.4-r3, 3.2.2 dev-util/cmake: 2.8.6-r4 dev-util/pkgconfig: 0.26 sys-apps/baselayout: 2.0.3 sys-apps/openrc: 0.9.8.4 sys-apps/sandbox: 2.5 sys-devel/autoconf: 2.68 sys-devel/automake: 1.9.6-r3, 1.11.1 sys-devel/binutils: 2.21.1-r1 sys-devel/gcc: 4.5.3-r1 sys-devel/gcc-config: 1.5-r2 sys-devel/libtool: 2.4-r1 sys-devel/make: 3.82-r1 sys-kernel/linux-headers: 3.1 (virtual/os-headers) sys-libs/glibc: 2.13-r4 CBUILD="x86_64-pc-linux-gnu" CFLAGS="-O2 -pipe -march=nocona" CHOST="x86_64-pc-linux-gnu" CXXFLAGS="-O2 -pipe -march=nocona" LANG="en_US.UTF-8" LDFLAGS="-Wl,-O1 -Wl,--as-needed" MAKEOPTS="-j5"

2 3

Re: [Maria-discuss] MariaDB & InnoDB native aio disabled
by Axel Schwenke 25 Apr '12

25 Apr '12

Hi Jocelyn, jocelyn fournier wrote: > > I've just figured out after installing MariaDB 5.5.23 on two server (one > directly from the x64 binary, and the other using the debian packing) > that innodb_use_native_aio is OFF on the two servers. ... > Am I missing something ? No, you are right. It seems both the tar.gz and deb packages provided by us are built without libaio. For the deb packages, we regard this a bug and I created this bug report: https://bugs.launchpad.net/maria/+bug/988204 For the tar.gz packages, we are rather reluctant to add additional dependencies like libaio. Unless deb, a tar.gz package cannot announce such dependencies, so users might end with a dysfunctional installation without a warning. We will review this decision internally. Thank you for reporting this problem! Axel Schwenke Senior Performance Engineer, MariaDB Services AB

1 0

[Maria-discuss] getting all name-value pairs from a dynamic column
by MARK CALLAGHAN 13 Apr '12

13 Apr '12

These docs are excellent -- http://kb.askmonty.org/en/dynamic-columns How do you fetch all name-value pairs from a dynamic column in a format that can be consumed by a client? The client can select the column as is but then must know how mariadb encoded it. The function column_list returns the column names. If there were a function that encoded all name-value pairs as JSON, then the client could do something like this and be able to decode the result: select column_json(dynamic_column_name) from t where ... -- Mark Callaghan mdcallag(a)gmail.com

4 9

[Maria-discuss] Maria/Aria unit test failures
by Brian Evans 11 Apr '12

11 Apr '12

I'm trying to pin down why unit tests fail for the 5.1, 5.2 and 5.3 series of the (m)aria engine. My build tool runs 'make test-unit' and the following errors appear. The build tool does strip out some environment variables, but running from bash directly doesn't change anything. Can anyone provide pointers? Thanks (This is from MariaDB 5.1.62) [16:34:05] ../storage/maria/unittest/ma_test_all-t ..................... 73/830 Failed test '../storage/maria/unittest/../ma_test2 -s -htmp -m10000 -e4096 -K ' (loop iteration 8.) at line 316 (errcode: 256, test: 83) [16:34:05] ../storage/maria/unittest/ma_test_all-t ..................... 85/830 Failed test '../storage/maria/unittest/../ma_test2 -s -htmp -m10000 -e8192 -K ' (loop iteration 9.) at line 316 (errcode: 256, test: 85) Failed test '../storage/maria/unittest/../ma_test2 -s -htmp -m10000 -e16384 -E16384 -K -L ' (loop iteration 10.) at line 316 (errcode: 256, test: 87) [16:34:05] ../storage/maria/unittest/ma_test_all-t ..................... 238/830 Failed test '../storage/maria/unittest/../ma_test2 -s -htmp -m10000 -e4096 -K -S' (loop iteration 8.) at line 316 (errcode: 256, test: 242) Failed test '../storage/maria/unittest/../ma_test2 -s -htmp -m10000 -e8192 -K -S' (loop iteration 9.) at line 316 (errcode: 256, test: 244) [16:34:05] ../storage/maria/unittest/ma_test_all-t ..................... 246/830 Failed test '../storage/maria/unittest/../ma_test2 -s -htmp -m10000 -e16384 -E16384 -K -L -S' (loop iteration 10.) at line 316 (errcode: 256, test: 246) [16:34:05] ../storage/maria/unittest/ma_test_all-t ..................... 399/830 Failed test '../storage/maria/unittest/../ma_test2 -s -htmp -m10000 -e4096 -K -M' (loop iteration 8.) at line 316 (errcode: 256, test: 401) Failed test '../storage/maria/unittest/../ma_test2 -s -htmp -m10000 -e8192 -K -M' (loop iteration 9.) at line 316 (errcode: 256, test: 403) Failed test '../storage/maria/unittest/../ma_test2 -s -htmp -m10000 -e16384 -E16384 -K -L -M' (loop iteration 10.) at line 316 (errcode: 256, test: 405) [16:34:05] ../storage/maria/unittest/ma_test_all-t ..................... 557/830 Failed test '../storage/maria/unittest/../ma_test2 -s -htmp -m10000 -e4096 -K -M -T' (loop iteration 8.) at line 316 (errcode: 256, test: 560) Failed test '../storage/maria/unittest/../ma_test2 -s -htmp -m10000 -e8192 -K -M -T' (loop iteration 9.) at line 316 (errcode: 256, test: 562) [16:34:05] ../storage/maria/unittest/ma_test_all-t ..................... 564/830 Failed test '../storage/maria/unittest/../ma_test2 -s -htmp -m10000 -e16384 -E16384 -K -L -M -T' (loop iteration 10.) at line 316 (errcode: 256, test: 564) [16:34:05] ../storage/maria/unittest/ma_test_all-t ..................... 716/830 Failed test '../storage/maria/unittest/../ma_test2 -s -htmp -m10000 -e4096 -K -M -T -C' (loop iteration 8.) at line 316 (errcode: 256, test: 719) [16:34:05] ../storage/maria/unittest/ma_test_all-t ..................... 721/830 Failed test '../storage/maria/unittest/../ma_test2 -s -htmp -m10000 -e8192 -K -M -T -C' (loop iteration 9.) at line 316 (errcode: 256, test: 721) Failed test '../storage/maria/unittest/../ma_test2 -s -htmp -m10000 -e16384 -E16384 -K -L -M -T -C' (loop iteration 10.) at line 316 (errcode: 256, test: 723) [16:34:05] ../storage/maria/unittest/ma_test_all-t ..................... Dubious, test returned 1 (wstat 256, 0x100) Failed 15/830 subtests

1 0

[Maria-discuss] MariaDB 5.5.23 stable (GA) now available
by Daniel Bartholomew 11 Apr '12

11 Apr '12

The MariaDB project is pleased to announce the immediate availability of MariaDB 5.5.23. This is a stable (GA) release. It includes MariaDB 5.3.6 and MySQL 5.5.23, some performance improvements, and bug fixes. This is the first stable (GA) release in the MariaDB 5.5 series. - - MariaDB 5.5 Links - - - - - - - - - - - - - - - - - - - - - - - - - Release Notes: http://kb.askmonty.org/en/mariadb-5523-release-notes Changelog: http://kb.askmonty.org/en/mariadb-5523-changelog Downloads: http://downloads.askmonty.org/mariadb/5.5.23 .deb Repositories: http://downloads.askmonty.org/mariadb/repositories/ Overview of MariaDB 5.5: http://kb.askmonty.org/en/what-is-mariadb-55 - - SkySQL and MariaDB: Solutions Day - - - - - - - - - - - - - - - - - We'll be co-hosting the the "SkySQL & MariaDB: Solutions Day for the MySQL® Database" one day event on 13 April, 2012, at the Hyatt Regency Santa Clara. During this event, attendees will receive free, hands-on training and consulting on MariaDB and MySQL® database solutions from the experts at SkySQL, MariaDB, Continuent, ScaleDB, Severalnines, Sphinx, and Webyog, among others. SkySQL and MariaDB will bring together industry visionaries, including Michael (Monty) Widenius and David Axmark, the original authors of the MySQL database, to share their insights on current and future trends pertaining to the world's most popular open source database. To learn more about this free event, visit: http://www.skysql.com/events/mysql-solutions-day The schedule for the event is here: http://www.skysql.com/events/mysql-solutions-day/schedule Attendees are also invited to participate in Drizzle Day - a parallel event co-hosted by SkySQL, Percona, and the Drizzle Development Team, featuring tutorials on the Drizzle database. - - MariaDB Crash Course - - - - - - - - - - - - - - - - - - - - - - - The MariaDB-specific book, MariaDB Crash Course, by Ben Forta, is an excellent way to learn more about MariaDB. This book - for beginner to intermediate level users - will get you up and running with MariaDB, even if you've never used a database before. More information is available at: http://forta.com/books/0321799941/ - - User Feedback plugin - - - - - - - - - - - - - - - - - - - - - - - MariaDB includes a User Feedback plugin. This plugin is disabled by default. If enabled, it submits basic, completely anonymous MariaDB usage information. This information is used by the developers to track trends in MariaDB usage to better guide development efforts. If you would like to help make MariaDB better, please add "plugin-load=feedback.so" to your my.cnf file! On Windows, add "feedback=ON" to your my.ini file, or click the checkbox during the installation of the MSI package. See http://kb.askmonty.org/en/user-feedback-plugin for more information. - - Quality - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - The project always strives for quality, but in reality, nothing is perfect. Please take time to report any issues you encounter at: https://bugs.launchpad.net/maria - - Where else to find us - - - - - - - - - - - - - - - - - - - - - - - We're on Facebook: http://www.facebook.com/MariaDB.dbms We're on Twitter: http://twitter.com/#!/mariadb We're on Google Plus: http://gplus.to/mariadb We hope you enjoy MariaDB! -- Daniel Bartholomew MariaDB - http://mariadb.org Monty Program - http://montyprogram.com AskMonty Knowledgebase - http://kb.askmonty.org

1 0

[Maria-discuss] MariaDB 5.3.6 now available
by Daniel Bartholomew 09 Apr '12

09 Apr '12

The MariaDB project is pleased to announce the immediate availability of MariaDB 5.3.6. This is a stable (GA) release. It includes MySQL 5.1.62, some performance improvements, and several bug fixes. Most importantly, MariaDB 5.3.6 includes a fix for a bug which, under certain rare circumstances, allowed a user to connect with an invalid password. This is a serious security issue. We recommend upgrading from older versions as soon as possible. - - MariaDB 5.3 Links - - - - - - - - - - - - - - - - - - - - - - - - - Release Notes: http://kb.askmonty.org/en/mariadb-536-release-notes Changelog: http://kb.askmonty.org/en/mariadb-536-changelog Downloads: http://downloads.askmonty.org/mariadb/5.3.6 .deb Repositories: http://downloads.askmonty.org/mariadb/repositories/ Overview of MariaDB 5.3: http://kb.askmonty.org/en/what-is-mariadb-53 - - SkySQL and MariaDB: Solutions Day - - - - - - - - - - - - - - - - - We'll be co-hosting the the "SkySQL & MariaDB: Solutions Day for the MySQL® Database" one day event on 13 April, 2012, at the Hyatt Regency Santa Clara. During this event, attendees will receive free, hands-on training and consulting on MariaDB and MySQL® database solutions from the experts at SkySQL, MariaDB, Continuent, ScaleDB, Severalnines, Sphinx, and Webyog, among others. SkySQL and MariaDB will bring together industry visionaries, including Michael (Monty) Widenius and David Axmark, the original authors of the MySQL database, to share their insights on current and future trends pertaining to the world's most popular open source database. To learn more about this free event, visit: http://www.skysql.com/events/mysql-solutions-day The schedule for the event is here: http://www.skysql.com/events/mysql-solutions-day/schedule Attendees are also invited to participate in Drizzle Day - a parallel event co-hosted by SkySQL, Percona, and the Drizzle Development Team, featuring tutorials on the Drizzle database. - - MariaDB Crash Course - - - - - - - - - - - - - - - - - - - - - - - The MariaDB-specific book, MariaDB Crash Course, by Ben Forta, is an excellent way to learn more about MariaDB. This book - for beginner to intermediate level users - will get you up and running with MariaDB, even if you've never used a database before. More information is available at: http://forta.com/books/0321799941/ - - User Feedback plugin - - - - - - - - - - - - - - - - - - - - - - - MariaDB includes a User Feedback plugin. This plugin is disabled by default. If enabled, it submits basic, completely anonymous MariaDB usage information. This information is used by the developers to track trends in MariaDB usage to better guide development efforts. If you would like to help make MariaDB better, please add "plugin-load=feedback.so" to your my.cnf file! On Windows, add "feedback=ON" to your my.ini file, or click the checkbox during the installation of the MSI package. See http://kb.askmonty.org/en/user-feedback-plugin for more information. - - Quality - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - The project always strives for quality, but in reality, nothing is perfect. Please take time to report any issues you encounter at: https://bugs.launchpad.net/maria - - Where else to find us - - - - - - - - - - - - - - - - - - - - - - - We're on Facebook: http://www.facebook.com/MariaDB.dbms We're on Twitter: http://twitter.com/#!/mariadb We're on Google Plus: http://gplus.to/mariadb We hope you enjoy MariaDB! -- Daniel Bartholomew MariaDB - http://mariadb.org Monty Program - http://montyprogram.com AskMonty Knowledgebase - http://kb.askmonty.org

1 0

[Maria-discuss] MariaDB 5.1.62 and 5.2.12 now available
by Daniel Bartholomew 06 Apr '12

06 Apr '12

The MariaDB project is pleased to announce the immediate availability of MariaDB 5.1.62 and 5.2.12. Both of these are stable (RC) releases and include MySQL 5.1.62 and several bug fixes. Most importantly, MariaDB 5.1.62 and 5.2.12 include a fix for a bug that under certain rare circumstances allowed a user to connect with an invalid password. This is a serious security issue. We recommend upgrading from older versions as soon as possible. - - MariaDB 5.1.62 Links - - - - - - - - - - - - - - - - - - - - - - - - Release Notes: http://kb.askmonty.org/en/mariadb-5162-release-notes Changelog: http://kb.askmonty.org/en/mariadb-5162-changelog Downloads: http://downloads.askmonty.org/mariadb/5.1.62 .deb Repositories: http://downloads.askmonty.org/mariadb/repositories/ Overview of MariaDB 5.1: http://kb.askmonty.org/en/what-is-mariadb-51 - - MariaDB 5.2.12 Links - - - - - - - - - - - - - - - - - - - - - - - Release Notes: http://kb.askmonty.org/en/mariadb-5212-release-notes Changelog: http://kb.askmonty.org/en/mariadb-5212-changelog Downloads: http://downloads.askmonty.org/mariadb/5.2.12 .deb Repositories: http://downloads.askmonty.org/mariadb/repositories/ Overview of MariaDB 5.2: http://kb.askmonty.org/en/what-is-mariadb-52 - - SkySQL and MariaDB: Solutions Day - - - - - - - - - - - - - - - - - We'll be co-hosting the the "SkySQL & MariaDB: Solutions Day for the MySQL® Database" one day event on 13 April, 2012, at the Hyatt Regency Santa Clara. During this event, attendees will receive free, hands-on training and consulting on MariaDB and MySQL® database solutions from the experts at SkySQL, MariaDB, Continuent, ScaleDB, Severalnines, Sphinx, and Webyog, among others. SkySQL and MariaDB will bring together industry visionaries, including Michael (Monty) Widenius and David Axmark, the original authors of the MySQL database, to share their insights on current and future trends pertaining to the world's most popular open source database. To learn more about this free event, visit: http://www.skysql.com/events/mysql-solutions-day The schedule for the event is here: http://www.skysql.com/events/mysql-solutions-day/schedule Attendees are also invited to participate in Drizzle Day - a parallel event co-hosted by SkySQL, Percona, and the Drizzle Development Team, featuring tutorials on the Drizzle database. - - User Feedback plugin - - - - - - - - - - - - - - - - - - - - - - - MariaDB includes a User Feedback plugin. This plugin is disabled by default. If enabled, it submits basic, completely anonymous MariaDB usage information. This information is used by the developers to track trends in MariaDB usage to better guide development efforts. If you would like to help make MariaDB better, please add "plugin-load=feedback.so" to your my.cnf file! On Windows, add "feedback=ON" to your my.ini file, or click the checkbox during the installation of the MSI package. See http://kb.askmonty.org/en/user-feedback-plugin for more information. - - Quality - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - The project always strives for quality, but in reality, nothing is perfect. Please take time to report any issues you encounter at: https://bugs.launchpad.net/maria - - Where else to find us - - - - - - - - - - - - - - - - - - - - - - - We're on Facebook: http://www.facebook.com/MariaDB.dbms We're on Twitter: http://twitter.com/#!/mariadb We're on Google Plus: http://gplus.to/mariadb We hope you enjoy MariaDB! -- Daniel Bartholomew MariaDB - http://mariadb.org Monty Program - http://montyprogram.com AskMonty Knowledgebase - http://kb.askmonty.org

1 1

[Maria-discuss] MariaDB 5.1.61 and 5.2.11 now available
by Daniel Bartholomew 02 Apr '12

02 Apr '12

The MariaDB project is pleased to announce the immediate availability of MariaDB 5.1.61 and 5.2.11. Both of these are stable (RC) releases and include MySQL 5.1.61 and several bug fixes. Please see the "What is MariaDB 5.1" page for an overview of MariaDB 5.1: http://kb.askmonty.org/en/what-is-mariadb-51 Please see the "What is MariaDB 5.2" page for an overview of MariaDB 5.2: http://kb.askmonty.org/en/what-is-mariadb-52 - - MariaDB 5.1.61 Release Notes, Changelog, Downloads - - - - - - - The release notes for MariaDB 5.1.61 are available at: http://kb.askmonty.org/en/mariadb-5161-release-notes A changelog for this release is available at: http://kb.askmonty.org/en/mariadb-5161-changelog Sources, binaries and packages can be downloaded from: http://downloads.askmonty.org/mariadb/5.1.61 - - MariaDB 5.2.11 Release Notes, Changelog, Downloads - - - - - - - The release notes for MariaDB 5.2.11 are available at: http://kb.askmonty.org/en/mariadb-5211-release-notes A changelog for this release is available at: http://kb.askmonty.org/en/mariadb-5211-changelog Sources, binaries and packages can be downloaded from: http://downloads.askmonty.org/mariadb/5.2.11 Debian and Ubuntu packages for both releases are available from our mirrored apt repositories. A sources.list generator can be found at: http://downloads.askmonty.org/mariadb/repositories/ - - SkySQL and MariaDB: Solutions Day - - - - - - - - - - - - - - - - - We'll be co-hosting the the "SkySQL & MariaDB: Solutions Day for the MySQL® Database" one day event on 13 April, 2012, at the Hyatt Regency Santa Clara. During this event, attendees will receive free, hands-on training and consulting on MariaDB and MySQL® database solutions from the experts at SkySQL, MariaDB, Continuent, ScaleDB, Severalnines, Sphinx, and Webyog, among others. SkySQL and MariaDB will bring together industry visionaries, including Michael (Monty) Widenius and David Axmark, the original authors of the MySQL database, to share their insights on current and future trends pertaining to the world's most popular open source database. To learn more about this free event, visit http://www.skysql.com/events/mysql-solutions-day The schedule for the event is here: http://www.skysql.com/events/mysql-solutions-day/schedule Attendees are also invited to participate in Drizzle Day - a parallel event co-hosted by SkySQL, Percona, and the Drizzle Development Team, featuring tutorials on the Drizzle database. - - User Feedback plugin - - - - - - - - - - - - - - - - - - - - - - - MariaDB includes a User Feedback plugin. This plugin is disabled by default. If enabled, it submits basic, completely anonymous MariaDB usage information. This information is used by the developers to track trends in MariaDB usage to better guide development efforts. If you would like to help make MariaDB better, please add "plugin-load=feedback.so" to your my.cnf file! On Windows, add "feedback=ON" to your my.ini file, or click the checkbox during the installation of the MSI package. See http://kb.askmonty.org/en/user-feedback-plugin for more information. - - Quality - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - The project always strives for quality, but in reality, nothing is perfect. Please take time to report any issues you encounter at: https://bugs.launchpad.net/maria - - Where else to find us - - - - - - - - - - - - - - - - - - - - - - - We're on Facebook: http://www.facebook.com/MariaDB.dbms We're on Twitter: http://twitter.com/#!/mariadb We're on Google Plus: http://gplus.to/mariadb We hope you enjoy MariaDB! -- Daniel Bartholomew MariaDB - http://mariadb.org Monty Program - http://montyprogram.com AskMonty Knowledgebase - http://kb.askmonty.org

1 0

[Maria-discuss] Test failure with 5.5.22 on plugins.unix_socket
by Brian Evans 30 Mar '12

30 Mar '12

I'm getting a strange error with 5.5.22 (and 5.5.21) in the test runs. plugins.unix_socket [ fail ] Test ended at 2012-03-30 11:16:46 CURRENT_TEST: plugins.unix_socket mysqltest: At line 15: Can't initialize replace from 'replace_result $USER USER' The result from queries just before the failure was: install plugin unix_socket soname 'auth_socket.so'; # # with named user # Is this a test program issue? Brian

2 2

[Maria-discuss] MariaDB 5.5.22 release candidate now available
by Daniel Bartholomew 30 Mar '12

30 Mar '12

The MariaDB project is pleased to announce the immediate availability of MariaDB 5.5.22 release candidate (RC). MariaDB 5.5.22 is the first RC release in the 5.5 series. We hope to follow it up soon with a stable (GA) 5.5 release. Please test this release thoroughly! This is the third 5.5-based release. The MariaDB 5.5 series is the combination of MariaDB 5.3 and MySQL 5.5 with a few extra features and bug fixes. Please read the "What is MariaDB 5.5" page for an overview: http://kb.askmonty.org/en/what-is-mariadb-55 - - MariaDB 5.5.22 RC Release Notes, Changelog, Downloads - - - - - - - The release notes for MariaDB 5.5.22 RC are available at: http://kb.askmonty.org/en/mariadb-5522-release-notes A changelog for this release is available at: http://kb.askmonty.org/en/mariadb-5522-changelog Sources, binaries and packages can be downloaded from: http://downloads.askmonty.org/mariadb/5.5.22/ Debian and Ubuntu packages are available from our mirrored apt repositories. A sources.list generator can be found at: http://downloads.askmonty.org/mariadb/repositories/ - - About MariaDB 5.5 - - - - - - - - - - - - - - - - - - - - - - - - - The MariaDB 5.5 series is the combination of MariaDB 5.3 and MySQL 5.5. Please read the "What is MariaDB 5.5" page for details: http://kb.askmonty.org/en/what-is-mariadb-55 - - SkySQL and MariaDB: Solutions Day - - - - - - - - - - - - - - - - - We'll be co-hosting the the "SkySQL & MariaDB: Solutions Day for the MySQL® Database" one day event on 13 April, 2012, at the Hyatt Regency Santa Clara. During this event, attendees will receive free, hands-on training and consulting on MariaDB and MySQL® database solutions from the experts at SkySQL, MariaDB, Continuent, ScaleDB, Severalnines, Sphinx, and Webyog, among others. SkySQL and MariaDB will bring together industry visionaries, including Michael (Monty) Widenius and David Axmark, the original authors of the MySQL database, to share their insights on current and future trends pertaining to the world's most popular open source database. To learn more about this free event, visit http://www.skysql.com/events/mysql-solutions-day The schedule for the event is here: http://www.skysql.com/events/mysql-solutions-day/schedule Attendees are also invited to participate in Drizzle Day – a parallel event co-hosted by SkySQL, Percona, and the Drizzle Development Team, featuring tutorials on the Drizzle database. - - User Feedback plugin - - - - - - - - - - - - - - - - - - - - - - - MariaDB includes a User Feedback plugin. This plugin is disabled by default. If enabled, it submits basic, completely anonymous MariaDB usage information. This information is used by the developers to track trends in MariaDB usage to better guide development efforts. If you would like to help make MariaDB better, please add --plugin-load=feedback.so to your my.cnf file! On Windows, add "feedback=ON" to your my.ini file, or click the checkbox during the installation of the MSI package. See http://kb.askmonty.org/en/user-feedback-plugin for more information. - - Quality - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - The project always strives for quality, but in reality, nothing is perfect. Please take time to report any issues you encounter at: https://bugs.launchpad.net/maria - - Where else to find us - - - - - - - - - - - - - - - - - - - - - - - We're on Facebook: http://www.facebook.com/MariaDB.dbms We're on Twitter: http://twitter.com/#!/mariadb We're on Google Plus: http://gplus.to/mariadb We hope you enjoy MariaDB! -- Daniel Bartholomew MariaDB - http://mariadb.org Monty Program - http://montyprogram.com AskMonty Knowledgebase - http://kb.askmonty.org

1 0

[Maria-discuss] Blog post: What about the subqueries?
by Colin Charles 30 Mar '12

30 Mar '12

Hi! This came up on my radar: http://mysqlmaniac.com/2012/what-about-the-subqueries/ MariaDB does wonderfully for Q1, but not so well for Q2 on some specific queries. These were made with the MediaWiki extension called DynamicPageList (http://www.mediawiki.org/wiki/Extension:DynamicPageList_%28third-party%29) -- Colin Charles, http://bytebot.net/blog/ | twitter: @bytebot | skype: colincharles MariaDB: Community developed. Feature enhanced. Backward compatible. Download it at: http://www.mariadb.org/ Open MariaDB/MySQL documentation at the Knowledgebase: http://kb.askmonty.org/

1 0

Re: [Maria-discuss] Compiling 5.5.20 on OS X
by Richard Dunn 27 Mar '12

27 Mar '12

Hi Colin, I actually get a little farther along (83% instead of 77%), but it looks like we're failing at the same spot -- Linking CXX executable ma_pagecache_consist_1k-t [ 83%] Building C object storage/maria/unittest/CMakeFiles/ma_control_file-t.dir/ma_control_file-t.c.o Linking CXX executable ma_control_file-t [ 83%] Built target ma_control_file-t Scanning dependencies of target ma_pagecache_consist_1k-t [ 83%] Building C object storage/maria/unittest/CMakeFiles/ma_pagecache_consist_1k-t.dir/ma_pagecache_consist.c.o [ 83%] Building C object storage/maria/unittest/CMakeFiles/ma_pagecache_consist_1k-t.dir/test_file.c.o Linking CXX executable ma_pagecache_consist_1k-t Undefined symbols for architecture x86_64: "_key_PAGECACHE_cache_lock", referenced from: _init_pagecache in libaria.a(ma_pagecache.c.o) ld: symbol(s) not found for architecture x86_64 collect2: ld returned 1 exit status make[2]: *** [storage/maria/unittest/ma_pagecache_consist_1k-t] Error 1 make[1]: *** [storage/maria/unittest/CMakeFiles/ma_pagecache_consist_1k-t.dir/all] Error 2 make: *** [all] Error 2 Richard On Mar 27, 2012, at 04:52 , Colin Charles wrote: > Hi! > > On 17 Mar 2012, at 19:21, Richard Dunn wrote: > >> Same problem with MariaDB 5.5.21... >> > > Is this what you see currently? Produced this using 5.5.21 using BUILD/compile-pentium64-max > > [ 77%] Building C object storage/maria/unittest/CMakeFiles/ma_pagecache_consist_64k-t.dir/test_file.c.o > Linking CXX executable ma_pagecache_consist_1kRD-t > Linking CXX executable ma_pagecache_consist_1kWR-t > Undefined symbols for architecture x86_64: > "_key_PAGECACHE_cache_lock", referenced from: > _init_pagecache in libaria.a(ma_pagecache.c.o) > ld: symbol(s) not found for architecture x86_64 > collect2: ld returned 1 exit status > Undefined symbols for architecture x86_64: > "_key_PAGECACHE_cache_lock", referenced from: > _init_pagecache in libaria.a(ma_pagecache.c.o) > ld: symbol(s) not found for architecture x86_64 > collect2: ld returned 1 exit status > make[2]: *** [storage/maria/unittest/ma_pagecache_consist_1kRD-t] Error 1 > make[1]: *** [storage/maria/unittest/CMakeFiles/ma_pagecache_consist_1kRD-t.dir/all] Error 2 > make[2]: *** [storage/maria/unittest/ma_pagecache_consist_1kWR-t] Error 1 > make[1]: *** [storage/maria/unittest/CMakeFiles/ma_pagecache_consist_1kWR-t.dir/all] Error 2 > Linking CXX executable ma_pagecache_consist_64k-t > Undefined symbols for architecture x86_64: > "_key_PAGECACHE_cache_lock", referenced from: > _init_pagecache in libaria.a(ma_pagecache.c.o) > ld: symbol(s) not found for architecture x86_64 > collect2: ld returned 1 exit status > make[2]: *** [storage/maria/unittest/ma_pagecache_consist_64k-t] Error 1 > make[1]: *** [storage/maria/unittest/CMakeFiles/ma_pagecache_consist_64k-t.dir/all] Error 2 > [ 88%] Built target sql > make: *** [all] Error 2 > > >> >> On Mar 4, 2012, at 07:53 , Richard Dunn wrote: >> >>> I've been compiling MySQL and MariaDB on OS X for quite some time now, but this is the first time that I have ever used CMake to build an application. The 'make' step consistently fails with the following: >>> >>> Linking CXX executable ma_pagecache_consist_1k-t >>> Undefined symbols for architecture x86_64: >>> "_key_PAGECACHE_cache_lock", referenced from: >>> _init_pagecache in libaria.a(ma_pagecache.c.o) >>> ld: symbol(s) not found for architecture x86_64 >>> >>> I assume libaria.a is Maria specific. >>> >>> As a sanity check, I downloaded the MySQL source code for 5.5.21 from the MySQL site and I successfully compiled everything with CMake. >>> >>> Has anyone else successfully compiled a 64 bit 5.5.20 MariaDB on OS X? What am I missing? >> >> >> _______________________________________________ >> Mailing list: https://launchpad.net/~maria-discuss >> Post to : maria-discuss(a)lists.launchpad.net >> Unsubscribe : https://launchpad.net/~maria-discuss >> More help : https://help.launchpad.net/ListHelp > > -- > Colin Charles, http://bytebot.net/blog/ | twitter: @bytebot | skype: colincharles > MariaDB: Community developed. Feature enhanced. Backward compatible. > Download it at: http://www.mariadb.org/ > Open MariaDB/MySQL documentation at the Knowledgebase: http://kb.askmonty.org/ >

1 0

Re: [Maria-discuss] Compiling 5.5.20 on OS X
by Richard Dunn 27 Mar '12

27 Mar '12

Hi Sergei, The build log is attached. Thanks for your help! Richard On Mar 26, 2012, at 12:25 , Sergei Golubchik wrote: > Hi, Richard! > > I don't have an OS X build environment at the moment. > I'll try to help you and fix that, but I'll be asking a lot of > questions. Sorry for this. > > On Mar 04, Richard Dunn wrote: >> I've been compiling MySQL and MariaDB on OS X for quite some time now, >> but this is the first time that I have ever used CMake to build an >> application. The 'make' step consistently fails with the following: >> >> Linking CXX executable ma_pagecache_consist_1k-t >> Undefined symbols for architecture x86_64: >> "_key_PAGECACHE_cache_lock", referenced from: >> _init_pagecache in libaria.a(ma_pagecache.c.o) >> ld: symbol(s) not found for architecture x86_64 >> >> I assume libaria.a is Maria specific. > > Can you show the complete build log? > To collect it you can run "make VERBOSE=1 -k >& log". > The file might be quite big, don't forget to gzip it before emailing. > > Regards, > Sergei

1 0

[Maria-discuss] New KB Question: Maximum number of indexes supported by Xtradb
by Daniel Bartholomew 27 Mar '12

27 Mar '12

A new question has been posted to the Knowledgebase: http://kb.askmonty.org/en/maximum-number-of-indexes-supported-by-xtradb ----------------------------------------------------------------------- What is the maximum number of indexes allowed per-table when using the Xtradb storage engine? ----------------------------------------------------------------------- Thanks. -- Daniel Bartholomew MariaDB - http://mariadb.org Monty Program - http://montyprogram.com AskMonty Knowledgebase - http://kb.askmonty.org

1 0

[Maria-discuss] Wrong ordering in MariaDB 5.2.10
by Brian Evans 16 Mar '12

16 Mar '12

We are hitting a wrong ordering in 5.2.10 but it does not happen on a test box using 5.3 series (tried 5.3.3 and 5.3.5). The query can be rewritten and when we do, the range becomes an index scan and produces the correct results. Here are the queries: [Incorrect Order] SELECT SUBSTRING(StockNo, 3, 3) AS $number FROM inv WHERE StockNo LIKE 'JR%' OR StockNo LIKE 'VS%' OR StockNo LIKE 'JB%' OR StockNo LIKE 'JG%' ORDER BY $number DESC LIMIT 1; EXPLAIN Result id select_type table type possible_keys key key_len ref rows Extra 1 SIMPLE inv range PRIMARY PRIMARY 66 (NULL) 4 Using where; Using index; Using filesort [Correct Order] SELECT SUBSTRING(StockNo, 3, 3) AS $number FROM inv WHERE LEFT(StockNo,2) IN('JR','VS','JB','JG') ORDER BY $number DESC LIMIT 1; *EXPLAIN Result* id select_type table type possible_keys key key_len ref rows Extra 1 SIMPLE inv index (NULL) PRIMARY 66 (NULL) 2496 Using where; Using index; Using filesort Simplified Table Structure: CREATE TABLE `tableinventory` ( `StockNo` varchar(64) NOT NULL DEFAULT '', `ItemDesc` varchar(96) NOT NULL DEFAULT '', PRIMARY KEY (`StockNo`) ) ENGINE=PBXT DEFAULT CHARSET=latin1; All data is using a length of 7 even though it is defined as varchar(64).

2 5

[Maria-discuss] New KB question: Embedded engine?
by Daniel Bartholomew 01 Mar '12

01 Mar '12

A new question has been posted in the Knowledgebase: https://kb.askmonty.org/en/embedded-engine +++++++++++++++++++++++++++++++++++ Hi all, Is there an embedded version of MariaDB? If the answer is yes, then is it possible to connect to it using JDBC (this works for the Firebird embedded server)? TIA and rgs, Paul... +++++++++++++++++++++++++++++++++++ Thanks. -- Daniel Bartholomew MariaDB - http://mariadb.org Monty Program - http://montyprogram.com AskMonty Knowledgebase - http://kb.askmonty.org

1 0

[Maria-discuss] MariaDB 5.3.5 now available!
by Daniel Bartholomew 29 Feb '12

29 Feb '12

The MariaDB project is pleased to announce the immediate availability of MariaDB 5.3.5! MariaDB 5.3.5 is the first stable (GA) release in the 5.3 series. --- MariaDB 5.3.5 Release Notes, Changelog, Downloads ----------------- The release notes are available at: http://kb.askmonty.org/en/mariadb-535-release-notes A changelog is available at: http://kb.askmonty.org/en/mariadb-535-changelog Sources, binaries and packages can be downloaded from: http://downloads.askmonty.org/mariadb/5.3.5/ Debian and Ubuntu packages are available from our mirrored apt repositories. A sources.list generator can be found at: http://downloads.askmonty.org/mariadb/repositories/ --- About MariaDB 5.3 ------------------------------------------------- The MariaDB 5.3 series introduces many new features, includes MariaDB 5.2, and is based on MariaDB 5.1 & MySQL 5.1. Some highlights of new features in MariaDB 5.3 include: - subquery optimizations that finally make subqueries usable - many optimizer changes, including Classic Hash Join, Batched Key Access, a new implementation of Multi-Range-Read optimizations as well as Index Condition Pushdown - NoSQL-style interfaces via the HandlerSocket plugin as well as dynamic columns - group commit in XtraDB when the binary log is enabled - Microsoft Windows performance improvements These are just some of the highlights, and for a more complete list of changes, please read the What is MariaDB 5.3 page: http://kb.askmonty.org/en/what-is-mariadb-53 --- SkySQL and MariaDB: Solutions Day --------------------------------- We'll be co-hosting the the "SkySQL & MariaDB: Solutions Day for the MySQL® Database" one day event on 13 April, 2012, at the Hyatt Regency Santa Clara. During this event, attendees will receive free, hands-on training and consulting on MariaDB and MySQL® database solutions from the experts at SkySQL, MariaDB, Continuent, ScaleDB, Severalnines, Sphinx, and Webyog, among others. SkySQL and MariaDB will bring together industry visionaries, including Michael (Monty) Widenius and David Axmark, the original authors of the MySQL database, to share their insights on current and future trends pertaining to the world's most popular open source database. To learn more about this free event, visit http://www.skysql.com/events/mysql-solutions-day The schedule for the event is here: http://www.skysql.com/events/mysql-solutions-day/schedule Attendees are also invited to participate in Drizzle Day– a parallel event co-hosted by SkySQL, Percona, and the Drizzle Development Team, featuring tutorials on the Drizzle database. --- User Feedback plugin ---------------------------------------------- MariaDB includes a User Feedback plugin. This plugin is disabled by default. If enabled, it submits basic, completely anonymous MariaDB usage information. This information is used by the developers to track trends in MariaDB usage to better guide development efforts. If you would like to help make MariaDB better, please add --plugin-load=feedback.so to your my.cnf file! On Windows, add "feedback=ON" to your my.ini file, or click the checkbox during the installation of the MSI package. See http://kb.askmonty.org/en/user-feedback-plugin for more information. --- MariaDB Crash Course book ----------------------------------------- We would also like to mention the book "MariaDB Crash Course", by Ben Forta. This book - for beginner to intermediate level users - will get you up and running with MariaDB, even if you've never used a database before. More information is available at: http://forta.com/books/0321799941/ --- Quality ----------------------------------------------------------- The project always strives for quality, but in reality, nothing is perfect. Please take time to report any issues you encounter at: https://bugs.launchpad.net/maria We hope you enjoy MariaDB! -- Daniel Bartholomew MariaDB - http://mariadb.org Monty Program - http://montyprogram.com AskMonty Knowledgebase - http://kb.askmonty.org

1 0

[Maria-discuss] MariaDB 5.5.20-alpha now available
by Daniel Bartholomew 27 Feb '12

27 Feb '12

The MariaDB project is pleased to announce the immediate availability of MariaDB 5.5.20-alpha. MariaDB 5.5.20 is the first Alpha release in the 5.5 series. We hope to follow it up soon with a beta 5.5 release. MariaDB 5.5.20-alpha is a merge of MariaDB 5.3 and MySQL 5.5 with some limited additional bug fixes. This is the first 5.5-based release, and we are releasing it now, intentionally without any extra features, and with it missing some planned features, to get it into the hands of any who might want to test it. Extra features planned for MariaDB 5.5 will be pushed into subsequent releases. **Do not use alpha releases on production systems.** == MariaDB 5.5.20-alpha Release Notes, Changelog, Downloads =========== The release notes for MariaDB 5.5.20-alpha are available at: http://kb.askmonty.org/en/mariadb-5520-release-notes A changelog for this release is available at: http://kb.askmonty.org/en/mariadb-5520-changelog Sources, binaries and packages can be downloaded from: http://downloads.askmonty.org/mariadb/5.5.20/ Debian and Ubuntu packages are available from our mirrored apt repositories. A sources.list generator can be found at: http://downloads.askmonty.org/mariadb/repositories/ == About MariaDB 5.5 ================================================== The MariaDB 5.5 series is the combination of MariaDB 5.3 and MySQL 5.5. Please read the "What is MariaDB 5.5" page for details: http://kb.askmonty.org/en/what-is-mariadb-55 == SkySQL and MariaDB: Solutions Day ================================== We'll be co-hosting the the "SkySQL & MariaDB: Solutions Day for the MySQL® Database" one day event on 13 April, 2012, at the Hyatt Regency Santa Clara. During this event, attendees will receive free, hands-on training and consulting on MariaDB and MySQL® database solutions from the experts at SkySQL, MariaDB, Continuent, ScaleDB, Severalnines, Sphinx, and Webyog, among others. SkySQL and MariaDB will bring together industry visionaries, including Michael (Monty) Widenius and David Axmark, the original authors of the MySQL database, to share their insights on current and future trends pertaining to the world's most popular open source database. To learn more about this free event, visit http://www.skysql.com/events/mysql-solutions-day The schedule for the event is here: http://www.skysql.com/events/mysql-solutions-day/schedule Attendees are also invited to participate in Drizzle Day– a parallel event co-hosted by SkySQL, Percona, and the Drizzle Development Team, featuring tutorials on the Drizzle database. == User Feedback plugin =============================================== MariaDB includes a User Feedback plugin. This plugin is disabled by default. If enabled, it submits basic, completely anonymous MariaDB usage information. This information is used by the developers to track trends in MariaDB usage to better guide development efforts. If you would like to help make MariaDB better, please add --plugin-load=feedback.so to your my.cnf file! On Windows, add "feedback=ON" to your my.ini file, or click the checkbox during the installation of the MSI package. See http://kb.askmonty.org/en/user-feedback-plugin for more information. == MariaDB Crash Course book ========================================== We would also like to mention the book "MariaDB Crash Course", by Ben Forta. This book - for beginner to intermediate level users - will get you up and running with MariaDB, even if you've never used a database before. More information is available at: http://forta.com/books/0321799941/ == Quality ============================================================ The project always strives for quality, but in reality, nothing is perfect. Please take time to report any issues you encounter at: https://bugs.launchpad.net/maria We hope you enjoy MariaDB! -- Daniel Bartholomew MariaDB - http://mariadb.org Monty Program - http://montyprogram.com AskMonty Knowledgebase - http://kb.askmonty.org

1 0

Re: [Maria-discuss] MySQL's future in Debian and Ubuntu
by Alex Esterkin 22 Feb '12

22 Feb '12

As an end user, I would most strongly dislike this. You clearly don't understand how corporate users think and operate, how they work with open source technologies, and how they plan and evolve their technical roadmaps. Last year Ubuntu inflicted enough damage on itself by messing up with UI and display management. Replacing OpenOffice with LibreOffice was not a success story either. A year ago I had plans to migrate my remaining CentOS and Debian servers and test environments to Ubuntu and I recommended using Ubuntu for a couple of server appliance products we had in the works. These plans were revisited and revised in the fall, based on revised Linux distro release and roadmap assessment. As far as MySQL is concerned, I don't care at this point what your Ubuntu server distro plans are, as I have already migrated away from Ubuntu. However, if the discussion about replacing MySQL also spreads into the Fedora Project and CentOS communities, that would give me a very good reason for migrating/porting MySQL apps and products to Postgres. Regards, Alex Esterkin, Former Chief Architect, Infobright On Tue, Feb 7, 2012 at 04:37, Clint Byrum <clint(a)ubuntu.com> wrote: > Many of us in the Free and Open Source software community have seen a > trend regarding Oracle's stewardship of Open source software that it > inherited when it purchased Sun. In particular there were two fairly > large public project blow ups that resulted in OpenOffice splintering, > and the Hudson community (almost?) completely moving to an independent > fork called Jenkins. > > It has been brought to my attention that MySQL may have gone this way > as well, but in a much more subtle way. This started about a year ago, > and has only recently really become obvious. > > A few notable fellows from the MySQL ecosystem have commented: > > Mark Callaghan > http://mysqlha.blogspot.com/2011/02/where-have-bugs-gone.html > (read the comments on this one, very informative, and most of the > commenters are extremely important non-Oracle members of the MySQL > community) > > http://mysqlha.blogspot.com/2011/11/great-work-bug-12704861-was-fixed.html > > Stewart Smith: > http://www.mysqlperformanceblog.com/2011/11/20/bug12704861/ > > And the CVE's are extremely vague: > > http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2012-0119 > > "Unspecified vulnerability in the MySQL Server component in Oracle MySQL > 5.1.x and 5.5.x allows remote authenticated users to affect availability > via unknown vectors" > > Links to here: > > http://www.oracle.com/technetwork/topics/security/cpujan2012-366304.html > > Which links to here: > > http://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=1390289.1 > > Which requires an account (which I created). I did try to login but got > some kind of failure.. > > "Failure of server APACHE bridge:". > > The bzr commits for the latest MySQL releases also reference log bug#'s > that are thought to belong to the private oracle support system, not > accessible to non-paying customers. > > This is all very troubling, as in a Linux distribution, we must be able > to support our users and track upstream development. > > So what should we, the Debian and Ubuntu MySQL maintainers and users, > do about this? > > Well there is a Jenkins to MySQL's Hudson, a LibreOffice to their > OpenOffice. > > MariaDB 5.3, in release-candidate now, is 100% backward compatible with > MySQL 5.1. It also includes a few speedups and features that can be found > in MySQL 5.5 and Percona Server. It is developed 100% in the open, on > launchpad.net, including a public bug tracker and up to date bzr trees > of the code. > > http://mariadb.org > https://launchpad.net/maria > > I'm writing to the greater Debian and Ubuntu community to ask for your > thoughts on a proposal to drop MySQL in favor of MariaDB. Its clear to > me that Oracle is not going to do work in the open, and this will become > a huge support burden for Linux distributions. The recent CVE's had to > be hunted down and investigated at great difficulty to several people, > since the KB articles referenced and the internal Oracle bug numbers > referenced were not available. > > This will only get harder as the community bug tracker gets further out > of sync with the private one. > > There is some need to consider acting quickly: > > Ubuntu precise, the next LTS release of Ubuntu will be hitting feature > freeze on Feb. 16. The release, due in April, will be supported with > security updates for 5 years. That may be 5 long years of support if > MySQL continues to obscure things. > > Debian wheezy is still quite far off, but it is critical that this be > done and decided by the time the release freeze begins. > > So, here is a suggested plan, given the facts above: > > * Upload mariadb 5.3 to Debian experimental, with it providing > mysql-server, mysql-client, and libmysqlclient-dev. > > * For Ubuntu users, upload these packages to a PPA for testing > applications for compatibility, and rebuild testing. > > * If testing goes well, replace mysql-5.5 with mariadb in both Debian > unstable and Ubuntu precise. If there are reservations about switching > this late in precise's cycle, ship mysql-5.5 in precise, and push off > Ubuntu's transition until the next cycle. > > Before I strike out on this path alone, which, I understand, may sound > a bit radical, I want to hear what you all think. > > Thank you for your time and consideration. > > -- > Clint Byrum <clint(a)ubuntu.com> > Ubuntu Server Team > Debian MySQL Packaging Team >

7 8

[Maria-discuss] MySQL's future in Debian and Ubuntu
by Clint Byrum 17 Feb '12

17 Feb '12

Many of us in the Free and Open Source software community have seen a trend regarding Oracle's stewardship of Open source software that it inherited when it purchased Sun. In particular there were two fairly large public project blow ups that resulted in OpenOffice splintering, and the Hudson community (almost?) completely moving to an independent fork called Jenkins. It has been brought to my attention that MySQL may have gone this way as well, but in a much more subtle way. This started about a year ago, and has only recently really become obvious. A few notable fellows from the MySQL ecosystem have commented: Mark Callaghan http://mysqlha.blogspot.com/2011/02/where-have-bugs-gone.html (read the comments on this one, very informative, and most of the commenters are extremely important non-Oracle members of the MySQL community) http://mysqlha.blogspot.com/2011/11/great-work-bug-12704861-was-fixed.html Stewart Smith: http://www.mysqlperformanceblog.com/2011/11/20/bug12704861/ And the CVE's are extremely vague: http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2012-0119 "Unspecified vulnerability in the MySQL Server component in Oracle MySQL 5.1.x and 5.5.x allows remote authenticated users to affect availability via unknown vectors" Links to here: http://www.oracle.com/technetwork/topics/security/cpujan2012-366304.html Which links to here: http://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=1390289.1 Which requires an account (which I created). I did try to login but got some kind of failure.. "Failure of server APACHE bridge:". The bzr commits for the latest MySQL releases also reference log bug#'s that are thought to belong to the private oracle support system, not accessible to non-paying customers. This is all very troubling, as in a Linux distribution, we must be able to support our users and track upstream development. So what should we, the Debian and Ubuntu MySQL maintainers and users, do about this? Well there is a Jenkins to MySQL's Hudson, a LibreOffice to their OpenOffice. MariaDB 5.3, in release-candidate now, is 100% backward compatible with MySQL 5.1. It also includes a few speedups and features that can be found in MySQL 5.5 and Percona Server. It is developed 100% in the open, on launchpad.net, including a public bug tracker and up to date bzr trees of the code. http://mariadb.org https://launchpad.net/maria I'm writing to the greater Debian and Ubuntu community to ask for your thoughts on a proposal to drop MySQL in favor of MariaDB. Its clear to me that Oracle is not going to do work in the open, and this will become a huge support burden for Linux distributions. The recent CVE's had to be hunted down and investigated at great difficulty to several people, since the KB articles referenced and the internal Oracle bug numbers referenced were not available. This will only get harder as the community bug tracker gets further out of sync with the private one. There is some need to consider acting quickly: Ubuntu precise, the next LTS release of Ubuntu will be hitting feature freeze on Feb. 16. The release, due in April, will be supported with security updates for 5 years. That may be 5 long years of support if MySQL continues to obscure things. Debian wheezy is still quite far off, but it is critical that this be done and decided by the time the release freeze begins. So, here is a suggested plan, given the facts above: * Upload mariadb 5.3 to Debian experimental, with it providing mysql-server, mysql-client, and libmysqlclient-dev. * For Ubuntu users, upload these packages to a PPA for testing applications for compatibility, and rebuild testing. * If testing goes well, replace mysql-5.5 with mariadb in both Debian unstable and Ubuntu precise. If there are reservations about switching this late in precise's cycle, ship mysql-5.5 in precise, and push off Ubuntu's transition until the next cycle. Before I strike out on this path alone, which, I understand, may sound a bit radical, I want to hear what you all think. Thank you for your time and consideration.

10 16

Re: [Maria-discuss] MySQL's future in Debian and Ubuntu
by Pandu Poluan 17 Feb '12

17 Feb '12

On Feb 13, 2012 2:21 PM, "Eddie Bachle" <enb10(a)albion.edu> wrote: > > In general, I am generally an simply an observer on most of these mailing lists, however my concerns with a switch are far less technical and far more practical. I work currently for a college in Michigan which utilizes almost solely Windows servers simply because it is what the IT staff here knows. As a student here, I was brought in to assist with the web server administration, and as time went by because I have a degree of Linux knowledge, I was given permission to put together a Ubuntu LAMP server to serve a couple of interested parties on campus who wanted simply to demo several small scale web apps that were Linux exclusive. This server would serve as an exception to the general rule of our server architecture. However as time has went by and my knowledge looks more like it will be a fixture here after graduation, along with the simple instability of PHP and Apache on the Windows platform, my boss is giving far more consideration to moving to Linux. > > As Linux gains more public recognition, more and more Windows-only organizations will consider using it as an alternative, especially for their web servers. This is especially true because of the fact that each of the necessarily main components of a web server exist in Linux in the same form as the do on Windows and often run much better. Then, the only piece one would need to learn would be the new operating system, not the database, HTTP server, or PHP scripting language software. However, this is going to be a more difficult proposition if the aforementioned advantage is somewhat eliminated. Were I to have to tell my boss that we could switch to Ubuntu but it would mean that would need to use a "MySQL compatible" database if we want to use the native database (which we likely would because it's tested to be stable and it is supported by the developers), then she would be much more hesitant. > > There simply is a much greater sense of trepidation for those who are not significantly Linux savvy if there exists a possibility that they would have to make something work in an unfamiliar environment, especially if it were to happen unexpectedly. If we ported our www website server over to Ubuntu and then 6 months down the road we were to upgrade our Joomla version and there became an issue with MariaDB because it lacks some MySQL feature that it needs, or even that Joomla would fail to recognize Maria as being equivalent to MySQL at some point, then that would be a huge detraction against switching. > > Unless assurances that any software that asks for MySQL will recognize and accept MariaDB equivalents, and that this should always be the case, and that it will retain the stability and recognized benefits of MySQL, I would encourage extreme caution in encouraging a switch. Linux is beginning to grow into areas it previously didn't reach and bringing a far superior web server experience as well as simply a better operating system experience for many and I would not like to see that growth compromised. I would like to say we would still switch, or still heavily consider it for the grains that could be made by using Ubuntu, however realistically, the lack of native MySQL in any OS would be a huge mark against it. Also that being said, if the technical concerns are answered adequately for a vast majority of applications and hardware/OS setups, then I would be totally behind switching to a more open source friendly and compatible database software as there would be little love lost between me and MySQL. > > I hope this perspective helps a bit in considering this decision, > Do remember that there's an alternative to MySQL/MariaDB: PostgreSQL. I'm actually busy migrating the Windows infrastructure, and my target database is PostgreSQL. Note: I am *not* recommending that Ubuntu replaced its default database from MySQL to PostgreSQL; If a company already deployed a MySQL-based app, then it should migrate to MariaDB, if only to prevent being trapped by Oracle into migrating into Oracle. But for those still exploring a migration to Linux, I won't hesitate to push them toward PostgreSQL instead. There are clear benefits of PostgreSQL over MySQL for the enterprise, and vv. Rgds,

9 20

[Maria-discuss] MariaDB 5.3.4-rc now available
by Daniel Bartholomew 16 Feb '12

16 Feb '12

The MariaDB project would like to announce the availability of MariaDB 5.3.4-rc, the latest addition to our growing lineup of supported software. MariaDB 5.3.4-rc is the second Release Candidate release in the 5.3 series. We hope to follow it up soon with a stable (GA) 5.3 release. == MariaDB 5.3.4-rc Release Notes, Changelog, Downloads =============== The release notes for MariaDB 5.3.4-rc are available from: http://kb.askmonty.org/en/mariadb-534-release-notes A complete changelog for this beta is available from: http://kb.askmonty.org/en/mariadb-534-changelog Sources, binaries and packages can be downloaded from: http://downloads.askmonty.org/mariadb/5.3.4/ Debian and Ubuntu packages are available from our mirrored apt repositories. A sources.list generator can be found at: http://downloads.askmonty.org/mariadb/repositories/ == About MariaDB 5.3 ================================================== The MariaDB 5.3 series introduces many new features, includes MariaDB 5.2, and is based on MariaDB 5.1 & MySQL 5.1. Some highlights of new features in MariaDB 5.3 include: - subquery optimizations that finally make subqueries usable - many optimizer changes, including Classic Hash Join, Batched Key Access, a new implementation of Multi-Range-Read optimizations as well as Index Condition Pushdown - NoSQL-style interfaces via the HandlerSocket plugin as well as dynamic columns - group commit in XtraDB when the binary log is enabled - Microsoft Windows performance improvements These are just some of the highlights, and for a more complete list of changes, please read the What is MariaDB 5.3 page: http://kb.askmonty.org/en/what-is-mariadb-53 == User Feedback plugin =============================================== MariaDB 5.3 includes a User Feedback plugin. This plugin is disabled by default. If enabled, it submits basic, completely anonymous MariaDB usage information. This information is used by the developers to track trends in MariaDB usage to better guide development efforts. If you would like to help make MariaDB better, please add --plugin-load=feedback.so to your my.cnf file! On Windows, add "feedback=ON" to your my.ini file, or click the checkbox during the installation of the MSI package. See http://kb.askmonty.org/en/user-feedback-plugin for more information. == MariaDB Crash Course book ========================================== We would also like to mention the book "MariaDB Crash Course", by Ben Forta. This book -- for beginner to intermediate level users -- will get you up and running with MariaDB, even if you've never used a database before. More information is available at: http://forta.com/books/0321799941/ == Quality ============================================================ The project always strives for quality, but in reality, nothing is perfect. Please take time to report any issues you encounter at: https://bugs.launchpad.net/maria We hope you enjoy MariaDB 5.3.4-rc! -- Daniel Bartholomew MariaDB - http://mariadb.org Monty Program - http://montyprogram.com AskMonty Knowledgebase - http://kb.askmonty.org

1 0

Re: [Maria-discuss] MySQL's future in Debian and Ubuntu
by Robbie Williamson 16 Feb '12

16 Feb '12

On 02/13/2012 01:20 AM, Eddie Bachle wrote: > I would like to say we would still switch, or still heavily consider it > for the grains that could be made by using Ubuntu, however > realistically, the lack of native MySQL in any OS would be a huge mark > against it. FTR, we would not *drop* MySQL support. Worst case scenario, we'd place them in partner, much like we did with sun-java. The change would be that our default/recommended DB would be MariaDB. > Also that being said, if the technical concerns are > answered adequately for a vast majority of applications and hardware/OS > setups, then I would be totally behind switching to a more open source > friendly and compatible database software as there would be little love > lost between me and MySQL. One thing to note, the primary motivator for this proposal isn't about moving to a more "open source friendly" application. We have genuine security concerns/issues with how MySQL handles and publishes their security updates. We can't simply update supported prior Ubuntu releases to newer MySQL versions, so we have to backport patches. Their lack of information and access to the bugs addressed makes it *very* time consuming and difficult for our security and SRU teams to do this. If we can resolve these issues, then MySQL's future in main looks much brighter. -Robbie -- Robbie Williamson <robbie(a)ubuntu.com> robbiew[irc.freenode.net] "Don't make me angry...you wouldn't like me when I'm angry." -Bruce Banner

3 3

Re: [Maria-discuss] [debian-mysql] MySQL's future in Debian and Ubuntu
by Colin Charles 16 Feb '12

16 Feb '12

Hi! On 13 Feb 2012, at 15:20, Eddie Bachle wrote: > As Linux gains more public recognition, more and more Windows-only organizations will consider using it as an alternative, especially for their web servers. This is especially true because of the fact that each of the necessarily main components of a web server exist in Linux in the same form as the do on Windows and often run much better. Then, the only piece one would need to learn would be the new operating system, not the database, HTTP server, or PHP scripting language software. However, this is going to be a more difficult proposition if the aforementioned advantage is somewhat eliminated. Were I to have to tell my boss that we could switch to Ubuntu but it would mean that would need to use a "MySQL compatible" database if we want to use the native database (which we likely would because it's tested to be stable and it is supported by the developers), then she would be much more hesitant. I reckon MySQL will always be available -- this discussion is about a supported release, especially from a security POV > There simply is a much greater sense of trepidation for those who are not significantly Linux savvy if there exists a possibility that they would have to make something work in an unfamiliar environment, especially if it were to happen unexpectedly. If we ported our www website server over to Ubuntu and then 6 months down the road we were to upgrade our Joomla version and there became an issue with MariaDB because it lacks some MySQL feature that it needs, or even that Joomla would fail to recognize Maria as being equivalent to MySQL at some point, then that would be a huge detraction against switching. More and more software out there also state it works with MariaDB. While your particular example of Joomla! doesn't, another popular CMS like Drupal has had MariaDB on its list for quite some time. (see: http://drupal.org/requirements -- "Recommended: MySQL (or an equivalent such as MariaDB)") > Unless assurances that any software that asks for MySQL will recognize and accept MariaDB equivalents, and that this should always be the case, and that it will retain the stability and recognized benefits of MySQL, I would encourage extreme caution in encouraging a switch. Linux is beginning to grow into areas it previously didn't reach and bringing a far I can totally understand your concern and assure you that MariaDB developers ensure compatibility and treat it as a very high requirement. Backwards compatible is one of our goals and we've never broken that. Extensive testing and QA helps too naturally cheers, -c -- Colin Charles, http://bytebot.net/blog/ | twitter: @bytebot | skype: colincharles MariaDB: Community developed. Feature enhanced. Backward compatible. Download it at: http://www.mariadb.org/ Open MariaDB/MySQL documentation at the Knowledgebase: http://kb.askmonty.org/

1 0

[Maria-discuss] New KB Question: millisecond part is trimmed away when saving Java Date obj by hibernate
by Daniel Bartholomew 14 Feb '12

14 Feb '12

A new question has been posted in the Knowledgebase: http://kb.askmonty.org/en/millisecond-part-is-trimmed-away-when-saving-java… ---------------------------------------- Hi, I recently upgraded my MySQL DB to MariaDB for millisecond support. I can see the millisecond part in my upgraded database. And I tested the millisecond support by inserting a row to a table of my db. It functions well. But when I use hibernate to save a java.util.Date obj into database, millisecond part is trimmed and in MariaDB date obj is saved as: 2012-02-13 18:40:55.000. Do I need to set up something to activate millisecond support? Or I need to config hibernate for millisecond support? Thanks a lot! ---------------------------------------- Thanks. -- Daniel Bartholomew MariaDB - http://mariadb.org Monty Program - http://montyprogram.com AskMonty Knowledgebase - http://kb.askmonty.org

1 0

Re: [Maria-discuss] MySQL's future in Debian and Ubuntu
by Marc Deslauriers 13 Feb '12

13 Feb '12

On Mon, 2012-02-13 at 02:20 -0500, Eddie Bachle wrote: > In general, I am generally an simply an observer on most of these > mailing lists, however my concerns with a switch are far less > technical and far more practical. I work currently for a college in > Michigan which utilizes almost solely Windows servers simply because > it is what the IT staff here knows. As a student here, I was brought > in to assist with the web server administration, and as time went by > because I have a degree of Linux knowledge, I was given permission to > put together a Ubuntu LAMP server to serve a couple of interested > parties on campus who wanted simply to demo several small scale web > apps that were Linux exclusive. This server would serve as an > exception to the general rule of our server architecture. However as > time has went by and my knowledge looks more like it will be a fixture > here after graduation, along with the simple instability of PHP and > Apache on the Windows platform, my boss is giving far more > consideration to moving to Linux. > > > As Linux gains more public recognition, more and more Windows-only > organizations will consider using it as an alternative, especially for > their web servers. This is especially true because of the fact that > each of the necessarily main components of a web server exist in Linux > in the same form as the do on Windows and often run much better. > Then, the only piece one would need to learn would be the new > operating system, not the database, HTTP server, or PHP scripting > language software. However, this is going to be a more difficult > proposition if the aforementioned advantage is somewhat eliminated. > Were I to have to tell my boss that we could switch to Ubuntu but it > would mean that would need to use a "MySQL compatible" database if we > want to use the native database (which we likely would because it's > tested to be stable and it is supported by the developers), then she > would be much more hesitant. If you prefer MySQL, you'll still be able to manually install it MySQL on Ubuntu and Debian, much like you manually install it on Windows. > > > There simply is a much greater sense of trepidation for those who are > not significantly Linux savvy if there exists a possibility that they > would have to make something work in an unfamiliar environment, > especially if it were to happen unexpectedly. If we ported our www > website server over to Ubuntu and then 6 months down the road we were > to upgrade our Joomla version and there became an issue with MariaDB > because it lacks some MySQL feature that it needs, or even that Joomla > would fail to recognize Maria as being equivalent to MySQL at some > point, then that would be a huge detraction against switching. I predict it will be the opposite. Once distros and people start switching to MariaDB, other projects will be testing on MariaDB by default, and compatibility with MySQL will then become problematic. Marc.

1 0

[Maria-discuss] New KB Question: ODBC
by Daniel Bartholomew 08 Feb '12

08 Feb '12

A new question has been posted to the Knowledgebase: http://kb.askmonty.org/en/mariadb-odbc ==================== Is there an ODBC driver for use with MariaDB that is compatible with the driver provided with MySQL? ==================== Thanks. -- Daniel Bartholomew MariaDB - http://mariadb.org Monty Program - http://montyprogram.com AskMonty Knowledgebase - http://kb.askmonty.org

1 0

[Maria-discuss] New KB Question: Locking SQL_MODE against client changes
by Daniel Bartholomew 05 Feb '12

05 Feb '12

A new question has been posted in the Knowledgebase: http://kb.askmonty.org/en/locking-sql_mode-against-client-changes ==================== Is there any way for locking out sql_mode against client-side changes other than MySQL Proxy (which does not allow for SSL connections)? Perhaps some MariaDB-specific setting? ==================== Thanks. -- Daniel Bartholomew MariaDB - http://mariadb.org Monty Program - http://montyprogram.com AskMonty Knowledgebase - http://kb.askmonty.org

1 0

[Maria-discuss] auth_pam does not compile on OSX
by Terin Stock 20 Jan '12

20 Jan '12

The 5.2.10 version of MariaDB is not compiling for me (using homebrew) on OSX. The error and other information, is as follows. I've resolved the issue for now by passing in --without-plugin-auth_pam to configure. libtool: compile: /usr/bin/llvm-gcc -DHAVE_CONFIG_H -I. -I. -I../../include -I../../include -I/usr/local/Cellar/readline/6.2.1/include -DMYSQL_DYNAMIC_PLUGIN -O3 -w -pipe -march=core2 -msse4 -D_P1003_1B_VISIBLE -DSIGNAL_WITH_VIO_CLOSE -DSIGNALS_DONT_BREAK_READ -DIGNORE_SIGHUP_SIGQUIT -DDONT_DECLARE_CXA_PURE_VIRTUAL -c auth_pam.c -fno-common -DPIC -o .libs/auth_pam_la-auth_pam.o auth_pam.c:107: error: ‘pam_info’ redeclared as different kind of symbol /usr/include/security/openpam.h:104: error: previous declaration of ‘pam_info’ was here make[2]: *** [auth_pam_la-auth_pam.lo] Error 1 $ ./configure --without-docs --without-debug --disable-dependency-tracking --prefix=/usr/local/Cellar/mariadb/5.2.10 --localstatedir=/usr/local/var/mysql --sysconfdir=/usr/local/etc/ --with-extra-charsets=complex --without-readline --enable-assembler --enable-thread-safe-client --with-big-tables --without-plugin-innodb_plugin --with-mysqld-ldflags=-static --with-client-ldflags=-static --with-plugins=max-no-ndb --with-embedded-server --with-libevent C: /usr/bin/llvm-gcc => /usr/llvm-gcc-4.2/bin/llvm-gcc-4.2 CXX: /usr/bin/llvm-g++ => /usr/llvm-gcc-4.2/bin/llvm-g++-4.2 LD: /usr/bin/llvm-gcc => /usr/llvm-gcc-4.2/bin/llvm-gcc-4.2 CFLAGS: -O3 -w -pipe -march=core2 -msse4 CXXFLAGS: -O3 -w -pipe -march=core2 -msse4 -O3 -fno-omit-frame-pointer -felide-constructors CPPFLAGS: -I/usr/local/Cellar/readline/6.2.1/include LDFLAGS: -L/usr/local/Cellar/readline/6.2.1/lib MAKEFLAGS: -j4 -- #Terin Stock

4 5

[Maria-discuss] pam plugin does't compile on FreeBSD
by geoffroy desvernay 09 Jan '12

09 Jan '12

Hi everyone, I'm mariadb's port maintainer for FreeBSD, and I'd like to get it compile before pushing the 5.2.10 update... Seems to be the same problem than under OSX: (with openpam) https://lists.launchpad.net/maria-discuss/msg00506.html Under FreeBSD 9.0RC3 (and 8.2) amd64: libtool: compile: cc -DHAVE_CONFIG_H -I. -I. -I../../include -I../../include -I/usr/local/include -DMYSQL_DYNAMIC_PLUGIN -O2 -pipe -fno-strict-aliasing -MT auth_pam_la-auth_pam.lo -MD -MP -MF .deps/auth_pam_la-auth_pam.Tpo -c auth_pam.c -fPIC -DPIC -o .libs/auth_pam_la-auth_pam.o auth_pam.c:107: error: 'pam_info' redeclared as different kind of symbol /usr/include/security/openpam.h:102: error: previous declaration of 'pam_info' was here *** Error code 1 1 error *** Error code 1 1 error *** Error code 1 1 error *** Error code 1 Sergei Golubchik wrote 'Fixed' in the referenced mail, but I don't know if it's fixed by removing pam support for OSX or ? (did not find any difference in bzr branch 5.2) Should I disable pam support for FreeBSD or is there any patch I could include in the port for 5.2.10 ? Thanks, -- *Geoffroy Desvernay* C.R.I - Administration systèmes et réseaux Ecole Centrale de Marseille

2 2

[Maria-discuss] MariaDB 5.3.3-rc now available
by Daniel Bartholomew 21 Dec '11

21 Dec '11

The MariaDB project would like to announce the availability of MariaDB 5.3.3-rc, the latest addition to our growing lineup of supported software. MariaDB 5.3.3-rc is the first Release Candidate release in the 5.3 series. We hope to follow it up soon with a stable (GA) 5.3 release. == MariaDB 5.3.3-rc Release Notes, Changelog, Downloads =============== The release notes for MariaDB 5.3.3-rc are available from: http://kb.askmonty.org/en/mariadb-533-release-notes A complete changelog for this beta is available from: http://kb.askmonty.org/en/mariadb-533-changelog Sources, binaries and packages can be downloaded from: http://downloads.askmonty.org/mariadb/5.3.3/ Debian and Ubuntu packages (now including Ubuntu 11.10 "Oneiric") are available from our mirrored apt repositories. A sources.list generator can be found at: http://downloads.askmonty.org/mariadb/repositories/ == About MariaDB 5.3.3-rc ============================================= In MariaDB 5.3.3-rc there are a couple of changes compared to previous 5.3 releases: === Performance: Several optimizer features introduced in MariaDB 5.3 have been thoroughly tested, and switched on by default in 5.3.3. These include: * Subquery materialization (materialization=on) http://kb.askmonty.org/en/non-semi-join-subquery-optimizations * Semi-join optimizations (semijoin=on,firstmatch=on,loosescan=on) http://kb.askmonty.org/en/semi-join-subquery-optimizations * Derived table optimization (derived_merge=on,derived_with_keys=on) (Documentation is being worked on) * Index Condition Pushdown (index_condition_pushdown=on) http://kb.askmonty.org/en/index-condition-pushdown * Nested loop join will use its Block-based variant more aggressively http://kb.askmonty.org/en/block-based-join-algorithms * Block-based join for OUTER JOINs (outer_join_with_cache=on) * Block-based join for semi-joins (semijoin_with_cache=on) * Linked join buffers (more aggressive buffering of multi-way joins) (@@join_cache_level==2) Also, DISTINCT and GROUP BY clauses are now removed from subqueries when possible. This allows for more efficient query plans. (backported from MySQL 5.6) === Usability: EXPLAIN output has been improved in MariaDB 5.3.3 to be easier to understand: * The select_type column now shows MATERIALIZED for subqueries that are executed with Materialization (it used to show SUBQUERY, which made it hard to distinguish materialized subqueries from other kinds subqueries). * For a Duplicate Elimination strategy, Start temporary is now shown at the first table from the subquery. See also: http://kb.askmonty.org/en/explain === GIS Operations: GIS precise operations were added in MariaDB 5.3.3 (Documentation for this is still being worked on). == About MariaDB 5.3 ================================================== The MariaDB 5.3 series introduces many new features, includes MariaDB 5.2, and is based on MariaDB 5.1 & MySQL 5.1. Some highlights of new features in MariaDB 5.3 include: - subquery optimizations that finally make subqueries usable - many optimizer changes, including Classic Hash Join, Batched Key Access, a new implementation of Multi-Range-Read optimizations as well as Index Condition Pushdown - NoSQL-style interfaces via the HandlerSocket plugin as well as dynamic columns - group commit in XtraDB when the binary log is enabled - Microsoft Windows performance improvements These are just some of the highlights, and for a more complete list of changes, please read the What is MariaDB 5.3 page: http://kb.askmonty.org/en/what-is-mariadb-53 == User Feedback plugin =============================================== MariaDB 5.3 includes a User Feedback plugin. This plugin is disabled by default. If enabled, it submits anonymous basic MariaDB usage information. This information will be used by the developers to track trends in MariaDB usage to better guide development efforts. If you would like to help make MariaDB better, please add --plugin-load=feedback.so to your my.cnf file! On Windows, add "feedback=ON" to your my.ini file, or click the checkbox during the installation of the MSI package. See http://kb.askmonty.org/en/user-feedback-plugin for more information. == MariaDB Crash Course book ========================================== We would also like to mention the book "MariaDB Crash Course", by Ben Forta. This book -- for beginner to intermediate level users -- will get you up and running with MariaDB, even if you've never used a database before. More information is available at: http://forta.com/books/0321799941/ == Quality ============================================================ The project always strives for quality, but in reality, nothing is perfect. Please take some time to report any issues you encounter at: https://bugs.launchpad.net/maria We hope you enjoy MariaDB 5.3.3-rc! -- Daniel Bartholomew MariaDB - http://mariadb.org Monty Program - http://montyprogram.com AskMonty Knowledgebase - http://kb.askmonty.org

1 0

[Maria-discuss] MariaDB fails to compile with boost
by Terin Stock 21 Dec '11

21 Dec '11

A downstream user is reporting that 5.2.8 (and, after fixing the already reported issue with auth_pam, 5.2.10) does not install with boost 1.48.0 installed. Removing boost from the link path allows MariaDB to compile successfully. I've attached their output, in hopes it will arrive to the list safely. :) -- #Terin Stock

2 1

[Maria-discuss] MariaDB 5.2.10 and 5.1.60 Released
by Daniel Bartholomew 06 Dec '11

06 Dec '11

This email is longer than usual, but that is because we are announcing today the availability of both MariaDB 5.2.10 and 5.1.60, the latest additions to our growing lineup of supported software. MariaDB 5.2.10 and 5.1.60 are primarily bug-fix updates to the previous 5.2.9 and 5.1.55 releases, respectively. == About MariaDB 5.2 MariaDB 5.2 contains features that didn't have time to go into MariaDB 5.1. For all practical purposes it's a drop in replacement for MariaDB 5.1 (and thus MySQL 5.1). The new features in 5.2 are quite isolated and as most have been in use by members in the MySQL community for a long time. Current versions of MariaDB 5.2 are stable. This is equivalent to a MySQL GA release. For a list of the various changes in the MariaDB 5.2 series, please see: * http://kb.askmonty.org/en/what-is-mariadb-52 === PAM authentication plugin in MariaDB 5.2.10 One change in MariaDB 5.2.10 which we want to make you aware of is the inclusion of a new open source PAM authentication plugin. See http://kb.askmonty.org/en/pam-authentication-plugin for more information. === Windows Binaries delayed Due to some issues with our Windows build server, the Windows binaries for 5.2.10 have been delayed. They should be released soon. === MariaDB 5.2.10 Release Notes, Changelog, Downloads See the following pages for more information on MariaDB 5.2.10 and to download it: * http://kb.askmonty.org/en/mariadb-5210-release-notes * http://kb.askmonty.org/en/mariadb-5210-changelog * http://downloads.askmonty.org/mariadb/5.2.10/ == About MariaDB 5.1 MariaDB 5.1 is a binary drop in replacement of MySQL 5.1, but with performance like MySQL 5.5 (thanks to XtraDB), fewer bugs, and more features. Thanks to the extended and improved mysql_upgrade program it's also easier to upgrade from MySQL 5.0 to MariaDB 5.1 than to MySQL 5.1. MariaDB 5.1 is based on MySQL 5.1. In particular, MariaDB 5.1.60 is based on MySQL 5.1.60, with many improvements. For a list of the various improvements in the MariaDB 5.1 series, please see: * http://kb.askmonty.org/en/what-is-mariadb-51 === MariaDB 5.1.60 Release Notes, Changelog, Downloads See the following pages for more information on MariaDB 5.1.60 and to download it: * http://kb.askmonty.org/en/mariadb-5160-release-notes * http://kb.askmonty.org/en/mariadb-5160-changelog * http://downloads.askmonty.org/mariadb/5.1.60/ == Debian & Ubuntu Software Repositories Debian and Ubuntu packages are available from our mirrored apt repositories. A sources.list generator can be found at: http://downloads.askmonty.org/mariadb/repositories/ == MariaDB Crash Course book We would also like to mention the book "MariaDB Crash Course", by Ben Forta. This book -- for beginner to intermediate level users -- will get you up and running with MariaDB, even if you've never used a database before. More information is available at: http://forta.com/books/0321799941/ == Reporting issues The project always strives for quality, and being a beta release, we know that not everything may be perfect. Please take some time to report any issues you may encounter at: https://bugs.launchpad.net/maria Enjoy MariaDB 5.2.10 and 5.1.60! -- Daniel Bartholomew MariaDB - http://mariadb.org Monty Program - http://montyprogram.com AskMonty Knowledgebase - http://kb.askmonty.org

1 1

[Maria-discuss] Oneric DEBs are missing?
by Colin Charles 18 Nov '11

18 Nov '11

Hi! http://mirror.aarnet.edu.au/pub/MariaDB/repo/5.3/ubuntu/dists/ The mirror select tool allows you to choose Oneric as a distribution, but it seems to be missing from all the mirrors This probably needs to be fixed -- Colin Charles, http://bytebot.net/blog/ | twitter: @bytebot | skype: colincharles MariaDB: Community developed. Feature enhanced. Backward compatible. Download it at: http://www.mariadb.org/ Open MariaDB/MySQL documentation at the Knowledgebase: http://kb.askmonty.org/

2 1

[Maria-discuss] MariaDB 5.2.7 to 5.2.9 changes new bugs ?
by GEORGE LIU 13 Nov '11

13 Nov '11

First time posting to this list :) I've been using MariaDB since 5.2.4 for everyone of my side projects without issues. But having a problem while playing with Tungsten Replicator based replication. All worked fine with MariaDB 5.2.7 but since upgrading to MariaDB 5.2.9 via rpm on CentOS 6.0 64bit, I have been having problems getting Tungsten Replicator to play nice. Logged a bug report at http://code.google.com/p/tungsten-replicator/issues/detail?id=256 and the Tungsten Replicator folks say it could be possibly a problem with newer MariaDB 5.2.9 release ? Not sure who I should be contacting or whether or not MariaDB folks have already been made aware of this issue ? cheers

2 1

[Maria-discuss] New KB Question: Connecting to a Mariadb database with visual basic express 2010
by Daniel Bartholomew 08 Nov '11

08 Nov '11

A new question has been posted to the AskMonty Knowledgebase: http://kb.askmonty.org/en/connecting-to-a-mariadb-database-with-visual-basi… ----------------------------------------------------------------------- I have tried everything I know how to do -- to connect to an existing mariadb database with visual basic 2010 express. Can anyone give me any ideas on how to get a proper start. I am trying to connect to the localdb server created by heidi, which is a tcp/ip . Microsoft SQL server is installed. ----------------------------------------------------------------------- Thanks. -- Daniel Bartholomew MariaDB - http://mariadb.org Monty Program - http://montyprogram.com AskMonty Knowledgebase - http://kb.askmonty.org

1 0

[Maria-discuss] PlanetMariaDB glitch - resolved
by Arjen Lentz 08 Nov '11

08 Nov '11

Hi all This morning planetmariadb.org would show no feeds and no content. Config and db was all fine, and an agressive clearing of the rss/output cache appears to have resolved the issue. Not sure what caused the problem though, which is annoying. By the way, if you do spot a problem, please shoot me an email - don't just leave a msg on #maria as that can be missed. thanks! Cheers, Arjen. -- Arjen Lentz, Exec.Director @ Open Query (http://openquery.com) Remote expertise & maintenance for MySQL/MariaDB server environments. Follow us at http://openquery.com/blog/ & http://twitter.com/openquery

1 0

[Maria-discuss] New KB Question: CentOS 5.x/6.x mysql-lib conflicts and postfix
by Daniel Bartholomew 01 Nov '11

01 Nov '11

A new question has been posted to the Knowledgebase: http://kb.askmonty.org/en/centos-5x6x-mysql-lib-conflicts-and-postfix ======================================================================= On a fresh CentOS 5.x/6.x 32bit or 64bit install, mysql 5.0.xx is installed. To install MariaDB 5.2.x rpms, mysql-lib needs to be removed for MariaDB-server to be installed. But removing mysql-lib via yum remove, removes postfix. If later you need to install postfix via yum it still requires mysql-lib, but installing mysql-lib installs mysql 5.0.x server again. yum install postfix Loaded plugins: fastestmirror, refresh-packagekit Loading mirror speeds from cached hostfile * base: mirror.averse.net * extras: mirror.averse.net * rpmforge: apt.sw.be * updates: mirror.averse.net Setting up Install Process Resolving Dependencies --> Running transaction check ---> Package postfix.x86_64 2:2.6.6-2.1.el6_0 set to be updated --> Processing Dependency: mysql-libs for package: 2:postfix-2.6.6-2.1.el6_0.x86_64 --> Finished Dependency Resolution Error: Package: 2:postfix-2.6.6-2.1.el6_0.x86_64 (updates) Requires: mysql-libs You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest Anyway to properly resolve this ? with MariaDB 5.2/5.3.x version of mysql-lib ?? ======================================================================= Thanks. -- Daniel Bartholomew MariaDB - http://mariadb.org Monty Program - http://montyprogram.com AskMonty Knowledgebase - http://kb.askmonty.org

1 0

[Maria-discuss] Aria_log file
by Richard Dunn 15 Oct '11

15 Oct '11

How do you read the 'aria_log.0000001' file in the data directory? If I open it with a text editor, It appears to be binary, but mysqlbinlog says that it is not. I'm asking because it looks like 5.3.1 is continually (every two minutes) writing to the log, even with no database activity. This impacts automatic sleep on my Macbook Pro.

3 4

[Maria-discuss] MariaDB 5.3.2-beta now available
by Daniel Bartholomew 14 Oct '11

14 Oct '11

The MariaDB project would like to announce the availability of MariaDB 5.3.2-beta, the latest addition to our growing lineup of supported software. MariaDB 5.3.2-beta is a bug-fix update to the previous 5.3.1 and 5.3.0 betas. == About MariaDB 5.3 The MariaDB 5.3 series introduces many new features, includes MariaDB 5.2, and is based on MySQL 5.1. Some highlights of new features in MariaDB 5.3 include: - subquery optimizations that finally make subqueries usable - many optimizer changes, including Classic Hash Join, Batched Key Access, a new implementation of Multi-Range-Read optimizations as well as Index Condition Pushdown - NoSQL-style interfaces via the HandlerSocket plugin as well as dynamic columns - group commit in XtraDB when the binary log is enabled - Microsoft Windows performance improvements These are just some of the highlights, and for a more complete list of changes, please read the What is MariaDB 5.3 page: http://kb.askmonty.org/en/what-is-mariadb-53 == About MariaDB 5.3.2-beta In the MariaDB 5.3.2-beta there are a couple of changes compared to previous 5.3 releases: === User Feedback plugin MariaDB 5.3.2-beta introduces the User Feedback plugin. This plugin is disabled by default. If enabled, it submits anonymous basic MariaDB usage information. This information will be used by the developers to track trends in MariaDB usage to better guide development efforts. If you would like to help make MariaDB better, please add --plugin-load=feedback.so to your my.cnf file! On Windows, add "feedback=ON" to your my.ini file, or click the checkbox during installation of the MSI package. See http://kb.askmonty.org/en/user-feedback-plugin for more information. === Subquery Cache now on by default Starting in MariaDB 5.3.2-beta, the Subquery cache is on by default. In previous versions of MariaDB the cache was off by default. The goal of the subquery cache is to optimize the evaluation of correlated subqueries by storing results together with correlation parameters in a cache and avoiding re-execution of the subquery in cases where the result is already in the cache. See http://kb.askmonty.org/en/subquery-cache for more information. == MariaDB 5.3.2-beta Release Notes, Changelog, Downloads The release notes for MariaDB 5.3.2-beta are available from: http://kb.askmonty.org/en/mariadb-532-release-notes A complete changelog for this beta is available from: http://kb.askmonty.org/en/mariadb-532-changelog Sources, binaries and packages can be downloaded from: http://downloads.askmonty.org/mariadb/5.3.2/ Debian and Ubuntu packages are available from our mirrored apt repositories. A sources.list generator can be found at: http://downloads.askmonty.org/mariadb/repositories/ The project always strives for quality, and being a beta release, we know that not everything may be perfect. Please take some time to report any issues you may encounter at: https://bugs.launchpad.net/maria Enjoy MariaDB 5.3.2-beta & Happy Testing! -- Daniel Bartholomew MariaDB - http://mariadb.org Monty Program - http://montyprogram.com AskMonty Knowledgebase - http://kb.askmonty.org

1 0

[Maria-discuss] Including MariaDB server and client in my package application???
by wahono sri 06 Oct '11

06 Oct '11

May I include MariaDB files in my software package to make easy for user if they don't know about db server and how to install and configure it to use as db server for my application. I'll prefer my users to choose options of installation package : 1. Acosys Version 4 2. MariaDB Client Library 3. MariaDB Server 4. .... Is it allowed by MariaDB licence? I read MariaDB licence but I am confusing to understand it clearly. Thanks Wahono

4 3

[Maria-discuss] Error install from binary tarballs
by wahono sri 30 Sep '11

30 Sep '11

I use PCLinuxOS and I can't install from RPM or from binary. I got this message from /data/localhost.localhost.err 110930 22:52:06 mysqld_safe Starting mysqld daemon with databases from ./data 110930 22:52:06 [ERROR] mysqld: File '/usr/local/mysql/data/aria_log_control' not found (Errcode: 13) 110930 22:52:06 [ERROR] mysqld: Got error 'Can't open file' when trying to use aria control file '/usr/local/mysql/data/aria_log_control' 110930 22:52:06 [ERROR] Plugin 'Aria' init function returned error. 110930 22:52:06 [ERROR] Plugin 'Aria' registration as a STORAGE ENGINE failed. 110930 22:52:06 [ERROR] Failed to initialize plugins. 110930 22:52:06 [ERROR] Aborting 110930 22:52:06 [Note] ./bin/mysqld: Shutdown complete 110930 22:52:06 mysqld_safe mysqld from pid file ./data/localhost.localdomain.pid ended 110930 22:54:34 mysqld_safe Starting mysqld daemon with databases from /usr/local/mysql/data 110930 22:54:34 [ERROR] ./bin/mysqld: ambiguous option '--o' (old-alter-table, optimizer_switch) 110930 22:54:34 [ERROR] Aborting 110930 22:54:34 mysqld_safe mysqld from pid file /usr/local/mysql/data/localhost.localdomain.pid ended 110930 22:56:00 mysqld_safe Starting mysqld daemon with databases from ./data 110930 22:56:00 [ERROR] ./bin/mysqld: ambiguous option '--o' (old-alter-table, optimizer_switch) 110930 22:56:00 [ERROR] Aborting 110930 22:56:00 mysqld_safe mysqld from pid file ./data/localhost.localdomain.pid ended 110930 23:00:45 mysqld_safe Starting mysqld daemon with databases from ./data 110930 23:00:45 [ERROR] ./bin/mysqld: ambiguous option '--o' (old-alter-table, optimizer_switch) 110930 23:00:45 [ERROR] Aborting 110930 23:00:45 mysqld_safe mysqld from pid file ./data/localhost.localdomain.pid ended 110930 23:01:00 mysqld_safe Starting mysqld daemon with databases from /usr/local/mysql/data 110930 23:01:01 [ERROR] ./bin/mysqld: ambiguous option '--o' (old-alter-table, optimizer_switch) 110930 23:01:01 [ERROR] Aborting 110930 23:01:01 mysqld_safe mysqld from pid file /usr/local/mysql/data/localhost.localdomain.pid ended 110930 23:01:10 mysqld_safe Starting mysqld daemon with databases from /usr/local/mysql/data 110930 23:01:10 [ERROR] ./bin/mysqld: ambiguous option '--o' (old-alter-table, optimizer_switch) 110930 23:01:10 [ERROR] Aborting 110930 23:01:10 mysqld_safe mysqld from pid file /usr/local/mysql/data/localhost.localdomain.pid ended 110930 23:03:41 mysqld_safe Starting mysqld daemon with databases from ./data 110930 23:03:41 [ERROR] ./bin/mysqld: ambiguous option '--o' (old-alter-table, optimizer_switch) 110930 23:03:41 [ERROR] Aborting 110930 23:03:41 mysqld_safe mysqld from pid file ./data/localhost.localdomain.pid ended How to fix this error? Thanks

2 1

[Maria-discuss] New KB Question: MariaDB 5.2.x server RPM fails on upgrades - error: scriptlet failed, exit status 1
by Daniel Bartholomew 30 Sep '11

30 Sep '11

A new question has been posted to the Knowledgebase: MariaDB 5.2.x server RPM fails on upgrades - error: scriptlet failed, exit status 1 http://kb.askmonty.org/en/mariadb-52x-server-rpm-fails-on-upgrades-error-sc… --------------------------------------------------------------------- This problem occurs on CentOS 5.5/5.6/6.0 32bit and 64bit from first time I used MariaDB 5.2.3 all the way to 5.2.9 upgrade. It happens 1) via manual RPM upgrade from RPM downloaded at http://downloads.askmonty.org/mariadb/5.2/#file_type=rpm or 2) via ourdelta YUM REPO update http://ourdelta.org/centos (yum update MariaDB*). Problem, MariaDB-server-5.2.x RPM updates fails and needs manually removing previous version MariaDB-server-5.2.x RPM before the new update installs. error error: %pre(MariaDB-server-5.2.9-102.el5.x86_64) scriptlet failed, exit status 1 error: install: %pre scriptlet failed (2), skipping MariaDB-server-5.2.9-102.el5 full details below ... (continued in the KB) --------------------------------------------------------------------- Thanks. -- Daniel Bartholomew MariaDB - http://mariadb.org Monty Program - http://montyprogram.com AskMonty Knowledgebase - http://kb.askmonty.org

2 2

[Maria-discuss] Microseconds support in MariaDB 5.3.
by Peter Laursen 28 Sep '11

28 Sep '11

I noticed: http://askmonty.org/blog/the-2-year-old-mariadb/ "The support for microseconds in TIMESTAMP, DATETIME, and TIME". I fully agree the 'full seconds support only' has been a sever limitation in MySQL. But I have two concerns with ths: 1) 'noisyness'. On not very fast systems the last digits of a TIME in microseconds should not be considered too much important. It depends on what else the system is doing at the time. I think for lots of users milliseconds and not microseconds would be better/more relevant. It is not always a lot of digits can be proven true. When we went to school we were all taught not to present results in natural sciences more accurate than the accuracy of data sources and measurements. Providing too many digits in a resuslt actually caused a lower score in my highschool! 2) Compability. There is a problem with UPDATES. A client/application written for MySQL may assume 'full seconds support only' and may generate the current MySQL format byte format in the WHERE clause (typically if the client reserves a 14 byte buffer for TIMERSTAMPS etc). In SQL: UPDATE table SET column = 'something' WHERE time_column = '01:01:01': .. this update will fail if the currently stored value is '01:01:01:010001'; and the rigth query in the context would be. UPDATE table SET column = 'something' WHERE time_column = '01:01:01:010001'; Ideally I think there should be a configuration parameter and a global variable to SET time_accuracy = full_second|millisecond|microsecond. Did somebody have considerations about same? I definitely think that lots of applications using a TIME|TIMESTAMP|DATETIME column in the WHERE-clause of an UPDATE statement will need some rewrite to be upgradable to MariaDB 5.3 -- Peter

6 7

[Maria-discuss] New KB Question: Stop/Start MariaDB
by Daniel Bartholomew 27 Sep '11

27 Sep '11

A new question has been posted to the Knowledgebase: http://kb.askmonty.org/en/stopstart-mariadb --------------------------------------------------------------------- When upgrading MariaDb, using DEB package manager,it always fails to stop the server and the upgrade fails. Also the server cannot be stopped from MySQl Workbench. However, I can stop ok from the terminal with the command 'sudo service mysql stop' and then run the update which restarts the server automatically. Not fatal but puzzling. (Using Ubuntu Natty 64 bit). --------------------------------------------------------------------- Thanks. -- Daniel Bartholomew MariaDB - http://mariadb.org Monty Program - http://montyprogram.com AskMonty Knowledgebase - http://kb.askmonty.org

1 0

[Maria-discuss] New KB Question: Index/optimizations in Dynamic Columns
by Daniel Bartholomew 20 Sep '11

20 Sep '11

A new question has been posted to the Knowledgebase: http://kb.askmonty.org/en/indexoptimizations-in-dynamic-columns --------------------------------------------------------------------- Greetz to all... I have been playing with the dynamic columns in MariaDB 5.3... Running your test queries I decided to do an explain on one of them: MariaDB [test]> explain SELECT name FROM t1 WHERE COLUMN_GET(dynstr, 1 as char(10)) = "red"; +----+-------------+-------+------+---------------+------+---------+------+------+-------------+ | id | select_type | table | type | possible_keys | key | key_len | ref | rows | Extra | +----+-------------+-------+------+---------------+------+---------+------+------+-------------+ | 1 | SIMPLE | t1 | ALL | NULL | NULL | NULL | NULL | 4 | Using where | +----+-------------+-------+------+---------------+------+---------+------+------+-------------+ 1 row in set (0.00 sec) I was just curious, do dynamic columns suffer from the same perf penalties at scale that non-indexed or function-based where criteria do? If they currently do, are there currently any plans to index/optimize dynamic columns for super fast at-scale data access? Best, Joshua --------------------------------------------------------------------- Thanks. -- Daniel Bartholomew MariaDB - http://mariadb.org Monty Program - http://montyprogram.com AskMonty Knowledgebase - http://kb.askmonty.org

1 0

[Maria-discuss] MariaDB 5.3.1-beta now available!
by Daniel Bartholomew 12 Sep '11

12 Sep '11

[The following was just sent to the MariaDB 'announce' list (subscribe at http://mariadb.org) Re-posting here for those that are not on that list.] The MariaDB project would like to announce the availability of MariaDB 5.3.1-beta, the latest addition to our growing lineup of supported software. MariaDB 5.3.1-beta is a bug-fix update to the previous 5.3.0-beta. The MariaDB 5.3 series introduces many new features, includes MariaDB 5.2, and is based on MySQL 5.1. Some highlights of new features in MariaDB 5.3 include: - subquery optimizations that finally make subqueries usable - many optimizer changes, including Classic Hash Join, Batched Key Access, a new implementation of Multi-Range-Read optimizations as well as Index Condition Pushdown - NoSQL-style interfaces via the HandlerSocket plugin as well as dynamic columns - group commit in XtraDB when the binary log is enabled - Microsoft Windows performance improvements These are just some of the highlights, and for a full list of changes, please read the What is MariaDB 5.3 page: http://kb.askmonty.org/en/what-is-mariadb-53 A complete changelog for this beta is available from: http://kb.askmonty.org/en/mariadb-531-changelog Sources, binaries and packages can be downloaded from: http://downloads.askmonty.org/mariadb/5.3.1/ Debian and Ubuntu packages are available from repositories. A sources.list generator can be found at: http://downloads.askmonty.org/mariadb/repositories/ The project always strives for quality, and being a beta release, we know that not everything can be perfect. Please take some time to report any issues you may encounter at: https://bugs.launchpad.net/maria Enjoy MariaDB 5.3.1-beta & Happy Testing! -- Daniel Bartholomew MariaDB - http://mariadb.org Monty Program - http://montyprogram.com AskMonty Knowledgebase - http://kb.askmonty.org

1 0

[Maria-discuss] MariaDB compilation on old Linux
by Daniel Bartholomew 12 Sep '11

12 Sep '11

A new question has been posted to the Knowledgebase: http://kb.askmonty.org/en/mariadb-compilation-on-old-linux ---------------------------------------------------------------------- I still have to use MandrakeLinux 10.0 having MySQL v.4.0.22 in its repository. Is it possible to build binary rpm-packages (binary in /usr/bin, data in /var/lib/mysql and etc) of fresh MariaDB on old Linux distribution like MandrakeLinux 10.0 (something like `rpmbuild -bb mysql.spec`)? ---------------------------------------------------------------------- Thanks. -- Daniel Bartholomew MariaDB - http://mariadb.org Monty Program - http://montyprogram.com AskMonty Knowledgebase - http://kb.askmonty.org

1 0

[Maria-discuss] failed to initialize plugins error
by Patrick Galbraith 10 Sep '11

10 Sep '11

Hi all! Moin moin, Privet! I have the latest 5.3 compiled as well as a client's own storage engine. The compile, link, all went well. I do notice they only compile their engine statically, but see symbols for it in mysqld: ... 000000000081d4f0 T filepro_rkey 000000000081d9f0 T filepro_rnext 000000000081da80 T filepro_rprev 000000000081d350 T filepro_rrange 000000000081db20 T filepro_rrnd 000000000081ddc0 T filepro_scan 000000000081dde0 T filepro_scan_init 0000000000e747c8 B filepro_share_list 0000000000e52ea0 D filepro_storage_engine 000000000081de00 T filepro_update 000000000081e020 T filepro_write 0000000000e74798 b ha_filepro_exts ... So, when I start mysqld, I get the error: "[ERROR] Failed to initialize plugins." If I run this with strace, I don't see it trying to load a particular shared library file, just it logging messages to the log, opening replication log and index. So, not sure what I need to load with "plugin_load". When I configured MariaDB top compile, I used the following (per what the client uses with their successful build of MySQL 5.1.30) ./configure --with-plugins=all --without-plugin-oqgraph --with-charset=utf8 --enable-assembler --enable-profiling --enable-community-features --without-plugin-ndbcluster --prefix=/usr/local/maria I'm guessing that I'm missing something obvious and simple? Thank you in advance for any help! Patrick

3 2

[Maria-discuss] Native SQL-Connector for LibreOffice/OpenOffice
by Daniel Bartholomew 07 Sep '11

07 Sep '11

A new question has been posted to the Knowledgebase: http://kb.askmonty.org/en/native-sql-connector-for-libreofficeopenoffice --------------------------------------------------------------------- Hello, I have been using OO/LO for years and have used both the Java-Connector but also ODBC under both Debian-Linux and Windows-Vista. When it became available I switched to the Native MySQL-Connector as delivered by MySQL. Oracle now has obviously got rid of that connector. Is there or are there any plany for a native connector to LO/OO in MariaDB? Thanks for your help and regards H. Stoellinger Salzburg --------------------------------------------------------------------- Thanks. -- Daniel Bartholomew MariaDB - http://mariadb.org Monty Program - http://montyprogram.com AskMonty Knowledgebase - http://kb.askmonty.org

1 0

[Maria-discuss] Is there any java connector for MariaDB than the one from Mysql(mysql-java-5.1.6.jar) ?
by Daniel Bartholomew 01 Sep '11

01 Sep '11

A new question has been posted to the Knowledgebase: http://kb.askmonty.org/en/is-there-any-java-connector-for-mariadb-than-the-… ---------------------------------------------------------------------- For licensing purposes, we try to remove any link to MySQL connectors, we found for Delphi and .NET, but we did not yet find any for java. Does anyone know a third party components that can be used as java connector for MariaDB ? ---------------------------------------------------------------------- Thanks. -- Daniel Bartholomew MariaDB - http://mariadb.org Monty Program - http://montyprogram.com AskMonty Knowledgebase - http://kb.askmonty.org

1 0

Re: [Maria-discuss] GUI/Workbench for MariaDB Aria?
by Peter Laursen 31 Aug '11

31 Aug '11

'transactional' in Aria will eanable crash recovery for the table. It will not make the table transactional (ie. START TRANSACTION, COMMIT, ROLLBACK etc.) are still ignored. Probably it was originaly intended to have it trasactional over time but I do not think focus is there at the moment. Byt yes .. it is just a checkbox and would be simple to add to any GUI (conditionally if engine = ARIA). But I think that if people want (user-)tables with the Aria engine you would use '1' in most if not all cases (temproary tables created by server internally is another thing). -- Peter On Wed, Aug 31, 2011 at 07:47, Ansgar Becker <ansgar.becker(a)googlemail.com>wrote: > Hi all, > I'm a bit unsure what this option really does, now that Peter said it > doesn't make a table transactional, but I'm sure there is a reason for why > it exists. So I'll see if I can add a checkbox right besides the engine drop > down, which is enabled only if Aria is selected. Also I need to read out > this attribute in existing tables, which needs some adjustment in my CREATE > TABLE parser. > > Ansgar > > Am 30.08.2011 19:31, schrieb Peter Laursen: > > We have the same request for SQLyog: > http://code.google.com/p/sqlyog/issues/detail?id=538 > > Of course a client is never engine-specific. But that is not the same > that a client has GUI fucntionalities to su > > @Vlad you probably know that your company (Monty Program) and mine > (Webyog) are partners (what means customers will gain a rebate to our > products when comming from Monty Program website. Check it out or ask Monty > himself). Not that I would mind that Ansgar adds this to Heidi. But > basically we never found it very important. Even if ARIA is set to > transactioanl = 1 , it is not transactional. it has crash recovery what is > not the same. > > > Peter > Webyog > > On Tue, Aug 30, 2011 at 19:11, Vladislav Vaintroub <wlad(a)montyprogram.com>wrote: > >> I'm forwarding this to Ansgar, as a feature request for HeidiSQL. May be >> tricky to add it as Aria-specific option, currently CREATE TABLE >> options/checkboxes in HeidiSQL seem to be not engine dependent to me. >> >> > -----Original Message----- >> > From: maria-discuss- >> > bounces+wlad=montyprogram.com(a)lists.launchpad.net [mailto:maria- >> > discuss-bounces+wlad=montyprogram.com(a)lists.launchpad.net] On Behalf >> > Of Daniel Bartholomew >> > Sent: Dienstag, 30. August 2011 18:50 >> > To: Maria Discuss >> > Subject: [Maria-discuss] GUI/Workbench for MariaDB Aria? >> > >> > New question on the Knowledgebase: >> > >> > http://kb.askmonty.org/en/guiworkbench-for-mariadb-aria >> > >> > Does anybody know a good GUI/Work bench tool to handle ARIA >> > transactional=1/0 and row_format=PAGE situations? >> > >> > Thanks. >> > >> > -- >> > Daniel Bartholomew >> > MariaDB - http://mariadb.org >> > Monty Program - http://montyprogram.com >> > AskMonty Knowledgebase - http://kb.askmonty.org >> > >> > >> > _______________________________________________ >> > Mailing list: https://launchpad.net/~maria-discuss >> > Post to : maria-discuss(a)lists.launchpad.net >> > Unsubscribe : https://launchpad.net/~maria-discuss >> > More help : https://help.launchpad.net/ListHelp >> >> >> _______________________________________________ >> Mailing list: https://launchpad.net/~maria-discuss >> Post to : maria-discuss(a)lists.launchpad.net >> Unsubscribe : https://launchpad.net/~maria-discuss >> More help : https://help.launchpad.net/ListHelp >> > > >

1 0

[Maria-discuss] Good GUI
by md＠rpzdesign.com 30 Aug '11

30 Aug '11

Hello: I have been using Navicat to administer my Oracle/Sun based MySQL servers for years. (www.navicat.com) Now I am switched over to MariaDB 2.8 using ARIA engine. What do MariaDB users recommend of good GUI front end that allows me to manage ARIA Create Table Transactional=0|1 Row_format=PAGE setting. Most Tools do not support all of the MariaDB settings in the table setup dialogs. Suggestions appreciated... md

3 2

[Maria-discuss] GUI/Workbench for MariaDB Aria?
by Daniel Bartholomew 30 Aug '11

30 Aug '11

New question on the Knowledgebase: http://kb.askmonty.org/en/guiworkbench-for-mariadb-aria Does anybody know a good GUI/Work bench tool to handle ARIA transactional=1/0 and row_format=PAGE situations? Thanks. -- Daniel Bartholomew MariaDB - http://mariadb.org Monty Program - http://montyprogram.com AskMonty Knowledgebase - http://kb.askmonty.org

3 2

[Maria-discuss] Frequently running Event overlapping itself
by Brian Evans 17 Aug '11

17 Aug '11

I have an issue where a fast triggering event, running every 30 seconds, is occasionally running multiple times without each finishing. This is causing duplicate data as things are marked done one at a time. I am trying to figure a solution such that this event can only run singly, but what is the best way? DISABLE at start and ENABLE at end? Do SESSION variables work between event invocations?

2 2

[Maria-discuss] Installation issues with PHP5
by Daniel Bartholomew 15 Aug '11

15 Aug '11

A few comments were posted yesterday to the following Knowledgebase article: https://kb.askmonty.org/en/installation-issues-with-php5 The poster is getting mysql_connect errors. He's using CentOS 5 64bit, PHP 5.2, and recently upgraded from MySQL 5.0.77 to MariaDB 5.3. If you have any experience in this area, please consider jumping in and replying to the comments. Thanks! -- Daniel Bartholomew MariaDB - http://mariadb.org Monty Program - http://montyprogram.com AskMonty Knowledgebase - http://kb.askmonty.org

1 0

[Maria-discuss] Bug reporting
by planas 06 Aug '11

06 Aug '11

How does one post a bug? install issue with MariaDB-server-5.2 and 5.3 - fatal, crash on install Ubuntu 11.04 see below for terminal reports for both sudo apt-get install mariadb-server-5.2 Reading package lists... Done Building dependency tree Reading state information... Done The following extra packages will be installed: libdbd-mysql-perl libmariadbclient16 libmysqlclient16 mariadb-client-5.2 mariadb-client-core-5.2 mariadb-server-core-5.2 mysql-common Suggested packages: mailx mariadb-test The following NEW packages will be installed: libdbd-mysql-perl libmariadbclient16 libmysqlclient16 mariadb-client-5.2 mariadb-client-core-5.2 mariadb-server-5.2 mariadb-server-core-5.2 mysql-common 0 upgraded, 8 newly installed, 0 to remove and 2 not upgraded. Need to get 21.4 MB/21.5 MB of archives. After this operation, 51.2 MB of additional disk space will be used. Do you want to continue [Y/n]? y Get:1 http://ftp.osuosl.org/pub/mariadb/repo/5.2/ubuntu/ natty/main mysql-common all 5.2.7-mariadb101~natty [10.6 kB] Get:2 http://ftp.osuosl.org/pub/mariadb/repo/5.2/ubuntu/ natty/main libmariadbclient16 amd64 5.2.7-mariadb101~natty [1,454 kB] Get:3 http://ftp.osuosl.org/pub/mariadb/repo/5.2/ubuntu/ natty/main libmysqlclient16 amd64 5.2.7-mariadb101~natty [4,300 B] Get:4 http://ftp.osuosl.org/pub/mariadb/repo/5.2/ubuntu/ natty/main mariadb-client-core-5.2 amd64 5.2.7-mariadb101~natty [93.7 kB] Get:5 http://ftp.osuosl.org/pub/mariadb/repo/5.2/ubuntu/ natty/main mariadb-client-5.2 amd64 5.2.7-mariadb101~natty [1,759 kB] Get:6 http://ftp.osuosl.org/pub/mariadb/repo/5.2/ubuntu/ natty/main mariadb-server-core-5.2 amd64 5.2.7-mariadb101~natty [4,474 kB] Get:7 http://ftp.osuosl.org/pub/mariadb/repo/5.2/ubuntu/ natty/main mariadb-server-5.2 amd64 5.2.7-mariadb101~natty [13.6 MB] Fetched 21.4 MB in 6s (3,166 kB/s) Preconfiguring packages ... Selecting previously deselected package mysql-common. (Reading database ... 458443 files and directories currently installed.) Unpacking mysql-common (from .../mysql-common_5.2.7-mariadb101~natty_all.deb) ... Selecting previously deselected package libmariadbclient16. Unpacking libmariadbclient16 (from .../libmariadbclient16_5.2.7-mariadb101~natty_amd64.deb) ... Selecting previously deselected package libmysqlclient16. Unpacking libmysqlclient16 (from .../libmysqlclient16_5.2.7-mariadb101~natty_amd64.deb) ... Selecting previously deselected package libdbd-mysql-perl. Unpacking libdbd-mysql-perl (from .../libdbd-mysql-perl_4.016-1_amd64.deb) ... Selecting previously deselected package mariadb-client-core-5.2. Unpacking mariadb-client-core-5.2 (from .../mariadb-client-core-5.2_5.2.7-mariadb101~natty_amd64.deb) ... Selecting previously deselected package mariadb-client-5.2. Unpacking mariadb-client-5.2 (from .../mariadb-client-5.2_5.2.7-mariadb101~natty_amd64.deb) ... Selecting previously deselected package mariadb-server-core-5.2. Unpacking mariadb-server-core-5.2 (from .../mariadb-server-core-5.2_5.2.7-mariadb101~natty_amd64.deb) ... Processing triggers for man-db ... Processing triggers for menu ... Setting up mysql-common (5.2.7-mariadb101~natty) ... Selecting previously deselected package mariadb-server-5.2. (Reading database ... 458622 files and directories currently installed.) Unpacking mariadb-server-5.2 (from .../mariadb-server-5.2_5.2.7-mariadb101~natty_amd64.deb) ... Processing triggers for man-db ... Processing triggers for ureadahead ... Setting up libmysqlclient16 (5.2.7-mariadb101~natty) ... Setting up libmariadbclient16 (5.2.7-mariadb101~natty) ... Setting up libdbd-mysql-perl (4.016-1) ... Setting up mariadb-client-core-5.2 (5.2.7-mariadb101~natty) ... Setting up mariadb-client-5.2 (5.2.7-mariadb101~natty) ... Setting up mariadb-server-core-5.2 (5.2.7-mariadb101~natty) ... Setting up mariadb-server-5.2 (5.2.7-mariadb101~natty) ... ' * Stopping MariaDB database server mysqld [ OK ] 110805 19:21:20 [Note] Plugin 'PBXT' is disabled. 110805 19:21:20 [Note] Plugin 'InnoDB' is disabled. * Starting MariaDB database server mysqld [fail] invoke-rc.d: initscript mysql, action "start" failed. dpkg: error processing mariadb-server-5.2 (--configure): subprocess installed post-installation script returned error exit status 1 Processing triggers for libc-bin ... ldconfig deferred processing now taking place Processing triggers for menu ... Errors were encountered while processing: mariadb-server-5.2 E: Sub-process /usr/bin/dpkg returned an error code (1) sudo apt-get install mariadb-server-5.3 Reading package lists... Done Building dependency tree Reading state information... Done The following extra packages will be installed: libdbd-mysql-perl libmariadbclient16 libmysqlclient16 mariadb-client-5.3 mariadb-client-core-5.3 mariadb-server-core-5.3 mysql-common Suggested packages: mailx mariadb-test The following NEW packages will be installed: libdbd-mysql-perl libmariadbclient16 libmysqlclient16 mariadb-client-5.3 mariadb-client-core-5.3 mariadb-server-5.3 mariadb-server-core-5.3 mysql-common 0 upgraded, 8 newly installed, 0 to remove and 2 not upgraded. Need to get 22.8 MB of archives. After this operation, 56.5 MB of additional disk space will be used. Do you want to continue [Y/n]? y Get:1 http://ftp.osuosl.org/pub/mariadb/repo/5.3/ubuntu/ natty/main mysql-common all 5.3.0-mariadb101~natty [10.7 kB] Get:2 http://ftp.osuosl.org/pub/mariadb/repo/5.3/ubuntu/ natty/main libmariadbclient16 amd64 5.3.0-mariadb101~natty [1,517 kB] Get:3 http://us.archive.ubuntu.com/ubuntu/ natty/main libdbd-mysql-perl amd64 4.016-1 [140 kB] Get:4 http://ftp.osuosl.org/pub/mariadb/repo/5.3/ubuntu/ natty/main libmysqlclient16 amd64 5.3.0-mariadb101~natty [4,356 B] Get:5 http://ftp.osuosl.org/pub/mariadb/repo/5.3/ubuntu/ natty/main mariadb-client-core-5.3 amd64 5.3.0-mariadb101~natty [94.1 kB] Get:6 http://ftp.osuosl.org/pub/mariadb/repo/5.3/ubuntu/ natty/main mariadb-client-5.3 amd64 5.3.0-mariadb101~natty [1,760 kB] Get:7 http://ftp.osuosl.org/pub/mariadb/repo/5.3/ubuntu/ natty/main mariadb-server-core-5.3 amd64 5.3.0-mariadb101~natty [4,719 kB] Get:8 http://ftp.osuosl.org/pub/mariadb/repo/5.3/ubuntu/ natty/main mariadb-server-5.3 amd64 5.3.0-mariadb101~natty [14.5 MB] Fetched 22.8 MB in 6s (3,556 kB/s) Preconfiguring packages ... Selecting previously deselected package mysql-common. (Reading database ... 458566 files and directories currently installed.) Unpacking mysql-common (from .../mysql-common_5.3.0-mariadb101~natty_all.deb) ... Selecting previously deselected package libmariadbclient16. Unpacking libmariadbclient16 (from .../libmariadbclient16_5.3.0-mariadb101~natty_amd64.deb) ... Selecting previously deselected package libmysqlclient16. Unpacking libmysqlclient16 (from .../libmysqlclient16_5.3.0-mariadb101~natty_amd64.deb) ... Selecting previously deselected package libdbd-mysql-perl. Unpacking libdbd-mysql-perl (from .../libdbd-mysql-perl_4.016-1_amd64.deb) ... Selecting previously deselected package mariadb-client-core-5.3. Unpacking mariadb-client-core-5.3 (from .../mariadb-client-core-5.3_5.3.0-mariadb101~natty_amd64.deb) ... Selecting previously deselected package mariadb-client-5.3. Unpacking mariadb-client-5.3 (from .../mariadb-client-5.3_5.3.0-mariadb101~natty_amd64.deb) ... Selecting previously deselected package mariadb-server-core-5.3. Unpacking mariadb-server-core-5.3 (from .../mariadb-server-core-5.3_5.3.0-mariadb101~natty_amd64.deb) ... Processing triggers for man-db ... Processing triggers for menu ... Setting up mysql-common (5.3.0-mariadb101~natty) ... Selecting previously deselected package mariadb-server-5.3. (Reading database ... 458747 files and directories currently installed.) Unpacking mariadb-server-5.3 (from .../mariadb-server-5.3_5.3.0-mariadb101~natty_amd64.deb) ... Processing triggers for man-db ... Processing triggers for ureadahead ... Setting up libmysqlclient16 (5.3.0-mariadb101~natty) ... Setting up libmariadbclient16 (5.3.0-mariadb101~natty) ... Setting up libdbd-mysql-perl (4.016-1) ... Setting up mariadb-client-core-5.3 (5.3.0-mariadb101~natty) ... Setting up mariadb-client-5.3 (5.3.0-mariadb101~natty) ... Setting up mariadb-server-core-5.3 (5.3.0-mariadb101~natty) ... Setting up mariadb-server-5.3 (5.3.0-mariadb101~natty) ... * Stopping MariaDB database server mysqld [ OK ] 110805 19:01:37 [Note] Plugin 'PBXT' is disabled. 110805 19:01:37 [Note] Plugin 'InnoDB' is disabled. * Starting MariaDB database server mysqld [fail] invoke-rc.d: initscript mysql, action "start" failed. dpkg: error processing mariadb-server-5.3 (--configure): subprocess installed post-installation script returned error exit status 1 Processing triggers for libc-bin ... ldconfig deferred processing now taking place Processing triggers for menu ... Errors were encountered while processing: mariadb-server-5.3 E: Sub-process /usr/bin/dpkg returned an error code (1) I have spent days trying to fully resolve this. One should be able uninstall and reinstall a package as needed without tracking down bugs in the installer or uninstaller scripts. Logs have been blank or just repeat the above information. -- Jay Lozier jslozier(a)gmail.com

2 1

[Maria-discuss] Cannot install Mariadb-server-5.2
by planas 04 Aug '11

04 Aug '11

Hi I have been struggling to get mariadb to work. My problems have been either the server is very erratic, usually will not start it. After trying a complete reinstall I can not install the mariadb-server-5.2 package either from the repository or from a deb. I am using Ubuntu/Pinguy 11.04. The installation results from apt-get or aptitude are sudo aptitude install mariadb-server-5.2 The following NEW packages will be installed: mariadb-server-5.2 0 packages upgraded, 1 newly installed, 0 to remove and 21 not upgraded. Need to get 13.6 MB of archives. After unpacking 30.8 MB will be used. Get:1 http://ftp.osuosl.org/pub/mariadb/repo/5.2/ubuntu/ natty/main mariadb-server-5.2 amd64 5.2.7-mariadb101~natty [13.6 MB] Fetched 13.6 MB in 4s (2,733 kB/s) Preconfiguring packages ... (Reading database ... 427308 files and directories currently installed.) Unpacking mariadb-server-5.2 (from .../mariadb-server-5.2_5.2.7-mariadb101~natty_amd64.deb) ... Aborting downgrade from (at least) 5.3 to 5.2. If are sure you want to downgrade to 5.2, remove the file /var/lib/mysql/debian-*.flag and try installing again. dpkg: error processing /var/cache/apt/archives/mariadb-server-5.2_5.2.7-mariadb101~natty_amd64.deb (--unpack): subprocess new pre-installation script returned error exit status 1 Errors were encountered while processing: /var/cache/apt/archives/mariadb-server-5.2_5.2.7-mariadb101~natty_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) A package failed to install. Trying to recover: I tried MySQL 5.1.7 from the Ubuntu repository and got the same results. Searching various forums/online information has not turned up an answer including MySQL and Ubuntu. -- Jay Lozier jslozier(a)gmail.com

2 1

[Maria-discuss] A couple of new questions in the Knowledgebase
by Daniel Bartholomew 02 Aug '11

02 Aug '11

All, While I was out on vacation it appears a couple of new questions were posted to the Knowledgebase. If you have some time, please take a look. Thanks! Missing mysqld.sock file http://kb.askmonty.org/en/missing-mysqldsock-file and myisam_use_mmap does not use mmap after a massive insert http://kb.askmonty.org/en/myisam_use_mmap-does-not-use-mmap-after-a-massive… -- Daniel Bartholomew MariaDB - http://mariadb.org Monty Program - http://montyprogram.com AskMonty Knowledgebase - http://kb.askmonty.org

2 1

[Maria-discuss] MariaDB 5.3 on lenny crashing about every 8 minutes
by Carsten Bernhard 02 Aug '11

02 Aug '11

Hi, I have installed MariaDB 5.3 from the apt packages on a lenny amd64 machine. Initial setup went fine and the database is working correctly. When I give some load to the machine I get crashes about every 8 minutes. This is what the log shows: Jul 29 00:36:17 svn mysqld: 110729 0:36:17 [ERROR] mysqld got signal 11 ; Jul 29 00:36:17 svn mysqld: This could be because you hit a bug. It is also poss ible that this binary Jul 29 00:36:17 svn mysqld: or one of the libraries it was linked against is cor rupt, improperly built,Jul 29 00:36:17 svn mysqld: or misconfigured. This error can also be caused by m alfunctioning hardware. Jul 29 00:36:17 svn mysqld: We will try our best to scrape up some info that will hopefully help diagnose Jul 29 00:36:17 svn mysqld: the problem, but since we have already crashed, some thing is definitely wrongJul 29 00:36:17 svn mysqld: and this may fail. Jul 29 00:36:17 svn mysqld: Jul 29 00:36:17 svn mysqld: key_buffer_size=0 Jul 29 00:36:17 svn mysqld: read_buffer_size=2097152 Jul 29 00:36:17 svn mysqld: max_used_connections=13 Jul 29 00:36:17 svn mysqld: max_threads=102 Jul 29 00:36:17 svn mysqld: threads_connected=1 Jul 29 00:36:17 svn mysqld: It is possible that mysqld could use up toJul 29 00:36:17 svn mysqld: key_buffer_size + (read_buffer_size + sort_buffer_si ze)*max_threads = 627994 K Jul 29 00:36:17 svn mysqld: bytes of memoryJul 29 00:36:17 svn mysqld: Hope that's ok; if not, decrease some variables in t he equation. Jul 29 00:36:17 svn mysqld: Jul 29 00:36:17 svn mysqld: Thread pointer: 0x7f1740013780Jul 29 00:36:17 svn mysqld: Attempting backtrace. You can use the following info rmation to find outJul 29 00:36:17 svn mysqld: where mysqld died. If you see no messages after this , something went Jul 29 00:36:17 svn mysqld: terribly wrong... Jul 29 00:36:17 svn mysqld: stack_bottom = 0x41614110 thread_stack 0x48000Jul 29 00:36:17 svn mysqld: /usr/sbin/mysqld(my_print_stacktrace+0x2e) [0x7f176c 0dc1de]Jul 29 00:36:17 svn mysqld: /usr/sbin/mysqld(handle_segfault+0x448) [0x7f176bce3 de8] Jul 29 00:36:17 svn mysqld: /lib/libpthread.so.0 [0x7f176a281a80]Jul 29 00:36:17 svn mysqld: /usr/sbin/mysqld(JOIN::optimize()+0x22) [0x7f176bd68 c52] Jul 29 00:36:17 svn mysqld: /usr/sbin/mysqld(mysql_derived_optimize(THD*, st_lex*, TABLE_LIST*)+0x12e) [0x7f176be52fbe] Jul 29 00:36:17 svn mysqld: /usr/sbin/mysqld(mysql_handle_single_derived(st_lex*, TABLE_LIST*, unsigned int)+0x10e) [0x7f176be53c3e] Jul 29 00:36:17 svn mysqld: /usr/sbin/mysqld(st_select_lex::handle_derived(st_lex*, unsigned int)+0x48) [0x7f176bc07528] Jul 29 00:36:17 svn mysqld: /usr/sbin/mysqld(JOIN::optimize()+0xb2) [0x7f176bd68ce2] Jul 29 00:36:17 svn mysqld: /usr/sbin/mysqld(mysql_derived_optimize(THD*, st_lex*, TABLE_LIST*)+0x12e) [0x7f176be52fbe] Jul 29 00:36:17 svn mysqld: /usr/sbin/mysqld(mysql_handle_single_derived(st_lex*, TABLE_LIST*, unsigned int)+0x10e) [0x7f176be53c3e] Jul 29 00:36:17 svn mysqld: /usr/sbin/mysqld(st_select_lex::handle_derived(st_lex*, unsigned int)+0x48) [0x7f176bc07528] Jul 29 00:36:17 svn mysqld: /usr/sbin/mysqld(JOIN::optimize()+0xb2) [0x7f176bd68ce2] Jul 29 00:36:17 svn mysqld: /usr/sbin/mysqld(mysql_select(THD*, Item***, TABLE_LIST*, unsigned int, List<Item>&, Item*, unsigned int, st_order*, st_order*, Item*, st_order*, unsigned long long, select_result*, st_select_lex_unit*, st_select_lex*)+0x104) [0x7f176bd70a84] Jul 29 00:36:17 svn mysqld: /usr/sbin/mysqld(handle_select(THD*, st_lex*, select_result*, unsigned long)+0x171) [0x7f176bd714c1] Jul 29 00:36:17 svn mysqld: /usr/sbin/mysqld [0x7f176bcef8fb] Jul 29 00:36:17 svn mysqld: /usr/sbin/mysqld(mysql_execute_command(THD*)+0x1ef9) [0x7f176bcf2239] Jul 29 00:36:17 svn mysqld: /usr/sbin/mysqld(mysql_parse(THD*, char*, unsigned int, char const**)+0x2c1) [0x7f176bcf6181] Jul 29 00:36:17 svn mysqld: /usr/sbin/mysqld(dispatch_command(enum_server_command, THD*, char*, unsigned int)+0xde1) [0x7f176bcf8941] Jul 29 00:36:17 svn mysqld: /usr/sbin/mysqld(do_command(THD*)+0x100) [0x7f176bcf9230] Jul 29 00:36:17 svn mysqld: /usr/sbin/mysqld(handle_one_connection+0xe4) [0x7f176bceacf4] Jul 29 00:36:17 svn mysqld: /lib/libpthread.so.0 [0x7f176a279fc7] Jul 29 00:36:17 svn mysqld: /lib/libc.so.6(clone+0x6d) [0x7f176985764d] Jul 29 00:36:17 svn mysqld: Jul 29 00:36:17 svn mysqld: Trying to get some variables. Jul 29 00:36:17 svn mysqld: Some pointers may be invalid and cause the dump to abort. Jul 29 00:36:17 svn mysqld: Query (0x7f176ec35988): SELECT * FROM ( Jul 29 00:36:17 svn mysqld: SELECT @rn := if( @lc = l.l_contentid, @rn +1, 0 ) AS rnum, @lc := l_contentid, l.* Jul 29 00:36:17 svn mysqld: FROM vb3_vbseo_likes l, (SELECT @rn :=0, @lc :=0) r Jul 29 00:36:17 svn mysqld: WHERE l_ctype = 1 AND l_cgroup =39820 AND l_contentid IN (289195,289196 ) Jul 29 00:36:17 svn mysqld: ORDER BY l_contentid Jul 29 00:36:17 svn mysqld: ) as nest Jul 29 00:36:17 svn mysqld: where rnum<3 Jul 29 00:36:17 svn mysqld: Connection ID (thread ID): 511 Jul 29 00:36:17 svn mysqld: Status: NOT_KILLED Jul 29 00:36:17 svn mysqld: Jul 29 00:36:17 svn mysqld: The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains Jul 29 00:36:17 svn mysqld: information that should help you find out what is causing the crash. Jul 29 00:36:17 svn mysqld_safe: Number of processes running now: 0 Jul 29 00:36:17 svn mysqld_safe: mysqld restarted Just to confirm the installed packages: dpkg --get-selections | grep maria libmariadbclient16 install mariadb-client-5.3 install mariadb-client-core-5.3 install mariadb-server-5.3 install mariadb-server-core-5.3 install Any pointers? Cheers, Carsten

3 2

[Maria-discuss] MariaDB on Windows and Aria Temp Tables
by Brian Evans 01 Aug '11

01 Aug '11

I recently installed MariaDB 5.2.7 Win-x64 to a machine from http://downloads.askmonty.org/mariadb/. When I did 'SELECT @@aria_used_for_temp_tables;', it returned 0. I know this a compile time option and was wondering if this was intended. Several references I've found point that it is meant to be enabled by default. Thanks

2 1

[Maria-discuss] Help with RPM src build
by bwellsnc 22 Jul '11

22 Jul '11

I have gone over every document concerning building mariadb using src rpm. I am trying to build mariadb against RHEL 6. I have run rpmbuild against the src rpm and I get this error everytime: error: configure: error: C compiler cannot create executables The instructions, I have to admit, are not very good about building using the source rpm. If there is anyone who has a better howto, I would really appreciate it. Thanks! Brent

3 11

[Maria-discuss] mariadb runs at lowest priority (nice -n 19)
by Panayot Belchev 13 Jun '11

13 Jun '11

Hi, I just noticed that all our MariaDB 5.2 servers show the same: $ ps -eo ni,comm |grep mysql 9 mysqld_safe 19 mysql_isam_spac <defunct> 19 mysqld While servers with Oracle MySQL are at nice -n 0 I tried setting niceness=-10 in /usr/bin/mysqld_safe but with no effect. Is there a reason to run MariaDB at the lowest possible priority and is there a way to change that?

4 7

[Maria-discuss] XtraDB using the Windows Installer
by Jake Drew 09 Jun '11

09 Jun '11

I have a couple of questions regarding XtraDB. 1. I am curious, if XtraDB is turned on / installed by default when MariaDB is installed using the windows installer on a Windows 2008 R2 server? 2. Is this default behavior the same in 5.1.53 and 5.2.6? 3. How can I tell if XtraDB is currently installed on any given MariaDB install? i.e. Is there a SHOW or other similar command I can run to confirm that XtraDB is installed?

5 4

[Maria-discuss] Calculating Maximum Bytes Per Record
by Jake Drew 08 Jun '11

08 Jun '11

*Hello, * * * *I have recently been doing some capacity planning exercises for a new database we are developing in MariaDB. One of the exercises I completed was to create a database with all tables loaded with maximum width records at 100,000, 500,000, and 1,000,000 records. I noticed that when I did this it seems that the larger the tables grow, the less bytes per record are required. I am curious what causes this to happen? These are all InnoDB tables saved to their own tablespaces.* * Max Bytes Per Record Record Count Record Count Record Count 100,000 500,000 1,000,000 acct_activation 241 176 164 acct_deactivated 419 336 327 disk_usage 136 75 63 keywords 713 646 633 pods 77,511 56,698 53,126 pods_joined 178 101 96 pod_activity 461 369 357 pod_files 78,224 57,220 53,615 sessions 168 92 80 users 1,426 1,351 1,338 usr_profile 78,392 57,343 53,730 * *I also created a query (using Information_Schema.Columns) to calculate maximum possible bytes per record / table (SQL attached below). I ran the query and compared the estimates to the actual values produced above. The query is close, but I would like to make it a little more accurate if possible. * *TABLE_SCHEMA* *TABLE_NAME* *PK_BYTES_TOT* *FIELD_BYTES_TOT* * IX_FIELD_BYTES_TOT* *IX_FIELD_COUNT* *IX_OVERHEAD_BYTES* *IX_BYTES_TOT* * TABLE_BYTES_TOT* pods acct_activation 0 73 33 1 29 62 *189* pods acct_deactivated 8 269 0 0 0 0 *388* pods devices 1 273 0 0 0 0 *384* pods disk_usage 8 32 0 0 0 0 *56* pods keywords 0 264 264 2 58 322 *820* pods pods 8 65,821 16 1 29 45 *92,224* pods pods_joined 0 16 16 2 58 74 *126* pods pod_activity 0 275 9 1 29 38 *438* pods pod_files 8 66,376 56 2 58 114 *93,097* pods sessions 0 10 10 2 58 68 *109* pods users 8 1,112 41 1 29 70 *1,666* pods usr_profile 8 66,628 0 0 0 0 *93,290* *Does anyone have any suggestions for my calculations in the code below to make it more accurate?* * * *Basic Assumptions * * * - Calculated field widths are defined by data type in the CASE logic below. - Primary key bytes = The sum of all defined PK calculated field widths - Index Bytes = Primary key bytes + Index calculated field width + 29 bytes overhead (for each index defined) - 1 byte is added to each field that is Nullable. - All bytes defined above are multiplied by 1.4 for BTREE overhead.* * * * *Current SQL to calculate MAX record bytes by table:* * * SELECT B.TABLE_SCHEMA , B.TABLE_NAME , SUM(PK_BYTES) AS PK_BYTES_TOT , SUM(FIELD_BYTE_SPACE) AS FIELD_BYTES_TOT , SUM(IX_BYTES) AS IX_FIELD_BYTES_TOT , SUM(CASE WHEN IX_BYTES > 0 THEN 1 ELSE 0 END) AS IX_FIELD_COUNT , SUM(CASE WHEN IX_BYTES > 0 THEN 1 ELSE 0 END) * 29 AS IX_OVERHEAD_BYTES , (SUM(CASE WHEN IX_BYTES > 0 THEN 1 ELSE 0 END) * 29) + SUM(IX_BYTES) AS IX_BYTES_TOT , (SUM(PK_BYTES) + SUM(FIELD_BYTE_SPACE) + (SUM(CASE WHEN IX_BYTES > 0 THEN 1 ELSE 0 END) * 29) + SUM(IX_BYTES)) * 1.4 AS TABLE_BYTES_TOT FROM ( SELECT A.* , CASE WHEN COLUMN_KEY = 'PRI'THEN FIELD_BYTE_SPACE ELSE 0 END AS PK_BYTES , CASE WHEN A.COLUMN_KEY <> 'PRI' AND A.COLUMN_KEY <> '' THEN (PK_BYTE_SPACE + FIELD_BYTE_SPACE) ELSE 0 END AS IX_BYTES FROM ( SELECT PK_SP.TABLE_SCHEMA , PK_SP.TABLE_NAME , PK_SP.COLUMN_NAME , DATA_TYPE , CHARACTER_MAXIMUM_LENGTH , NUMERIC_PRECISION , IS_NULLABLE , COLUMN_KEY , CHARACTER_SET_NAME , CHARACTER_OCTET_LENGTH , (CASE -- CHARACTER FIELDS WHEN DATA_TYPE = 'varchar' THEN CHARACTER_MAXIMUM_LENGTH + 1 WHEN DATA_TYPE = 'char' THEN CHARACTER_MAXIMUM_LENGTH WHEN DATA_TYPE = 'tinyblob' OR DATA_TYPE = 'tinytext' THEN CHARACTER_MAXIMUM_LENGTH + 1 WHEN DATA_TYPE = 'blob' OR DATA_TYPE = 'text' THEN CHARACTER_MAXIMUM_LENGTH + 2 WHEN DATA_TYPE = 'mediumblob' OR DATA_TYPE = 'mediumtext' THEN CHARACTER_MAXIMUM_LENGTH + 3 WHEN DATA_TYPE = 'largeblob' OR DATA_TYPE = 'largetext' THEN CHARACTER_MAXIMUM_LENGTH + 4 -- NUMERIC FIELDS WHEN DATA_TYPE = 'tinyint' THEN 1 WHEN DATA_TYPE = 'smallint' THEN 2 WHEN DATA_TYPE = 'mediumint' THEN 3 WHEN DATA_TYPE = 'int' OR DATA_TYPE = 'integer' THEN 4 WHEN DATA_TYPE = 'bigint' THEN 8 WHEN DATA_TYPE = 'float' AND (NUMERIC_PRECISION <= 24 OR NUMERIC_PRECISION IS NULL) THEN 4 WHEN DATA_TYPE = 'float' AND NUMERIC_PRECISION > 24 THEN 8 WHEN DATA_TYPE = 'bit' THEN (NUMERIC_PRECISION + 7) / 8 WHEN DATA_TYPE = 'double' OR DATA_TYPE = 'numeric' THEN (FLOOR(NUMERIC_PRECISION/9)*4) + ROUND((NUMERIC_PRECISION- FLOOR(NUMERIC_PRECISION/9)*9)*.5,0) -- DATETIME FIELDS WHEN DATA_TYPE = 'date' OR DATA_TYPE = 'time' THEN 3 WHEN DATA_TYPE = 'datetime' THEN 8 WHEN DATA_TYPE = 'timestamp' THEN 4 WHEN DATA_TYPE = 'year' THEN 1 ELSE 999999999999999 END) + (CASE WHEN IS_NULLABLE = 'YES' THEN 1 ELSE 0 END) AS FIELD_BYTE_SPACE , CASE WHEN PK_BYTE_SPACE IS NULL THEN 0 ELSE PK_BYTE_SPACE END AS PK_BYTE_SPACE FROM information_schema.columns AS PK_SP LEFT OUTER JOIN (SELECT TABLE_SCHEMA , TABLE_NAME , SUM((CASE -- CHARACTER FIELDS WHEN DATA_TYPE = 'varchar' THEN CHARACTER_MAXIMUM_LENGTH + 1 WHEN DATA_TYPE = 'char' THEN CHARACTER_MAXIMUM_LENGTH WHEN DATA_TYPE = 'tinyblob' OR DATA_TYPE = 'tinytext' THEN CHARACTER_MAXIMUM_LENGTH + 1 WHEN DATA_TYPE = 'blob' OR DATA_TYPE = 'text' THEN CHARACTER_MAXIMUM_LENGTH + 2 WHEN DATA_TYPE = 'mediumblob' OR DATA_TYPE = 'mediumtext' THEN CHARACTER_MAXIMUM_LENGTH + 3 WHEN DATA_TYPE = 'largeblob' OR DATA_TYPE = 'largetext' THEN CHARACTER_MAXIMUM_LENGTH + 4 -- NUMERIC FIELDS WHEN DATA_TYPE = 'tinyint' THEN 1 WHEN DATA_TYPE = 'smallint' THEN 2 WHEN DATA_TYPE = 'mediumint' THEN 3 WHEN DATA_TYPE = 'int' OR DATA_TYPE = 'integer' THEN 4 WHEN DATA_TYPE = 'bigint' THEN 8 WHEN DATA_TYPE = 'float' AND (NUMERIC_PRECISION <= 24 OR NUMERIC_PRECISION IS NULL) THEN 4 WHEN DATA_TYPE = 'float' AND NUMERIC_PRECISION > 24 THEN 8 WHEN DATA_TYPE = 'bit' THEN (NUMERIC_PRECISION + 7) / 8 WHEN DATA_TYPE = 'double' OR DATA_TYPE = 'numeric' THEN (FLOOR(NUMERIC_PRECISION/9)*4) + ROUND((NUMERIC_PRECISION- FLOOR(NUMERIC_PRECISION/9)*9)*.5,0) -- DATETIME FIELDS WHEN DATA_TYPE = 'date' OR DATA_TYPE = 'time' THEN 3 WHEN DATA_TYPE = 'datetime' THEN 8 WHEN DATA_TYPE = 'timestamp' THEN 4 WHEN DATA_TYPE = 'year' THEN 1 ELSE 999999999999999 END) + (CASE WHEN IS_NULLABLE = 'YES' THEN 1 ELSE 0 END)) AS PK_BYTE_SPACE FROM information_schema.columns COL_SP WHERE COLUMN_KEY = 'PRI' AND TABLE_SCHEMA = 'PODS' GROUP BY TABLE_SCHEMA , TABLE_NAME) AS IX_SP ON PK_SP.TABLE_SCHEMA = IX_SP.TABLE_SCHEMA AND PK_SP.TABLE_NAME = IX_SP.TABLE_NAME WHERE PK_SP.TABLE_SCHEMA = 'PODS') AS A ) AS B GROUP BY B.TABLE_SCHEMA , B.TABLE_NAME * *

1 0

[Maria-discuss] Reqeust for SHOW FULL FIELDS FROM and virtual tables in MariaDB
by Peter Laursen 06 Jun '11

06 Jun '11

Refer http://kb.askmonty.org/v/virtual-columns - the example CREATE TABLE table1 ( a INT NOT NULL, b VARCHAR(32), c INT AS (a MOD 10) virtual, d VARCHAR(5) AS (LEFT(b,5)) persistent); now SHOW FULL FIELDS FROM table1; Field Type Collation Null Key Default Extra Privileges Comment ------ ----------- ----------------- ------ ------ ------- ------- ------------------------------- ------- a int(11) (NULL) NO (NULL) select,insert,update,references b varchar(32) latin1_swedish_ci YES (NULL) select,insert,update,references c int(11) (NULL) YES (NULL) VIRTUAL select,insert,update,references d varchar(5) latin1_swedish_ci YES (NULL) VIRTUAL select,insert,update,references I request that 'extra' column should return either "PERSISTENT" or " VIRTUAL, PERSISTENT" for column `d`. The reason is that the output from SHOW FULL FIELDS returns an *array* (that will not need to be parsed) as opposite to SHOW CREATE TABLE. Accordingly SHOW FULL FIELDS is much easier to use for an 'unintelligent client' as opposed to an 'intelligent (or ignorant for that sake :-) ) human user to decide on special properties for a column. Peter Webyog

3 4

[Maria-discuss] New Knowledgebase Question: MariaDB xtradb installation problem
by Daniel Bartholomew 04 Jun '11

04 Jun '11

Hello everyone, there's a new question in the Knowledgebase: http://kb.askmonty.org/v/mariadb-xtradb-installation-problem Thanks. -- Daniel Bartholomew MariaDB - http://mariadb.org Monty Program - http://montyprogram.com AskMonty Knowledgebase - http://kb.askmonty.org

1 0

[Maria-discuss] Support for MariaDB Configuration Options in MySQL Workbench
by Jake Drew 26 May '11

26 May '11

It looks like the MySQL Workbench team has decided to place support for MariaDB configuration file options in the next release of MySQL Workbench! (Configuration file option tabs currently display blank for any MariaDB versions greater than 5.1 in MySQL Workbench) http://bugs.mysql.com/bug.php?id=61219

1 0

[Maria-discuss] UserStats = 1
by Jake Drew 18 May '11

18 May '11

I am interested in turning on user statistics as described here: http://kb.askmonty.org/v/user-statistics. However, when I add the line userstats = 1 to the my.ini file under the [mysqld] section, the server will not restart. I am running MariaDB 5.1.53 on Windows Server 2008 R2. Is there anything else I need to install before I am able to use this option?

3 3

[Maria-discuss] 5.2.6 .msi isntaller questions issues
by Peter Laursen 14 May '11

14 May '11

I think this is for @wlad! :-) I just installed 5.2.6 using the new .msi installer. This was an upgrade 'on top' of the previous (5.2.3 or 5.2.4) .msi build distributed by wlad in mailing list. The installer worked fine, The previos 5.2 instance was upgraded (ie. executables and similar files replaced, old my.ini and datadir is still used etc.). So far so good. The problem is with the configuration wizard. What is it supposed to do? Run 'mysql_upgrade'? More than this or something else? Let me explain my setup. Except for this MariaDB instance (running as service 'maria52') I have both MySQL/Oracle 5.0, 5.1, 5.5 and 5.6 (running as services 'MySQL50, 'MySQL51' , 'MySQL55' , 'MySQL56') . The config wizard prompts me which instance should be upgraded an gives me a choice of 'MySQL50 and 'MySQL51' but not 'MySQL55', 'MySQL56' and 'maria52'. 1) Now if the wizard starts 'mysql_upgrade' it makes perfect sense not to offer to upgrade 'MySQL55' and 'MySQL56' (as MySQL51/MariaDb52 are 'lower' than those - it would be a 'downgrade' - not an 'upgrade' then - what 'mysql_upgrade' does not handle). But ideally I think they should be displayed but 'greyed out' or otherwise indicated that upgrading MySQL 5.5/5.6 --> MariaDB 5.2 is not possible. 2) More important: the instance that I *really* wanted to upgrade ('maria52') was not displayed. I assume that the services' list is filtered by the prefix 'mysql'. Am I right? In that case I suggest the filtering is done on both (OR'ed) prefixes 'mysql' and 'maria'. Anyway after just exiting the wizard before executing it everything seems fine. But the wizard GUI can still be 'polished' a little I think. -- Peter Laursen -- Webyog

2 1

[Maria-discuss] New Knowledgebase Question
by Daniel Bartholomew 12 May '11

12 May '11

Here's a new question in the Knowlegebase about running MariaDB and MySQL side-by-side on the same server. http://kb.askmonty.org/v/mariadb-coexist-with-mysql The text of the question: ---------------------------------------------------------------- Hello, I'm currently using MySQL and would like to test MariaDB. I only have one server, and don't wish to overwrite the current MySQL instance. Is it possible to have both MySQL and MariaDB to coexist within the same environment? How can I define the mysql client on which db to connect to? by port? Many thanks! ---------------------------------------------------------------- Anyone with real-world experience in running (or trying to run) MariaDB side-by-side with MySQL want to add a comment to (or answer) this question? I thought I remembered seeing an email thread on this topic a while back but my search-fu is weak today and I can't find it (well, either that or I'm imagining things). Thanks. -- Daniel Bartholomew MariaDB - http://mariadb.org Monty Program - http://montyprogram.com AskMonty Knowledgebase - http://kb.askmonty.org

2 1

[Maria-discuss] How to fix the fact that MariaDB runs as 'mysql', instead of 'mysqld' now.
by Bradley D. Thornton 07 May '11

07 May '11

-----BEGIN PGP SIGNED MESSAGE----- Hash: RIPEMD160 I've run into a problem with implementations of MariaDB where I get messages like "mysqld: unrecognized service". This threw me for a loop at first because everything seems to be fine on the surface, drop in replacement as usual, etc. The problem, seems to be related to something I hadn't noticed before, which is that MariaDB runs as 'mysql', instead of 'mysqld'. Is there a tutorial or howto related to this issue? I would imagine that it is a common occurrence (not a bug, obviously, yet still an issue that might need to be addressed on a regular basis when performing installations). Although I usually use Slackware, on the particular CentOS 5.6 box that is giving me the problem, the executibles/scripts that I have are located: /usr/bin/mysqld_multi /usr/bin/mysqld_safe /usr/bin/mysqldump /usr/bin/mysqldumpslow /usr/sbin/mysqld To be specific, I installed PiaF via a script onto a running host under VMware ESXI, that I prepared from scratch, had some libraries, yet no real install of MySQL. That made the installation of MariaDB even easier than usual, until I had prepped the box and ran the installation script, which at one point pulls binaries from the pbxinaflash.com site as a bundle. I've been sifting through the code, to see if I can correct this, yet figure that I'll have endless headaches when, for example, I perform updates to the PBX system. Therefore, I'm thinking that symlinking or something of that nature is the most effective solution, as part of my standard EllisonCO eradication philosophy, to avoid such issues in the future. Any assistance in this regard would be greatly appreciated, and go a long way towards me completing a complete removal of all MySQL Servers under my purview. Kindest regards, - -- Bradley D. Thornton Manager Network Services NorthTech Computer TEL: +1.760.666.2703 (US) TEL: +44.203.318.2755 (UK) http://NorthTech.US -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Find this cert at x-hkp://pool.sks-keyservers.net iQEcBAEBAwAGBQJNxNIRAAoJEE1wgkIhr9j3S1IH/iZHW2yYwI6K0S5nOwIMVj+C OVqNG5W5+wdzN6XAIBWhoh6PO7o9YDxoow59qdaHN4yw9fmGRFVadSg9PHcQZd7g yRVyTnuPALFWJ5YSOurC2rhyYKUQfV+oqEV6AXfznF7YOZSr47fJG1Mrw7IBO2dl GGjxmq7P/e1SsBAcOe7c6Okj5MxKlAk5S/gzRqeIcLthtRaKoNBIQhDaG36tnUNn rXWvhe1nU8vz7E9ZbFOvWE9Qe40j/P6nNtmcTeUTlP+0wc3Jue0h6+Nk7sWpZe4a 15KZx4AZHT417m+OpEpsn4CdNCkNVcdH606ijo60A/FVyyeTSZb2d5tI2bM13wM= =ng1q -----END PGP SIGNATURE-----

2 2

[Maria-discuss] Hibernate & MariaDB
by Daniel Bartholomew 21 Apr '11

21 Apr '11

New question in the Knowledgebase: http://kb.askmonty.org/v/hibernate-mariadb ---------------------------------------------------------------------- Hello, what settings do I need in a Hibernate (/Spring) configuration file (XML) for MariaDB? The same as in MySQL? Which URL, JDBC driver and Hibernate dialect I have to use? Thanks in advance! Greetings: Anke ---------------------------------------------------------------------- Anyone with any experience with Hibernate and Spring want to jump in and comment on (or answer) this question? If not I will just answer with the standard "If it works with MySQL it will work with MariaDB...." Thanks. -- Daniel Bartholomew MariaDB - http://mariadb.org Monty Program - http://montyprogram.com AskMonty Knowledgebase - http://kb.askmonty.org

2 1

[Maria-discuss] dynamic columns interface
by MARK CALLAGHAN 19 Apr '11

19 Apr '11

Will dynamic columns always require the position (column_nr argument)? I prefer an interface in which that is not required. -- Mark Callaghan mdcallag(a)gmail.com

3 3

[Maria-discuss] New comment in the Knowledgebase
by Daniel Bartholomew 13 Apr '11

13 Apr '11

All, A new comment ( http://kb.askmonty.org/v/about-xtradb#comment_76 ) was just posted on the Knowledgebase on the About XtraDB page ( http://kb.askmonty.org/v/about-xtradb ). The text of the comment is: ------------------------------------- How do I activate XtraDB to replace InnoDB? I have searched this website and Percona and have not found this question or answer. I have a clean, rpm install on openSuse 11.3 (x86_64) of mariadb-5.1.51-8.1.x86_64. I copied over /etc/my.cnf which works with MySQL 5.1.43sp1. It has several options like innodb_file_per_table under section [mysqld], yet when I try to run "mysql_install_db --user=mysql", I get errors for every InnoDB option like: [ERROR] /usr/sbin/mysqld: unknown option '--innodb_file_per_table' ------------------------------------- Any thoughts or comments from the list? Please reply here or directly to the comment in the Knowledgebase. Thanks! -- Daniel Bartholomew MariaDB - http://mariadb.org Monty Program - http://montyprogram.com AskMonty Knowledgebase - http://kb.askmonty.org

1 0

[Maria-discuss] MariaDB 5.6
by Peter Laursen 12 Apr '11

12 Apr '11

I noticed this on planet.mysql: http://kb.askmonty.org/v/plans-for-56 I *again* strongly want to discourage a major version number identical with a MySQL/Oracle release. MySQL plans a 5.6 too and I believe that there is already a source-tree available on launchpad. I think I understand that MariaDB 5.6 is planned to use MySQL 5.5 codebase. Am I correct? The problem arises with *generic clients* (ie clients that are supposed to work with not only one specific server version but a broad range of server versions) - including all GUI clients. Such clients will execute a "SELECT VERSION()" after connection to decide what features in the client should be enabled or not (necessary as "SHOW VARIABLES LIKE 'have_***"" and "SELECT ... FROM I_S" cannot always be used due to incomplete instrumentation with those) I have now posted this complaint 2 or 3 times (including the times I complained about the use of 5.2 for a mariaDB based on MySQL 5.1 code as there is alose a (now abandoned) MySQL 5.2 tree. I never had a reply from a MariaDB 'decisionmaker'. Could I at least request a reply this time? Please! :-) I repeat: It is really causing problems for *generic clients* if there are too different 5.6's with different feature sets. What solution would you suggest for a client that shall be able to connect to both MySQL5.6 and MariaDB 5.6 without confusing the features of one server with the other? Peter Webyog

3 5

[Maria-discuss] FreeBSD BuildBot Slave - I can offer one
by Jakob Lorberblatt 07 Apr '11

07 Apr '11

Hello, I noticed that you do not have a regular build of FreeBSD for either common architecture (x86_64 or i386) I would be able to provide that for you, I have equipment to spare and would be willing to lend this to the project for building assistance; in addition I am fairly familiar with FreeBSD compilation in general so I can also help with any issues that arise. I can begin configuring this host for the service, if I could have some direction towards what needs to be done in order for the MariaDB project at large to be able to make use of it. I believe I used to have some bookmarks of resources regarding the matter. However I don't have the references off the top of my head. -- Jakob Lorberblatt President / Technical Lead Beowolf Information Technology Email: jakob(a)native-intelligence.net

3 2

[Maria-discuss] MariaDB and Sun CoolThread
by Alexandre Almeida 05 Apr '11

05 Apr '11

Hi all, I am installing MariaDB on a server Sun/Oracle T5140 with CoolThread/ CMT technology. This server has two physical Sparc CPU with 48 1165MHZ virtual processors each. However, it's look like that MariaDB is performing much better on my MacBook Pro when compared against this server. As far as I can see MariaDB stay locked/running on a single virtual CPU and MariaDB doesn't take advantage of CoolThread/CMT technologies, I mean it can not run on more than one virtual CPU same time. Result: poor performance. Anybody knows if there is something can I do to spread ;-) MariaDB all over cpus? Am I missing something? Thank you all Alex

5 5

Re: [Maria-discuss] Dynamic columns Library
by Michael Widenius 05 Apr '11

05 Apr '11

Hi! I am cc:ing maria-discuss as you accidently forgot to also email the patch there. >>>>> "Oleksandr" == Oleksandr Byelkin <sanja(a)askmonty.org> writes: Oleksandr> Hi! Oleksandr> Here it is dynamic columns library. I do not think that you will have time to review it completely, but please look at it. Oleksandr> Some notes: Oleksandr> - I changed indices from int to uint + some other minor changes in prototypes. Oleksandr> - dynamic_column_exists() has no way to report error (what to do?) I assume that same problem exists for all the other functions. Two options: - Change function type from my_bool to int where -1 means something went bad (like bad format for the blob). - Add an 'error' argument to all functions that is set to <> 0 if something goes wrong. I think we should go with first option, as this is how many other MariaDB functions work. Oleksandr> - inability to get length without keeping data in the same order as headers (because we store only offsets) lead to +1 memove call (i.e we prefer size to speed of update) I think this is ok. We can proably avoid the +1 memmove call by combining the call when we add things to the header to when we place the data in it's right place. For example, on insert <h1><h3><data1><data3> When adding h2 we would first do: <h1><h3><data1><data3> -> <h1><h3><data1><place for h2 + data2><data3> -> <h1><h3><data1><place for h2><data2><data3> -> <h1><h2><h3><data1><data2><data3> In other words, one memove of all data (trough 2 calls) Oleksandr> - sorry for absence of comment but I prefer unit testing and finishing the library in time. ok. > === added file 'include/ma_dyncol.h' > --- include/ma_dyncol.h 1970-01-01 00:00:00 +0000 > +++ include/ma_dyncol.h 2011-03-27 22:36:38 +0000 > @@ -0,0 +1,87 @@ > +#ifndef ma_dyncol_h > +#define ma_dyncol_h > + > +#include <my_global.h> You can assume that my_global.h is done. > +#include <my_sys.h> > +#include <m_string.h> > +#include <decimal.h> > +#include <my_decimal_limits.h> > +#include <mysql_time.h> > + > +typedef DYNAMIC_STRING DYNAMIC_COLUMN; > + > +enum enum_dynamic_column_type > +{ > + DYN_COL_NULL= 0, > + DYN_COL_INT, > + DYN_COL_UINT, > + DYN_COL_DOUBLE, > + DYN_COL_STRING, > + DYN_COL_DECIMAL, > + DYN_COL_DATETIME, > + DYN_COL_DATE, > + DYN_COL_TIME > +}; > + > +typedef enum enum_dynamic_column_type DYNAMIC_COLUMN_TYPE; > + > +struct st_dynamic_column_value > +{ > + DYNAMIC_COLUMN_TYPE type; > + union > + { > + long long long_value; > + unsigned long long ulong_value; > + double double_value; > + struct { > + LEX_STRING string_value; > + CHARSET_INFO *charset; > + }; > + struct { > + decimal_digit_t decimal_buffer[DECIMAL_BUFF_LENGTH]; > + decimal_t decimal_value; > + }; > + MYSQL_TIME time_value; > + }; > +}; > + > +typedef struct st_dynamic_column_value DYNAMIC_COLUMN_VALUE; > + > +my_bool dynamic_column_create(DYNAMIC_COLUMN *str, > + uint column_nr, > + DYNAMIC_COLUMN_VALUE *value); > + > +my_bool dynamic_column_create_many(DYNAMIC_COLUMN *str, > + uint column_count, > + uint *column_numbers, > + DYNAMIC_COLUMN_VALUE *values); > + > +my_bool dynamic_column_update(DYNAMIC_COLUMN *org, uint column_nr, > + DYNAMIC_COLUMN_VALUE *value); > + > +my_bool dynamic_column_delete(DYNAMIC_COLUMN *org, uint column_nr); > + > +/* Returns 1 if value exists */ > +my_bool dynamic_column_exists(DYNAMIC_COLUMN *org, uint column_nr); > + > +/* List of not NULL columns */ > +my_bool dynamic_column_list(DYNAMIC_COLUMN *org, DYNAMIC_ARRAY *array_of_uint); > + > +/* > + TODO: ask - return 1 on error, if column do not exists it is NULL > +*/ Yes! Same for all the above functions. > +my_bool dynamic_column_get(DYNAMIC_COLUMN *org, int column_nr, > + DYNAMIC_COLUMN_VALUE *store_it_here); > + > +#define dynamic_column_column_free(V) dynstr_free(V) > + > +#define dynamic_column_value_init(V) (V)->type= DYN_COL_NULL > + > +void dynamic_column_value_free(DYNAMIC_COLUMN_VALUE *value); > + > +/* > + Prepare value for using as decimal > +*/ > +void dynamic_column_prepare_decimal(DYNAMIC_COLUMN_VALUE *value); > + > +#endif > === modified file 'mysys/Makefile.am' > --- mysys/Makefile.am 2010-11-19 21:33:47 +0000 > +++ mysys/Makefile.am 2011-03-24 13:54:12 +0000 > @@ -57,7 +57,7 @@ > my_handler.c my_netware.c my_largepage.c \ > my_memmem.c stacktrace.c \ > my_windac.c my_access.c base64.c my_libwrap.c \ > - wqueue.c > + wqueue.c ma_dyncol.c > libmysys_la_LDFLAGS = $(AM_LDFLAGS) @WRAPLIBS@ > libmysys_la_LIBADD = $(ZLIB_LIBS) > === added file 'mysys/ma_dyncol.c' > --- mysys/ma_dyncol.c 1970-01-01 00:00:00 +0000 > +++ mysys/ma_dyncol.c 2011-03-27 22:36:38 +0000 > @@ -0,0 +1,1084 @@ > +#include <ma_dyncol.h> > + > +/* > + Flag byte bits > + > + 2 bits which determinate size of offset in the header > + > + 1 byte > + 2 byte > + 3 byte > + 3 byte > +*/ > +#define DYNCOL_FLG_OFFSET1 0 > +#define DYNCOL_FLG_OFFSET2 1 > +#define DYNCOL_FLG_OFFSET3 2 > +#define DYNCOL_FLG_OFFSET4 3 I don't see where you use the above or understand how you would use this. > +/* mask to get above bits */ > +#define DYNCOL_FLG_OFFSET 3 > +/* All known flags mask */ > +#define DYNCOL_FLG_KNOWN 3 > + > + > +/* dynamic column size reserve */ > +#define DYNCOL_SYZERESERVE 80 > + > + > +static my_bool dynamic_column_time_add(DYNAMIC_COLUMN *str, > + MYSQL_TIME *value); > +static my_bool dynamic_column_date_add(DYNAMIC_COLUMN *str, > + MYSQL_TIME *value); > +static my_bool > +dynamic_column_time_read_int(DYNAMIC_COLUMN_VALUE *store_it_here, > + uchar *data, size_t length); > +static my_bool > +dynamic_column_date_read_int(DYNAMIC_COLUMN_VALUE *store_it_here, > + uchar *data, size_t length); > + > + > +my_bool dynamic_column_init_str(DYNAMIC_COLUMN *str, size_t size) > +{ > + if (!size) > + size= DYNCOL_SYZERESERVE; > + /* > + Make string with no fields (empty header) > + - First \0 is flags > + - other four \0 is 0 fileds counter > + */ > + if (init_dynamic_string(str, NULL, > + size + 5, DYNCOL_SYZERESERVE)) > + return TRUE; > + return dynstr_append_mem(str, "\0\0\0\0\0", 5); > +} Why is an empty data 5 bytes instead of 1 or even 0? > + > +/* > + How many bytes needed to store val as variable length integer where > + fist bit indicate continuation of the sequence > +*/ > +size_t dynamic_column_var_uint_bytes(ulonglong val) > +{ > + size_t len= 0; > + do > + { > + len++; > + val>>= 7; > + } while (val); > + return len; > +} > + > +my_bool dynamic_column_var_uint_add(DYNAMIC_COLUMN *str, ulonglong val) > +{ > + if (dynstr_realloc(str, 10)) // max what we can use > + return TRUE; > + > + do > + { > + ulonglong rest= val >> 7; > + str->str[str->length++]= ((val & 0x7f) | (rest ? 0x80 : 0x00)); > + val= rest; > + } while (val); > + return FALSE; > +} > +ulonglong dynamic_column_var_uint_get(uchar *data, size_t *len) > +{ > + ulonglong val= 0; > + *len= 0; > + for(;;) > + { > + val+= (((ulonglong)(data[len[0]] & 0x7f)) << (len[0]*7)); > + if (!(data[len[0]] & 0x80)) > + break; > + len[0]++; > + } > + len[0]++; > + return val; > +} > + > +/* > + How many bytes needed to store val as unsigned > +*/ > + > +size_t dynamic_column_uint_bytes(ulonglong val) > +{ > + size_t len= 0; > + do > + { > + len++; > + val>>= 8; > + } while (val); > + return len; > +} > + > +my_bool dynamic_column_uint_add(DYNAMIC_COLUMN *str, ulonglong val) > +{ > + if (dynstr_realloc(str, 8)) // max what we can use > + return TRUE; > + do > + { > + str->str[str->length++]= val & 0xff; > + val>>= 8; > + } while (val); > + return FALSE; > +} Better to change all the _add' columns to take a pointer where to store the data, not a dynamic column. This makes it easier to do things like only one memmove In other words: void dynamic_column_uint_add(uchar *data, ulonglong val) { for ( ; val ; val>>= 8) *data++= val & 0xff; return FALSE; } We must test for val first to get 0 stored in 0 bytes A nice change is that no of the _add primitives can fail anymore, so we can make all of them void. > +my_bool dynamic_column_uint_read(DYNAMIC_COLUMN_VALUE *store_it_here, > + uchar *data, > + size_t length) > +{ > + ulonglong value= 0; > + size_t i; > + for (i= 0; i < length; i++) > + { > + value+= ((ulonglong)data[i]) << (i*8); > + } > + store_it_here->ulong_value= value; > + return FALSE; > +} Send pointer to store_it_here->ulong_value to the function. (Makes it more general) > + > +/* > + How many bytes needed to store val as signed in following encoding: > + 0 -> 0 > + -1 -> 1 > + 1 -> 2 > + -2 -> 3 > + 2 -> 4 > + ... > +*/ > + > +size_t dynamic_column_sint_bytes(longlong val) > +{ > + return dynamic_column_uint_bytes((val << 1) ^ > + (val < 0 ? ULL(0xffffffffffffffff) : 0)); > +} > + > +my_bool dynamic_column_sint_add(DYNAMIC_COLUMN *str, longlong val) > +{ > + return dynamic_column_uint_add(str, > + (val << 1) ^ > + (val < 0 ? ULL(0xffffffffffffffff) : 0)); > +} > +my_bool dynamic_column_sint_read(DYNAMIC_COLUMN_VALUE *store_it_here, > + uchar *data, > + size_t length) > +{ > + ulonglong val; > + dynamic_column_uint_read(store_it_here, data, length); > + val= store_it_here->ulong_value; > + if (val & 1) > + val= (val >> 1) ^ ULL(0xffffffffffffffff); > + else > + val>>= 1; > + store_it_here->long_value= (longlong)(val); > + return FALSE; > +} Quite clever. The idea I had to store these are: - Store positive integers as DYN_COL_UINT - Store negative numbers as DYN_COL_INT, which just makes them positive and uses the DYN_COL_UINT functions to store the. > + > +size_t dynamic_column_value_len(DYNAMIC_COLUMN_VALUE *value) > +{ > + switch (value->type) { > + case DYN_COL_NULL: > + return 0; > + case DYN_COL_INT: > + return dynamic_column_sint_bytes(value->long_value); > + case DYN_COL_UINT: > + return dynamic_column_uint_bytes(value->ulong_value); > + case DYN_COL_DOUBLE: > + return 8; > + case DYN_COL_STRING: > + return (dynamic_column_var_uint_bytes(value->charset->number) + > + value->string_value.length); > + case DYN_COL_DECIMAL: > + return (dynamic_column_var_uint_bytes(value->decimal_value.intg) + > + dynamic_column_var_uint_bytes(value->decimal_value.frac) + > + decimal_bin_size(value->decimal_value.intg + > + value->decimal_value.frac, > + value->decimal_value.frac)); We should probably store the value of dynamic_column_var_uint_bytes(...) cols in a parameter (size_t lengths[3]) to make things easier for the caller. > + case DYN_COL_DATETIME: > + /* date+time in bits: 14 + 4 + 5 + 5 + 6 + 6 + 20 + 1 61bits = 8 bytes */ > + return 8; > + case DYN_COL_DATE: > + /* date in dits: 14 + 4 + 5 = 23bits ~= 3bytes*/ > + return 3; > + case DYN_COL_TIME: > + /* time in bits: 5 + 6 + 6 + 20 + 1 = 38bits ~= 5bytes*/ > + return 5; > + default: > + DBUG_ASSERT(0); > + return 0; > + } > +} > + > +my_bool dynamic_column_double_add(DYNAMIC_COLUMN *str, double val) > +{ > + if (dynstr_realloc(str, 8)) > + return TRUE; > + float8store(str->str + str->length, val); > + str->length+= 8; > + return FALSE; > +} See comment for adding to integer for how to change this > + > +my_bool dynamic_column_double_read(DYNAMIC_COLUMN_VALUE *store_it_here, > + uchar *data, > + size_t length) > +{ > + if (length != 8) > + return TRUE; > + float8get(store_it_here->double_value, data); > + return FALSE; > +} > + > + > +my_bool dynamic_column_string_add(DYNAMIC_COLUMN *str, LEX_STRING *string, > + CHARSET_INFO *charset) > +{ > + if (dynamic_column_var_uint_add(str, charset->number)) > + return TRUE; > + return dynstr_append_mem(str, string->str, string->length); > +} If we just send data, and not DYNAMIC_COLUMN's, this should be changed to: my_bool dynamic_column_string_add(uchar *data, LEX_STRING *string, uint charset_number, size_t charset_storage_size) { dynamic_column_var_uint_add(data, charset_number)) memmove(data + charset_storage_size, string->str, string->length); } > + > +my_bool dynamic_column_string_read(DYNAMIC_COLUMN_VALUE *store_it_here, > + uchar *data, > + size_t length) > +{ > + size_t len; > + store_it_here->charset= get_charset(dynamic_column_var_uint_get(data, &len), > + MYF(0)); > + if (store_it_here->charset == NULL || len > length) > + return FALSE; Should return -1 > + data+= len; > + store_it_here->string_value.length= (length-= len); > + if (!(store_it_here->string_value.str= malloc(length + 1))) > + return FALSE; > + store_it_here->type= DYN_COL_STRING; // just to correctly destroy the value > + memcpy(store_it_here->string_value.str, data, length); > + store_it_here->string_value.str[length]= '\0'; // just to be safe Don't malloc it. Just return a pointer to the string in the dynamic data! (Yes, now \0, but we can live with that for the additional speed of not having to do malloc for every access). > + return TRUE; > +} > + > + > +my_bool dynamic_column_decimal_add(DYNAMIC_COLUMN *str, > + decimal_t *value) > +{ > + uint bin_size= decimal_bin_size(value->intg + value->frac, value->frac); > + if (dynamic_column_var_uint_add(str, value->intg) || > + dynamic_column_var_uint_add(str, value->frac) || > + dynstr_realloc(str, bin_size)) > + return TRUE; > + decimal2bin(value, (uchar *)str->str + str->length, value->intg + value->frac, > + value->frac); > + str->length+= bin_size; > + return FALSE; > +} To change this, we need to know the sizes for the intg and frac lengths. Can be done by storing them in an array when we calculate them. C > + > +void dynamic_column_prepare_decimal(DYNAMIC_COLUMN_VALUE *value) > +{ > + value->decimal_value.buf= value->decimal_buffer; > + value->decimal_value.len= DECIMAL_BUFF_LENGTH; > + // just to be safe > + value->type= DYN_COL_DECIMAL; > + decimal_make_zero(&value->decimal_value); > +} > + > +my_bool dynamic_column_decimal_read(DYNAMIC_COLUMN_VALUE *store_it_here, > + uchar *data, > + size_t length __attribute__((unused))) > +{ > + size_t len; > + uint intg, frac; > + > + dynamic_column_prepare_decimal(store_it_here); > + intg= dynamic_column_var_uint_get(data, &len); > + data+= len; > + frac= dynamic_column_var_uint_get(data, &len); > + data+= len; > + if (bin2decimal(data, &store_it_here->decimal_value, intg + frac, frac) != > + E_DEC_OK) > + return TRUE; > + return FALSE; > +} > + > + > +my_bool dynamic_column_date_time_add(DYNAMIC_COLUMN *str, MYSQL_TIME *value) > +{ > + /* > + 0<----year----><mn><day>00!<hr-><min-><sec-><---microseconds---> > + 12345678901234123412345 11234512345612345612345678901234567890 > + <123456><123456><123456><123456><123456><123456><123456><123456> > + */ > + return (dynamic_column_date_add(str, value) || > + dynamic_column_time_add(str, value)); > +} > + > + > +my_bool dynamic_column_date_time_read(DYNAMIC_COLUMN_VALUE *store_it_here, > + uchar *data, > + size_t length) > +{ > + /* > + 0<----year----><mn><day>00!<hr-><min-><sec-><---microseconds---> > + 12345678901234123412345 11234512345612345612345678901234567890 > + <123456><123456><123456><123456><123456><123456><123456><123456> > + */ > + if (length != 8) > + goto err; > + store_it_here->time_value.time_type= MYSQL_TIMESTAMP_DATETIME; > + if (dynamic_column_date_read_int(store_it_here, data, 3) || > + dynamic_column_time_read_int(store_it_here, data + 3, 5)) > + goto err; > + return FALSE; > + > +err: > + store_it_here->time_value.time_type= MYSQL_TIMESTAMP_ERROR; > + return TRUE; > +} > + > + > +my_bool dynamic_column_time_add(DYNAMIC_COLUMN *str, MYSQL_TIME *value) > +{ > + uchar *buf= ((uchar *)str->str) + str->length; > + if (dynstr_realloc(str, 5)) > + return TRUE; > + if (value->time_type == MYSQL_TIMESTAMP_NONE || > + value->time_type == MYSQL_TIMESTAMP_ERROR || > + value->time_type == MYSQL_TIMESTAMP_DATE) > + value->neg= value->second_part= value->hour= > + value->minute= value->second= 0; > + DBUG_ASSERT(value->hour <= 23); note that for time arguments, hour can be bigger than 23 ! (as this is elapsed time, not a wall-clock time) > + DBUG_ASSERT(value->minute <= 59); > + DBUG_ASSERT(value->second <= 59); > + DBUG_ASSERT(value->second_part <= 999999); > + /* > + 00!<hr-><min-><sec-><---microseconds---> > + 11234512345612345612345678901234567890 > + <123456><123456><123456><123456><123456> > + */ > + buf[0]= (value->second_part & 0xff); > + buf[1]= ((value->second_part & 0xff00) >> 8); > + buf[2]= (((value->second & 0xf) << 4) | > + ((value->second_part & 0xf0000) >> 16)); > + buf[3]= ((value->minute << 2) | ((value->second & 0x30) >> 4)); > + buf[4]= ((value->neg ? 0x20 : 0) | value->hour); Good but hard to read and verify. Another way would to store this in an uint and then just use int5store() to store it. We need to store at least the same precision of time as MariaDB is doing in a normal field. This means a hour up to TIME_MAX_HOUR which is 838, which means you need to use another byte for the hour. > + str->length+= 5; > + return FALSE; > +} > + > + > +my_bool dynamic_column_time_read(DYNAMIC_COLUMN_VALUE *store_it_here, > + uchar *data, > + size_t length) > +{ > + store_it_here->time_value.year= store_it_here->time_value.month= > + store_it_here->time_value.day= 0; No reason to reset the parts. Either the function should work or we should get an error. > + store_it_here->time_value.time_type= MYSQL_TIMESTAMP_TIME; > + return dynamic_column_time_read_int(store_it_here, data, length); > +} > + > + > +my_bool dynamic_column_time_read_int(DYNAMIC_COLUMN_VALUE *store_it_here, > + uchar *data, > + size_t length) > +{ > + if (length != 5) > + goto err; > + /* > + 00!<hr-><min-><sec-><---microseconds---> > + 11234512345612345612345678901234567890 > + <123456><123456><123456><123456><123456> > + */ > + store_it_here->time_value.second_part= (data[0] | > + (data[1] << 8) | > + ((data[2] & 0xf) << 16)); > + store_it_here->time_value.second= ((data[2] >> 4) | > + ((data[3] & 0x3) << 4)); > + store_it_here->time_value.minute= (data[3] >> 2); > + store_it_here->time_value.hour= (data[4] & 0x1f); > + store_it_here->time_value.neg= ((data[4] & 0x20) ? 1 : 0); > + if (store_it_here->time_value.second > 59 || > + store_it_here->time_value.minute > 59 || > + store_it_here->time_value.hour > 23 || > + store_it_here->time_value.second_part > 999999) > + goto err; > + return FALSE; Hour should not be checked. > + > +err: > + store_it_here->time_value.time_type= MYSQL_TIMESTAMP_ERROR; > + return TRUE; > +} > + > + > +my_bool dynamic_column_date_add(DYNAMIC_COLUMN *str, MYSQL_TIME *value) > +{ > + uchar *buf= ((uchar *)str->str) + str->length; > + if (dynstr_realloc(str, 3)) > + return TRUE; > + if (value->time_type == MYSQL_TIMESTAMP_NONE || > + value->time_type == MYSQL_TIMESTAMP_ERROR || > + value->time_type == MYSQL_TIMESTAMP_TIME) > + value->year= value->month= value->day = 0; > + DBUG_ASSERT(value->year <= 9999); > + DBUG_ASSERT(value->month <= 12); > + DBUG_ASSERT(value->day <= 31); > + /* > + 0<----year----><mn><day> > + 012345678901234123412345 > + <123456><123456><123456> > + */ > + buf[0]= (value->day | > + ((value->month & 0x7) << 5)); > + buf[1]= ((value->month >> 3) | ((value->year & 0x7F) << 1)); > + buf[2]= (value->year >> 7); > + str->length+= 3; > + return FALSE; > +} > + > +my_bool dynamic_column_date_read(DYNAMIC_COLUMN_VALUE *store_it_here, > + uchar *data, > + size_t length) > +{ > + store_it_here->time_value.neg= store_it_here->time_value.second_part= > + store_it_here->time_value.hour= store_it_here->time_value.minute= > + store_it_here->time_value.second= 0; Don't reset the above. > + store_it_here->time_value.time_type= MYSQL_TIMESTAMP_DATE; > + return dynamic_column_date_read_int(store_it_here, data, length); > +} > + > +my_bool dynamic_column_date_read_int(DYNAMIC_COLUMN_VALUE *store_it_here, > + uchar *data, > + size_t length) > +{ > + if (length != 3) > + goto err; > + /* > + 0<----year----><mn><day> > + 12345678901234123412345 > + <123456><123456><123456> > + */ > + store_it_here->time_value.day= (data[0] & 0x1f); > + store_it_here->time_value.month= (((data[1] & 0x1) << 3) | > + (data[0] >> 5)); > + store_it_here->time_value.year= ((((uint)data[2]) << 7) | > + (data[1] >> 1)); > + if (store_it_here->time_value.day > 31 || > + store_it_here->time_value.month > 12 || > + store_it_here->time_value.year > 9999) > + goto err; > + return FALSE; > + > +err: > + store_it_here->time_value.time_type= MYSQL_TIMESTAMP_ERROR; > + return TRUE; > +} > + > + > +my_bool data_add(DYNAMIC_COLUMN *str, DYNAMIC_COLUMN_VALUE *value) > +{ Change to take uchar *data instead of DYNAMIC_COLUMN > + switch (value->type) { > + case DYN_COL_INT: > + return dynamic_column_sint_add(str, value->long_value); > + case DYN_COL_UINT: > + return dynamic_column_uint_add(str, value->ulong_value); > + case DYN_COL_DOUBLE: > + return dynamic_column_double_add(str, value->double_value); > + case DYN_COL_STRING: > + return dynamic_column_string_add(str, &value->string_value, > + value->charset); > + case DYN_COL_DECIMAL: > + return dynamic_column_decimal_add(str, &value->decimal_value); > + case DYN_COL_DATETIME: > + /* date+time in bits: 14 + 4 + 5 + 5 + 6 + 6 40bits = 5 bytes */ > + return dynamic_column_date_time_add(str, &value->time_value); > + case DYN_COL_DATE: > + /* date in dits: 14 + 4 + 5 = 23bits ~= 3bytes*/ > + return dynamic_column_date_add(str, &value->time_value); > + case DYN_COL_TIME: > + /* time in bits: 5 + 6 + 6 = 17bits ~= 3bytes*/ > + return dynamic_column_time_add(str, &value->time_value); > + default: > + DBUG_ASSERT(0); > + return TRUE; > + } > +} > + > + > +size_t dynamic_column_offset_bytes(size_t data_length) > +{ > + if (data_length < 0x1f) // all 1 value is reserved > + return 1; > + if (data_length < 0x1fff) // all 1 value is reserved > + return 2; > + if (data_length < 0x1fffff) // all 1 value is reserved > + return 3; > + if (data_length < 0x1fffffff) // all 1 value is reserved > + return 4; > + return 5; > +} > + > + > +void type_and_offset_store(uchar *place, size_t offset_size, > + DYNAMIC_COLUMN_TYPE type, > + size_t offset) > +{ > + ulong val = (((ulong) offset) << 3) | (type - 1);; Make 3 a define. Remove double ; > + DBUG_ASSERT(type != DYN_COL_NULL); > + DBUG_ASSERT(((type - 1) & (~7)) == 0); // fit in 3 bits type <= 8 would also work... > + switch (offset_size) { > + case 1: > + DBUG_ASSERT(offset < 0x1f); // all 1 value is reserved > + place[0]= (uchar)val; > + break; > + case 2: > + DBUG_ASSERT(offset < 0x1fff); // all 1 value is reserved > + int2store(place, val); > + break; > + case 3: > + DBUG_ASSERT(offset < 0x1fffff); // all 1 value is reserved > + int3store(place, val); > + break; > + case 4: > + DBUG_ASSERT(offset < 0x1fffffff); // all 1 value is reserved > + int4store(place, val); > + break; > + default: > + DBUG_ASSERT(0); // impossible > + } > +} > + > + > +void type_and_offset_read(DYNAMIC_COLUMN_TYPE *type, > + size_t *offset, > + uchar *place, size_t offset_size) > +{ > + ulong val; > + switch (offset_size) { > + case 1: > + val= (ulong)place[0]; > + break; > + case 2: > + val= uint2korr(place); > + break; > + case 3: > + val= uint3korr(place); > + break; > + case 4: > + val= uint4korr(place); > + break; > + default: > + DBUG_ASSERT(0); // impossible > + } > + *type= (val & 0x7) + 1; > + *offset= val >> 3; > +} > + > + > +int column_sort(const void *a, const void *b) > +{ > + return **((uint **)a) - **((uint **)b); > +} > + > +#define FIXED_HEADER_SIZE 5 > + > +my_bool dynamic_new_column_add(DYNAMIC_COLUMN *str, > + size_t header_size, > + size_t offset_size, > + uint column_count, > + uint non_null_count, > + size_t data_size, > + uint *column_numbers, > + DYNAMIC_COLUMN_VALUE *values) > +{ > + uchar *header_end; > + uint **columns_order; > + uint i; > + uint entry_size= 2 + offset_size; > + my_bool err= TRUE; > + bzero(str, sizeof(DYNAMIC_COLUMN)); // just to make dynstr_free() working > + if (!(columns_order= malloc(sizeof(uint*)*column_count))) > + return TRUE; > + if (dynamic_column_init_str(str, > + data_size + header_size + DYNCOL_SYZERESERVE)) > + goto err; > + > + /* sort columns for the header */ > + for (i= 0; i < column_count; i++) > + columns_order[i]= column_numbers + i; > + qsort(columns_order, (size_t)column_count, sizeof(uint*), &column_sort); > + /* check numbers */ -> Change to 'ensure that there is no duplicates' > + for (i= 0; i < column_count - 1; i++) > + if (columns_order[i][0] == columns_order[i+1][0]) > + goto err; > + > + DBUG_ASSERT(str->length == FIXED_HEADER_SIZE); > + str->str[0]|= (offset_size - 1); // size of offset > + int4store(str->str + 1, non_null_count); // columns number Lets limit the number of columns to 65536 (2 bytes) Don't understand why we store non_null_count in header Don't we need to store total number of columns ? I think we should store also null's in the dynamic columns as someone may want to distinguish between a non existing columns and a column with not a set value. We could store this either as an extended type or as datetime with size 0. > + DBUG_ASSERT(str->max_length > str->length + header_size); > + str->length+= header_size; // reserve place for header > + header_end= (uchar *)str->str + FIXED_HEADER_SIZE; > + for (i= 0; i < column_count; i++) > + { > + uint ord= columns_order[i] - column_numbers; > + if (values[ord].type != DYN_COL_NULL) > + { Better to not skip these. > + int2store(header_end, column_numbers[ord]); > + type_and_offset_store(header_end + 2, offset_size, make '2' a define > + values[ord].type, > + str->length - header_size - FIXED_HEADER_SIZE); > + if (data_add(str, values + ord)) > + goto err; Add a note that this can only fail for wrong data, not for memory allocation as everything is already allocated. > + header_end+= entry_size; > + } > + } > + err= FALSE; > +err: > + free(columns_order); > + return err; > +} > + > + > +my_bool dynamic_column_create_many(DYNAMIC_COLUMN *str, > + uint column_count, > + uint *column_numbers, > + DYNAMIC_COLUMN_VALUE *values) > +{ > + size_t data_size= 0; > + size_t header_size, offset_size; > + uint i; > + int not_null_column_count= column_count; > + for (i= 0; i < column_count; i++) > + { > + data_size+= dynamic_column_value_len(values + i); It would be good to store the parts lengths for the values somewhere. Same as for the 'order' parts. One nice way to do this would be to add some 'private' members to the DYANMIC_COLUMN_VALUE struct: uint length[2] /* To store part lengths when packing values */ uint column_number; /* Temp value for column number */ > + if (values[i].type == DYN_COL_NULL) > + not_null_column_count--; > + } > + if ((offset_size= dynamic_column_offset_bytes(data_size)) >= 5) > + { > + /* TODO: error - no more space for data */ > + return TRUE; > + } > + /* header entry is column number + offset&type */ > + header_size= not_null_column_count * (offset_size + 2); > + > + return dynamic_new_column_add(str, > + header_size, offset_size, > + column_count, > + not_null_column_count, > + data_size, > + column_numbers, values); > +} > + > + > +my_bool dynamic_column_create(DYNAMIC_COLUMN *str, uint column_nr, > + DYNAMIC_COLUMN_VALUE *value) > +{ > + return dynamic_column_create_many(str, 1, &column_nr, value); > +} We also need functions: Initialize the DYNAMIC_COLUMN. (Basicly just a call to init_dynamic_string()) > + > +int header_compar(const void *a, const void *b) > +{ > + uint va= uint2korr((uchar*)a), vb= uint2korr((uchar*)b); > + return (va > vb ? 1 : (va < vb ? -1 : 0)); > +} > + /* If the column doesn't exist, *entry_pos contains the place in the header where the data should be stored. */ > +my_bool find_column(DYNAMIC_COLUMN_TYPE *type, uchar **data, size_t *length, > + uchar *header, size_t offset_size, uint column_count, > + uchar *data_end, uint num, uchar **entry_pos) > +{ > + uchar *entry; > + size_t offset, offset_next; > + size_t header_size, entry_size; > + DYNAMIC_COLUMN_TYPE type_next; > + uchar key[2+4]; > + if (!entry_pos) > + entry_pos= &entry; > + > + entry_size= 2 + offset_size; > + header_size= entry_size * column_count; > + int2store(key, num); > + entry= bsearch(key, header, (size_t)column_count, entry_size, > + &header_compar); Change to: uint mid, start, end; int flag; start= 0; end= column_count -1; mid= 1; while (start != end) { uint val; mid= (start + end) / 2; val= uint2korr(header+ mid * entry_size); if ((flag= CMP_NUM(num, val)) >= 0) end= mid; else start= mid+1; } if (start != mid) { val= uint2korr(header+ start * entry_size); flag= CMP_NUM(num, val); } entry= header+ start * entry_size; if (flag < 0) entry+= entry_size; /* Point at next bigger key */ > + if (!entry) This should now be flag != 0 > + { > + *type= DYN_COL_NULL; > + *entry_pos= NULL; > + return FALSE; > + } > + type_and_offset_read(type, &offset, entry + 2, offset_size); > + *data= header + header_size + offset; > + DBUG_ASSERT(*data < data_end); Should not be an assert, but an error condition. Add /* If not last entry */ > + if (entry + entry_size < header + header_size) > + { > + type_and_offset_read(&type_next, &offset_next, entry + entry_size + 2, > + offset_size); > + *length= offset_next - offset; > + } > + else > + *length= data_end - *data; > + *entry_pos= entry; > + return FALSE; > +} > + > +my_bool dynamic_column_get(DYNAMIC_COLUMN *str, int column_nr, > + DYNAMIC_COLUMN_VALUE *store_it_here) > +{ > + uchar *data; > + size_t offset_size, length; > + uint column_count; > + > + if (!str || str->length < FIXED_HEADER_SIZE || > + (str->str[0] & (~DYNCOL_FLG_KNOWN))) > + goto err; Having a length 0 string should be seen as ok. > + > + offset_size= (str->str[0] & DYNCOL_FLG_OFFSET) + 1; > + column_count= uint4korr(str->str + 1); > + > + if (find_column(&store_it_here->type, &data, &length, (uchar*)str->str + 5, > + offset_size, column_count, (uchar*)str->str + str->length, > + column_nr, NULL)) > + goto err; > + > + switch (store_it_here->type) > + { > + case DYN_COL_INT: > + dynamic_column_sint_read(store_it_here, data, length); > + break; > + case DYN_COL_UINT: > + dynamic_column_uint_read(store_it_here, data, length); > + break; > + case DYN_COL_DOUBLE: > + dynamic_column_double_read(store_it_here, data, length); > + break; > + case DYN_COL_STRING: > + dynamic_column_string_read(store_it_here, data, length); > + break; > + case DYN_COL_DECIMAL: > + dynamic_column_decimal_read(store_it_here, data, length); > + break; > + case DYN_COL_DATETIME: > + dynamic_column_date_time_read(store_it_here, data, length); > + break; > + case DYN_COL_DATE: > + dynamic_column_date_read(store_it_here, data, length); > + break; > + case DYN_COL_TIME: > + dynamic_column_time_read(store_it_here, data, length); > + break; > + case DYN_COL_NULL: > + break; > + default: > + goto err; > + } > + return FALSE; > + > +err: > + store_it_here->type= DYN_COL_NULL; Wouldn't it be better to set: store_it_here->type= DYN_COL_ERROR; > + return TRUE; > +} > + > + > +void dynamic_column_value_free(DYNAMIC_COLUMN_VALUE *value) > +{ > + switch (value->type) > + { > + case DYN_COL_INT: > + case DYN_COL_UINT: > + case DYN_COL_DOUBLE: > + case DYN_COL_DECIMAL: > + case DYN_COL_DATETIME: > + case DYN_COL_DATE: > + case DYN_COL_TIME: > + case DYN_COL_NULL: > + break; // no need cleanup; > + case DYN_COL_STRING: > + free(value->string_value.str); No need for the above as we will point directly to the data. > + value->string_value.str= NULL; //just to be safe > + value->type= DYN_COL_NULL; > + break; > + default: > + DBUG_ASSERT(0); > + } > +} > + > + For this one we proably need a couple of different return values: -1 wrong data in DYNAMIC_COLUMN 0 Column was not part of data 1 Column was part of data and is now deleted. > +my_bool dynamic_column_delete(DYNAMIC_COLUMN *str, uint column_nr) > +{ > + uchar *data, *header_entry, *read, *write; > + size_t offset_size, new_offset_size, length, entry_size, new_entry_size, > + header_size, new_header_size, data_size, new_data_size, > + deleted_entry_offset; > + uint column_count, i; > + DYNAMIC_COLUMN_TYPE type; > + > + if (!str || str->length < FIXED_HEADER_SIZE || > + (str->str[0] & (~DYNCOL_FLG_KNOWN))) > + return TRUE; > + > + offset_size= (str->str[0] & DYNCOL_FLG_OFFSET) + 1; > + column_count= uint4korr(str->str + 1); > + > + if (column_count == 0) > + return FALSE; // no columns > + > + if (find_column(&type, &data, &length, (uchar*)str->str + 5, > + offset_size, column_count, (uchar*)str->str + str->length, > + column_nr, &header_entry)) > + return TRUE; We need to have find_column to have different return values for wrong data, did not find it, found it. With this we can do the above as: if ((res= find_column()) <= 0) return res; > + > + if (type == DYN_COL_NULL) > + return FALSE; // no such column Which allows us to skip the above. > + if (column_count == 1) > + { > + /* delete the only column */ > + str->length= FIXED_HEADER_SIZE; > + bzero(str->str, FIXED_HEADER_SIZE); > + return FALSE; Better to make the string 0 size. > + } > + > + entry_size= 2 + offset_size; > + header_size= entry_size * column_count; > + data_size= str->length - FIXED_HEADER_SIZE - header_size; > + > + new_data_size= data_size - length; > + new_offset_size= dynamic_column_offset_bytes(new_data_size); > + DBUG_ASSERT(new_offset_size <= offset_size); > + new_entry_size= 2 + new_offset_size; > + new_header_size= new_entry_size * (column_count - 1); > + > + deleted_entry_offset= (data - (uchar*)str->str) - > + header_size - FIXED_HEADER_SIZE; > + > + > + /* rewrite header*/ > + str->str[0]|= (new_offset_size - 1); // size of offset > + int4store(str->str + 1, column_count - 1); // columns number > + for (i= 0, write= read= (uchar *)str->str + FIXED_HEADER_SIZE; > + i < column_count; > + i++, read+= entry_size, write+= new_entry_size) > + { > + size_t offs; > + uint nm; > + DYNAMIC_COLUMN_TYPE tp; > + if (read == header_entry) > + { > +#ifndef DBUG_OFF > + nm= uint2korr(read); > + type_and_offset_read(&tp, &offs, read + 2, > + offset_size); > + DBUG_ASSERT(nm == column_nr); > + DBUG_ASSERT(offs == deleted_entry_offset); > +#endif > + write-= new_entry_size; // do not move writer > + continue; // skip removed field > + } > + > + nm= uint2korr(read), > + type_and_offset_read(&tp, &offs, read + 2, > + offset_size); > + > + if (offs > deleted_entry_offset) > + offs-= length; // data stored after removed data > + > + int2store(write, nm); > + type_and_offset_store(write + 2, new_offset_size, tp, offs); > + } Please optimize that if new_offset_size == old_offset_size then we should start from header_entry. You should also make the above a function as update also needs to do this! > + > + /* move data */ > + { > + size_t first_chunk_len= (data - (uchar *)str->str) - > + FIXED_HEADER_SIZE - header_size; > + size_t second_chunk_len= new_data_size - first_chunk_len; > + if (first_chunk_len) > + memmove(str->str + FIXED_HEADER_SIZE + new_header_size, > + str->str + FIXED_HEADER_SIZE + header_size, > + first_chunk_len); > + if (second_chunk_len) > + memmove(str->str + > + FIXED_HEADER_SIZE + new_header_size + first_chunk_len, > + str->str + > + FIXED_HEADER_SIZE + header_size + first_chunk_len + length, > + second_chunk_len); > + } > + > + /* fix str length */ > + DBUG_ASSERT(str->length >= > + FIXED_HEADER_SIZE + new_header_size + new_data_size); > + str->length= FIXED_HEADER_SIZE + new_header_size + new_data_size; > + > + return FALSE; > +} > + > + > +my_bool dynamic_column_update(DYNAMIC_COLUMN *str, uint column_nr, > + DYNAMIC_COLUMN_VALUE *value) > +{ > + size_t offset_size, new_offset_size, data_size, new_data_size, > + add_data_size, entry_size, new_entry_size, > + header_size, new_header_size, additional_size, next_offs, > + data_ins_offset; > + uint column_count, i; > + uchar *read, *write; > + my_bool added; > + > + /* TODO: optimize update without deleting */ > + if (dynamic_column_delete(str, column_nr)) > + return TRUE; The problem with doing delete + insert later is that the whole function needs to be rewritten and you can't use any of the old code (for columns that exists). So I suggest you write this ASAP! > + > + if (value->type == DYN_COL_NULL) > + return FALSE; Should be stored. > + > + if (!str || str->length < FIXED_HEADER_SIZE || > + (str->str[0] & (~DYNCOL_FLG_KNOWN))) > + return TRUE; length of 0 should be regarded as ok. > + offset_size= (str->str[0] & DYNCOL_FLG_OFFSET) + 1; > + column_count= uint4korr(str->str + 1); > + > + add_data_size= dynamic_column_value_len(value); > + > + if (column_count == 0) > + { > + /* offset size of one record could be minimal */ > + return dynamic_new_column_add(str, 1 * (1 + 2), 1, 1, 1, > + new_data_size, &column_nr, value); > + } > + > + entry_size= 2 + offset_size; > + header_size= entry_size * column_count; > + data_size= str->length - FIXED_HEADER_SIZE - header_size; > + > + new_data_size= data_size + add_data_size; > + new_offset_size= dynamic_column_offset_bytes(new_data_size); > + DBUG_ASSERT(new_offset_size >= offset_size); > + new_entry_size= 2 + new_offset_size; > + new_header_size= new_entry_size * (column_count + 1); > + > + additional_size= add_data_size + (new_header_size - header_size); > + > + if (dynstr_realloc(str, additional_size)) > + return TRUE; > + > + /* move data to the string end */ > + str->length+= additional_size; > + memmove(str->str + FIXED_HEADER_SIZE + new_header_size + add_data_size, > + str->str + FIXED_HEADER_SIZE + header_size, > + data_size); Data should be placed on it's right position, not at end! You can do now do that with find_column() ! > + /* rewrite header */ > + next_offs= str->length - FIXED_HEADER_SIZE - new_header_size; > + for (i= column_count, > + read= (uchar *)str->str + FIXED_HEADER_SIZE + header_size - entry_size, > + write= ((uchar *)str->str + FIXED_HEADER_SIZE + > + (new_entry_size * column_count)); > + i > 0; > + i--, read-= entry_size, write-= new_entry_size) > + { > + size_t offs; > + uint nm; > + DYNAMIC_COLUMN_TYPE tp; > + > + nm= uint2korr(read); > + type_and_offset_read(&tp, &offs, read + 2, offset_size); > + > + if (!added && column_nr > nm) > + { > + /* place to put the new column */ > + int2store(write, column_nr); > + type_and_offset_store(write + 2, new_offset_size, > + value->type, > + (data_ins_offset= next_offs - add_data_size)); > + /* move previous data */ > + memmove(str->str + FIXED_HEADER_SIZE + new_header_size, > + str->str + FIXED_HEADER_SIZE + new_header_size + add_data_size, > + next_offs - add_data_size); > + added= TRUE; > + write-= new_entry_size; > + } > + int2store(write, nm); > + if (!added) > + offs+= add_data_size; > + type_and_offset_store(write + 2, new_offset_size, tp, offs); > + next_offs= offs; > + } We should just have one function to rewrite the headers! To make life easer, maybe we should assume that header size change operation is a very unlikely one and accept to do an extra memmove when header offset changes? This would allow us to have a simple function that just rewrites the header (from a given point) and another that increases/decreases the header size + all data ? Then all operations are basicly: - If offset_pointer_size changes, fix data - Add / remove things from header and data (with new offset size) - Update header The whole things above would then be very trivial: - realloc str->length if it needs to grow - If offset_pointer_size changes, fix data and update entry_pos - Update data (and create new header entry last) - memmove(entry, entry + entry_size, header_end - entry); - Write data at entry > + if (!added) > + { > + /* put the new column before others */ > + int2store(write, column_nr); > + type_and_offset_store(write + 2, new_offset_size, > + value->type, (data_ins_offset= 0)); > + } > + str->str[0]|= (new_offset_size - 1); // size of offset > + int4store(str->str + 1, column_count + 1); // columns number > + > + { > + /* insert data */ > + size_t save_len= str->length; > + str->length= data_ins_offset + FIXED_HEADER_SIZE + new_header_size; > + if (data_add(str, value)) > + return TRUE; > + str->length= save_len; > + } > + > + return FALSE; > +} > + > + > +my_bool dynamic_column_exists(DYNAMIC_COLUMN *str, uint column_nr) > +{ > + uchar *data; > + size_t offset_size, length; > + uint column_count; > + DYNAMIC_COLUMN_TYPE type; > + > + if (!str || str->length < FIXED_HEADER_SIZE || > + (str->str[0] & (~DYNCOL_FLG_KNOWN))) > + return TRUE; length 0 should return FALSE > + > + offset_size= (str->str[0] & DYNCOL_FLG_OFFSET) + 1; > + column_count= uint4korr(str->str + 1); > + > + if (column_count == 0) > + return FALSE; // no columns > + > + if (find_column(&type, &data, &length, (uchar*)str->str + 5, > + offset_size, column_count, (uchar*)str->str + str->length, > + column_nr, NULL)) > + return FALSE; // error but we can't report it > + > + return type != DYN_COL_NULL; > +} > + > +my_bool dynamic_column_list(DYNAMIC_COLUMN *str, DYNAMIC_ARRAY *array_of_uint) > +{ > + uchar *read; > + size_t offset_size, entry_size; > + uint column_count, i; > + > + if (!str || str->length < FIXED_HEADER_SIZE || > + (str->str[0] & (~DYNCOL_FLG_KNOWN))) > + return TRUE; > + > + offset_size= (str->str[0] & DYNCOL_FLG_OFFSET) + 1; > + column_count= uint4korr(str->str + 1); > + entry_size= 2 + offset_size; > + > + if (init_dynamic_array(array_of_uint, sizeof(uint), > + column_count, 10 CALLER_INFO)) > + return TRUE; -> my_init_dynamic_array2(array_of_uint, sizeof(uint), NULL, column_count,0) > + > + for (i= 0, read= (uchar *)str->str + FIXED_HEADER_SIZE; > + i < column_count; > + i++, read+= entry_size) > + { > + uint nm= uint2korr(read); > + if (insert_dynamic(array_of_uint, (uchar *)&nm)) > + { > + delete_dynamic(array_of_uint); > + return TRUE; > + } > + } > + return FALSE; > +} > === modified file 'sql/my_decimal.h' > --- sql/my_decimal.h 2010-11-24 22:57:34 +0000 > +++ sql/my_decimal.h 2011-03-24 16:30:27 +0000 > @@ -32,32 +32,7 @@ > #include <decimal.h> > C_MODE_END > -#define DECIMAL_LONGLONG_DIGITS 22 > -#define DECIMAL_LONG_DIGITS 10 > -#define DECIMAL_LONG3_DIGITS 8 > - > -/** maximum length of buffer in our big digits (uint32). */ > -#define DECIMAL_BUFF_LENGTH 9 > - > -/* the number of digits that my_decimal can possibly contain */ > -#define DECIMAL_MAX_POSSIBLE_PRECISION (DECIMAL_BUFF_LENGTH * 9) > - > - > -/** > - maximum guaranteed precision of number in decimal digits (number of our > - digits * number of decimal digits in one our big digit - number of decimal > - digits in one our big digit decreased by 1 (because we always put decimal > - point on the border of our big digits)) > -*/ > -#define DECIMAL_MAX_PRECISION (DECIMAL_MAX_POSSIBLE_PRECISION - 8*2) > -#define DECIMAL_MAX_SCALE 30 > -#define DECIMAL_NOT_SPECIFIED 31 > - > -/** > - maximum length of string representation (number of maximum decimal > - digits + 1 position for sign + 1 position for decimal point) > -*/ > -#define DECIMAL_MAX_STR_LENGTH (DECIMAL_MAX_POSSIBLE_PRECISION + 2) > +#include <my_decimal_limits.h> > /** > maximum size of packet length. > === modified file 'unittest/mysys/Makefile.am' > --- unittest/mysys/Makefile.am 2010-11-30 21:11:03 +0000 > +++ unittest/mysys/Makefile.am 2011-03-25 07:46:32 +0000 > @@ -25,4 +25,4 @@ > EXTRA_DIST = CMakeLists.txt > noinst_PROGRAMS = bitmap-t base64-t my_atomic-t lf-t waiting_threads-t \ > - my_vsnprintf-t > + my_vsnprintf-t ma_dyncol-t > === added file 'unittest/mysys/ma_dyncol-t.c' > --- unittest/mysys/ma_dyncol-t.c 1970-01-01 00:00:00 +0000 > +++ unittest/mysys/ma_dyncol-t.c 2011-03-27 22:53:44 +0000 > @@ -0,0 +1,690 @@ > +#include <my_global.h> > +#include <ma_dyncol.h> > +#include <tap.h> > + > + > + > +void test_value_single_null() > +{ > + int rc= FALSE; > + DYNAMIC_COLUMN_VALUE val, res; > + DYNAMIC_COLUMN str; > + /* init values */ > + val.type= DYN_COL_NULL; > + dynamic_column_value_init(&res); > + /* create column */ > + if (dynamic_column_create(&str, 1, &val)) > + goto err; > + dynstr_append(&str, "\1"); str.length--; //check for overflow > + /* read column */ > + if (dynamic_column_get(&str, 1, &res)) > + goto err; > + rc= (res.type == DYN_COL_NULL); > +err: > + ok(rc, "%s", "NULL"); > + /* cleanup */ > + dynamic_column_column_free(&str); > + dynamic_column_value_free(&val); > + dynamic_column_value_free(&res); > +} > + > +void test_value_single_uint(ulonglong num, const char *name) > +{ > + int rc= FALSE; > + DYNAMIC_COLUMN_VALUE val, res; > + DYNAMIC_COLUMN str; > + /* init values */ > + val.type= DYN_COL_UINT; > + val.ulong_value= num; > + dynamic_column_value_init(&res); > + /* create column */ > + if (dynamic_column_create(&str, 1, &val)) > + goto err; > + dynstr_append(&str, "\1"); str.length--; //check for overflow > + /* read column */ > + if (dynamic_column_get(&str, 1, &res)) > + goto err; > + rc= (res.type == DYN_COL_UINT) && (res.ulong_value == num); > + num= res.ulong_value; > +err: > + ok(rc, "%s - %llu", name, num); > + /* cleanup */ > + dynamic_column_column_free(&str); > + dynamic_column_value_free(&val); > + dynamic_column_value_free(&res); > +} > + > +void test_value_single_sint(longlong num, const char *name) > +{ > + int rc= FALSE; > + DYNAMIC_COLUMN_VALUE val, res; > + DYNAMIC_COLUMN str; > + /* init values */ > + val.type= DYN_COL_INT; > + val.long_value= num; > + dynamic_column_value_init(&res); > + /* create column */ > + if (dynamic_column_create(&str, 1, &val)) > + goto err; > + dynstr_append(&str, "\1"); str.length--; //check for overflow > + /* read column */ > + if (dynamic_column_get(&str, 1, &res)) > + goto err; > + rc= (res.type == DYN_COL_INT) && (res.long_value == num); > + num= res.ulong_value; > +err: > + ok(rc, "%s - %lld", name, num); > + /* cleanup */ > + dynamic_column_column_free(&str); > + dynamic_column_value_free(&val); > + dynamic_column_value_free(&res); > +} > + > + > +void test_value_single_double(double num, const char *name) > +{ > + int rc= FALSE; > + DYNAMIC_COLUMN_VALUE val, res; > + DYNAMIC_COLUMN str; > + /* init values */ > + val.type= DYN_COL_DOUBLE; > + val.double_value= num; > + dynamic_column_value_init(&res); > + /* create column */ > + if (dynamic_column_create(&str, 1, &val)) > + goto err; > + dynstr_append(&str, "\1"); str.length--; //check for overflow > + /* read column */ > + if (dynamic_column_get(&str, 1, &res)) > + goto err; > + rc= (res.type == DYN_COL_DOUBLE) && (res.double_value == num); > + num= res.ulong_value; > +err: > + ok(rc, "%s - %lf", name, num); > + /* cleanup */ > + dynamic_column_column_free(&str); > + dynamic_column_value_free(&val); > + dynamic_column_value_free(&res); > +} > + > +void test_value_single_decimal(const char *num) > +{ > + char *end= (((char*)num) + strlen(num)); > + char buff[80]; > + int rc= FALSE; > + int length= 80; > + DYNAMIC_COLUMN_VALUE val, res; > + DYNAMIC_COLUMN str; > + > + /* init values */ > + dynamic_column_prepare_decimal(&val); // special procedure for decimal!!! > + if (string2decimal(num, &val.decimal_value, &end) != E_DEC_OK) > + goto err; > + dynamic_column_value_init(&res); > + > + /* create column */ > + if (dynamic_column_create(&str, 1, &val)) > + goto err; > + dynstr_append(&str, "\1"); str.length--; //check for overflow > + /* read column */ > + if (dynamic_column_get(&str, 1, &res)) > + goto err; > + rc= ((res.type == DYN_COL_DECIMAL) && > + (decimal_cmp(&res.decimal_value, &val.decimal_value) == 0)); > + decimal2string(&res.decimal_value, buff, &length, 0, 0, ' '); > +err: > + ok(rc, "%s - %s", num, buff); > + /* cleanup */ > + dynamic_column_column_free(&str); > + dynamic_column_value_free(&val); > + dynamic_column_value_free(&res); > +} > + > +static CHARSET_INFO *charset_list[]= > +{ > +#ifdef HAVE_CHARSET_big5 > + &my_charset_big5_chinese_ci, > + &my_charset_big5_bin, > +#endif > +#ifdef HAVE_CHARSET_euckr > + &my_charset_euckr_korean_ci, > + &my_charset_euckr_bin, > +#endif > +#ifdef HAVE_CHARSET_gb2312 > + &my_charset_gb2312_chinese_ci, > + &my_charset_gb2312_bin, > +#endif > +#ifdef HAVE_CHARSET_gbk > + &my_charset_gbk_chinese_ci, > + &my_charset_gbk_bin, > +#endif > +#ifdef HAVE_CHARSET_latin1 > + &my_charset_latin1, > + &my_charset_latin1_bin, > +#endif > +#ifdef HAVE_CHARSET_sjis > + &my_charset_sjis_japanese_ci, > + &my_charset_sjis_bin, > +#endif > +#ifdef HAVE_CHARSET_tis620 > + &my_charset_tis620_thai_ci, > + &my_charset_tis620_bin, > +#endif > +#ifdef HAVE_CHARSET_ujis > + &my_charset_ujis_japanese_ci, > + &my_charset_ujis_bin, > +#endif > +#ifdef HAVE_CHARSET_utf8 > + &my_charset_utf8_general_ci, > +#ifdef HAVE_HAVE_UCA_COLLATIONS > + &my_charset_utf8_unicode_ci, > +#endif > + &my_charset_utf8_bin, > +#endif > +}; > + > + > +void test_value_single_string(const char *string, size_t len, > + CHARSET_INFO *cs) > +{ > + int rc= FALSE; > + DYNAMIC_COLUMN_VALUE val, res; > + DYNAMIC_COLUMN str; > + > + /* init values */ > + val.type= DYN_COL_STRING; > + val.string_value.str= (char*)string; > + val.string_value.length= len; > + val.charset= cs; > + dynamic_column_value_init(&res); > + > + /* create column */ > + if (dynamic_column_create(&str, 1, &val)) > + goto err; > + dynstr_append(&str, "\1"); str.length--; //check for overflow > + /* read column */ > + if (dynamic_column_get(&str, 1, &res)) > + goto err; > + rc= ((res.type == DYN_COL_STRING) && > + (res.string_value.length == len) && > + (memcmp(res.string_value.str, string, len) == 0) && > + (res.charset->number == cs->number)); > +err: > + ok(rc, "'%s' - '%s' %u %u-%s", string, > + res.string_value.str, (uint)res.string_value.length, > + (uint)res.charset->number, res.charset->name); > + /* cleanup */ > + val.string_value.str= NULL; // we did not allocated it > + dynamic_column_column_free(&str); > + dynamic_column_value_free(&val); > + dynamic_column_value_free(&res); > +} > + > +void test_value_single_date(uint year, uint month, uint day, const char *name) > +{ > + int rc= FALSE; > + DYNAMIC_COLUMN_VALUE val, res; > + DYNAMIC_COLUMN str; > + /* init values */ > + val.type= DYN_COL_DATE; > + val.time_value.time_type= MYSQL_TIMESTAMP_DATE; > + val.time_value.year= year; > + val.time_value.month= month; > + val.time_value.day= day; > + dynamic_column_value_init(&res); > + /* create column */ > + if (dynamic_column_create(&str, 1, &val)) > + goto err; > + dynstr_append(&str, "\1"); str.length--; //check for overflow > + /* read column */ > + if (dynamic_column_get(&str, 1, &res)) > + goto err; > + rc= ((res.type == DYN_COL_DATE) && > + (res.time_value.time_type == MYSQL_TIMESTAMP_DATE) && > + (res.time_value.year == year) && > + (res.time_value.month == month) && > + (res.time_value.day == day)); > +err: > + ok(rc, "%s - %04u-%02u-%02u", name, year, month, day); > + /* cleanup */ > + dynamic_column_column_free(&str); > + dynamic_column_value_free(&val); > + dynamic_column_value_free(&res); > +} > + > +void test_value_single_time(uint neg, uint hour, uint minute, uint second, > + uint mic, const char *name) > +{ > + int rc= FALSE; > + DYNAMIC_COLUMN_VALUE val, res; > + DYNAMIC_COLUMN str; > + /* init values */ > + val.type= DYN_COL_TIME; > + val.time_value.time_type= MYSQL_TIMESTAMP_TIME; > + val.time_value.neg= neg; > + val.time_value.hour= hour; > + val.time_value.minute= minute; > + val.time_value.second= second; > + val.time_value.second_part= mic; > + dynamic_column_value_init(&res); > + /* create column */ > + if (dynamic_column_create(&str, 1, &val)) > + goto err; > + dynstr_append(&str, "\1"); str.length--; //check for overflow > + /* read column */ > + if (dynamic_column_get(&str, 1, &res)) > + goto err; > + rc= ((res.type == DYN_COL_TIME) && > + (res.time_value.time_type == MYSQL_TIMESTAMP_TIME) && > + (res.time_value.neg == (int)neg) && > + (res.time_value.hour == hour) && > + (res.time_value.minute == minute) && > + (res.time_value.second == second) && > + (res.time_value.second_part == mic)); > +err: > + ok(rc, "%s - %c%02u:%02u:%02u.%06u", name, (neg ? '-' : '+'), > + hour, minute, second, mic); > + /* cleanup */ > + dynamic_column_column_free(&str); > + dynamic_column_value_free(&val); > + dynamic_column_value_free(&res); > +} > + > + > +void test_value_single_datetime(uint neg, uint year, uint month, uint day, > + uint hour, uint minute, uint second, > + uint mic, const char *name) > +{ > + int rc= FALSE; > + DYNAMIC_COLUMN_VALUE val, res; > + DYNAMIC_COLUMN str; > + /* init values */ > + val.type= DYN_COL_DATETIME; > + val.time_value.time_type= MYSQL_TIMESTAMP_DATETIME; > + val.time_value.neg= neg; > + val.time_value.year= year; > + val.time_value.month= month; > + val.time_value.day= day; > + val.time_value.hour= hour; > + val.time_value.minute= minute; > + val.time_value.second= second; > + val.time_value.second_part= mic; > + dynamic_column_value_init(&res); > + /* create column */ > + if (dynamic_column_create(&str, 1, &val)) > + goto err; > + dynstr_append(&str, "\1"); str.length--; //check for overflow > + /* read column */ > + if (dynamic_column_get(&str, 1, &res)) > + goto err; > + rc= ((res.type == DYN_COL_DATETIME) && > + (res.time_value.time_type == MYSQL_TIMESTAMP_DATETIME) && > + (res.time_value.neg == (int)neg) && > + (res.time_value.year == year) && > + (res.time_value.month == month) && > + (res.time_value.day == day) && > + (res.time_value.hour == hour) && > + (res.time_value.minute == minute) && > + (res.time_value.second == second) && > + (res.time_value.second_part == mic)); > +err: > + ok(rc, "%s - %c %04u-%02u-%02u %02u:%02u:%02u.%06u", name, (neg ? '-' : '+'), > + year, month, day, hour, minute, second, mic); > + /* cleanup */ > + dynamic_column_column_free(&str); > + dynamic_column_value_free(&val); > + dynamic_column_value_free(&res); > +} > + > + > +void test_value_multi(ulonglong num0, > + longlong num1, > + double num2, > + const char *num3, > + const char *string4, size_t len4, CHARSET_INFO *cs4, > + uint year5, uint month5, uint day5, > + uint neg6, uint hour6, uint minute6, > + uint second6, uint mic6, > + uint neg7, uint year7, uint month7, uint day7, > + uint hour7, uint minute7, uint second7, > + uint mic7, > + uint *column_numbers, > + const char *name) > +{ > + char *end3= (((char*)num3) + strlen(num3)); > + int rc= FALSE; > + uint i; > + DYNAMIC_COLUMN_VALUE val[9], res[9]; > + DYNAMIC_COLUMN str; > + /* init values */ > + val[0].type= DYN_COL_UINT; > + val[0].ulong_value= num0; > + val[1].type= DYN_COL_INT; > + val[1].long_value= num1; > + val[2].type= DYN_COL_DOUBLE; > + val[2].double_value= num2; > + dynamic_column_prepare_decimal(val + 3); // special procedure for decimal!!! > + if (string2decimal(num3, &val[3].decimal_value, &end3) != E_DEC_OK) > + goto err; > + val[4].type= DYN_COL_STRING; > + val[4].string_value.str= (char*)string4; > + val[4].string_value.length= len4; > + val[4].charset= cs4; > + val[5].type= DYN_COL_DATE; > + val[5].time_value.time_type= MYSQL_TIMESTAMP_DATE; > + val[5].time_value.year= year5; > + val[5].time_value.month= month5; > + val[5].time_value.day= day5; > + val[6].type= DYN_COL_TIME; > + val[6].time_value.time_type= MYSQL_TIMESTAMP_TIME; > + val[6].time_value.neg= neg6; > + val[6].time_value.hour= hour6; > + val[6].time_value.minute= minute6; > + val[6].time_value.second= second6; > + val[6].time_value.second_part= mic6; > + val[7].type= DYN_COL_DATETIME; > + val[7].time_value.time_type= MYSQL_TIMESTAMP_DATETIME; > + val[7].time_value.neg= neg7; > + val[7].time_value.year= year7; > + val[7].time_value.month= month7; > + val[7].time_value.day= day7; > + val[7].time_value.hour= hour7; > + val[7].time_value.minute= minute7; > + val[7].time_value.second= second7; > + val[7].time_value.second_part= mic7; > + val[8].type= DYN_COL_NULL; > + for (i= 0; i < 9; i++) > + dynamic_column_value_init(res + i); > + /* create column */ > + if (dynamic_column_create_many(&str, 9, column_numbers, val)) > + goto err; > + dynstr_append(&str, "\1"); str.length--; //check for overflow > + /* read column */ > + for (i= 0; i < 9; i++) > + if (dynamic_column_get(&str, column_numbers[i], res + i)) > + goto err; > + rc= ((res[0].type == DYN_COL_UINT) && > + (res[0].ulong_value == num0) && > + (res[1].type == DYN_COL_INT) && > + (res[1].long_value == num1) && > + (res[2].type == DYN_COL_DOUBLE) && > + (res[2].double_value == num2) && > + (res[3].type == DYN_COL_DECIMAL) && > + (decimal_cmp(&res[3].decimal_value, &val[3].decimal_value) == 0) && > + (res[4].type == DYN_COL_STRING) && > + (res[4].string_value.length == len4) && > + (memcmp(res[4].string_value.str, string4, len4) == 0) && > + (res[4].charset->number == cs4->number) && > + (res[5].type == DYN_COL_DATE) && > + (res[5].time_value.time_type == MYSQL_TIMESTAMP_DATE) && > + (res[5].time_value.year == year5) && > + (res[5].time_value.month == month5) && > + (res[5].time_value.day == day5) && > + (res[6].type == DYN_COL_TIME) && > + (res[6].time_value.time_type == MYSQL_TIMESTAMP_TIME) && > + (res[6].time_value.neg == (int)neg6) && > + (res[6].time_value.hour == hour6) && > + (res[6].time_value.minute == minute6) && > + (res[6].time_value.second == second6) && > + (res[6].time_value.second_part == mic6) && > + (res[7].type == DYN_COL_DATETIME) && > + (res[7].time_value.time_type == MYSQL_TIMESTAMP_DATETIME) && > + (res[7].time_value.neg == (int)neg7) && > + (res[7].time_value.year == year7) && > + (res[7].time_value.month == month7) && > + (res[7].time_value.day == day7) && > + (res[7].time_value.hour == hour7) && > + (res[7].time_value.minute == minute7) && > + (res[7].time_value.second == second7) && > + (res[7].time_value.second_part == mic7) && > + (res[8].type == DYN_COL_NULL)); > +err: > + ok(rc, "%s", name); > + /* cleanup */ > + val[4].string_value.str= NULL; // we did not allocated it > + dynamic_column_column_free(&str); > + for (i= 0; i < 9; i++) > + { > + dynamic_column_value_free(val + i); > + dynamic_column_value_free(res + i); > + } > +} > + > + > +void test_value_multi_same_num() > +{ > + int rc= FALSE; > + uint i; > + DYNAMIC_COLUMN_VALUE val[5]; > + uint column_numbers[]= {3,4,5,3,6}; // same column numbers > + DYNAMIC_COLUMN str; > + /* init values */ > + for (i= 0; i < 5; i++) > + val[i].type= DYN_COL_NULL; > + /* create column */ > + if (!dynamic_column_create_many(&str, 5, column_numbers, val)) > + goto err; > + rc= TRUE; > +err: > + ok(rc, "%s", "same column numbers check"); > + /* cleanup */ > + dynamic_column_column_free(&str); > + for (i= 0; i < 5; i++) > + dynamic_column_value_free(val + i); > +} > + > + > +void test_update_multi(uint *column_numbers, uint *column_values, > + my_bool *null_values, int only_add, int all) > +{ > + int rc= FALSE; > + int i, j; > + DYNAMIC_COLUMN str; > + DYNAMIC_COLUMN_VALUE val; > + > + val.type= DYN_COL_UINT; > + val.ulong_value= column_values[0]; > + if (dynamic_column_create(&str, column_numbers[0], &val)) > + goto err; > + dynamic_column_value_free(&val); > + for (i= 1; i < all; i++) > + { > + val.type= (null_values[i] ? DYN_COL_NULL : DYN_COL_UINT); > + val.ulong_value= column_values[i]; > + if (dynamic_column_update(&str, column_numbers[i], &val)) > + goto err; > + dynamic_column_value_free(&val); > + > + /* check value(s) */ > + for (j= i; j >= (i < only_add ? 0 : i); j--) > + { > + if (dynamic_column_get(&str, column_numbers[j], &val)) > + goto err; > + if (null_values[j]) > + { > + if (val.type != DYN_COL_NULL || > + dynamic_column_exists(&str, column_numbers[j])) > + goto err; > + } > + else > + { > + if (val.type != DYN_COL_UINT || > + val.ulong_value != column_values[j] || > + !dynamic_column_exists(&str, column_numbers[j])) > + goto err; > + } > + dynamic_column_value_free(&val); > + } > + if (i < only_add) > + { > + DYNAMIC_ARRAY num; > + if (dynamic_column_list(&str, &num)) > + goto err; > + /* cross check arrays */ > + if ((int)num.elements != i + 1) > + { > + delete_dynamic(&num); > + goto err; > + } > + for(j= 0; j < i + 1; j++) > + { > + int k; > + for(k= 0; > + k < i + 1 && column_numbers[j] != > + *dynamic_element(&num, k, uint*); > + k++); > + if (k >= i + 1) > + { > + delete_dynamic(&num); > + goto err; > + } > + for(k= 0; > + k < i + 1 && column_numbers[k] != > + *dynamic_element(&num, j, uint*); > + k++); > + if (k >= i + 1) > + { > + delete_dynamic(&num); > + goto err; > + } > + } > + delete_dynamic(&num); > + } > + } > + > + rc= TRUE; > +err: > + ok(rc, "%s", "add/delete/update"); > + /* cleanup */ > + dynamic_column_column_free(&str); > + dynamic_column_value_free(&val); > +} > + > + > +int main(int argc __attribute__((unused)), char **argv) > +{ > + uint i; > + MY_INIT(argv[0]); > + plan(53); > + char *big_string= malloc(1024*1024); > + if (!big_string) > + exit(1); > + for (i= 0; i < 1024*1024; i++) > + big_string[i]= ('0' + (i % 10)); > + test_value_single_null(); > + test_value_single_uint(0, "0"); > + test_value_single_uint(0xffffffffffffffff, "0xffffffffffffffff"); > + test_value_single_uint(0xaaaaaaaaaaaaaaaa, "0xaaaaaaaaaaaaaaaa"); > + test_value_single_uint(0x5555555555555555, "0x5555555555555555"); > + test_value_single_uint(27652, "27652"); > + test_value_single_sint(0, "0"); > + test_value_single_sint(1, "1"); > + test_value_single_sint(-1, "-1"); > + test_value_single_sint((longlong)0x7fffffffffffffff, > + "0x7fffffffffffffff"); > + test_value_single_sint((longlong)0xaaaaaaaaaaaaaaaa, > + "0xaaaaaaaaaaaaaaaa"); > + test_value_single_sint((longlong)0x5555555555555555, > + "0x5555555555555555"); > + test_value_single_sint((longlong)0x8000000000000000, > + "0x8000000000000000"); > + test_value_single_double(0.0, "0.0"); > + test_value_single_double(1.0, "1.0"); > + test_value_single_double(-1.0, "-1.0"); > + test_value_single_double(1.0e100, "1.0e100"); > + test_value_single_double(1.0e-100, "1.0e-100"); > + test_value_single_double(9999999999999999999999999999999999999.0, > + "9999999999999999999999999999999999999.0"); > + test_value_single_double(-9999999999999999999999999999999999999.0, > + "-9999999999999999999999999999999999999.0"); > + test_value_single_decimal("0"); > + test_value_single_decimal("1"); > + test_value_single_decimal("-1"); > + test_value_single_decimal("9999999999999999999999999999999"); > + test_value_single_decimal("-9999999999999999999999999999999"); > + test_value_single_decimal("0.9999999999999999999999999999999"); > + test_value_single_decimal("-0.9999999999999999999999999999999"); > + test_value_single_string("", 0, charset_list[0]); > + test_value_single_string("1234567890", 10, charset_list[0]); > + test_value_single_string("nulls\0\0\0\0\0", 10, charset_list[0]); > + sprintf(big_string, "%x", 0x7a); > + test_value_single_string(big_string, 0x7a, charset_list[0]); > + sprintf(big_string, "%x", 0x80); > + test_value_single_string(big_string, 0x80, charset_list[0]); > + sprintf(big_string, "%x", 0x7ffa); > + test_value_single_string(big_string, 0x7ffa, charset_list[0]); > + sprintf(big_string, "%x", 0x8000); > + test_value_single_string(big_string, 0x8000, charset_list[0]); > + sprintf(big_string, "%x", 1024*1024); > + test_value_single_string(big_string, 1024*1024, charset_list[0]); > + free(big_string); > + test_value_single_date(0, 0, 0, "zero date"); > + test_value_single_date(9999, 12, 31, "max date"); > + test_value_single_date(2011, 3, 26, "some date"); > + test_value_single_time(0, 0, 0, 0, 0, "zero time"); > + test_value_single_time(1, 23, 59, 59, 999999, "min time"); > + test_value_single_time(0, 23, 59, 59, 999999, "max time"); > + test_value_single_time(0, 21, 36, 20, 28, "some time"); > + test_value_single_datetime(0, 0, 0, 0, 0, 0, 0, 0, "zero datetime"); > + test_value_single_datetime(1, 9999, 12, 31, 23, 59, 59, 999999, > + "min datetime"); > + test_value_single_datetime(0, 9999, 12, 31, 23, 59, 59, 999999, > + "max datetime"); > + test_value_single_datetime(0, 2011, 3, 26, 21, 53, 12, 3445, > + "some datetime"); > + { > + uint column_numbers[]= {100,1,2,3,4,5,6,7,8}; > + test_value_multi(0, 0, 0.0, "0", > + "", 0, charset_list[0], > + 0, 0, 0, > + 0, 0, 0, 0, 0, > + 0, 0, 0, 0, 0, 0, 0, 0, > + column_numbers, > + "zero data"); > + } > + { > + uint column_numbers[]= {10,1,12,37,4,57,6,76,87}; > + test_value_multi(0xffffffffffffffff, 0x7fffffffffffffff, > + 99999999.999e120, "9999999999999999999999999999999", > + big_string, 1024*1024, charset_list[0], > + 9999, 12, 31, > + 0, 23, 59, 59, 999999, > + 0, 9999, 12, 31, 23, 59, 59, 999999, > + column_numbers, > + "much data"); > + } > + { > + uint column_numbers[]= {101,12,122,37,24,572,16,726,77}; > + test_value_multi(37878, -3344, > + 2873.3874, "92743.238984789898", > + "string", 6, charset_list[0], > + 2011, 3, 26, > + 1, 23, 23, 20, 333, > + 0, 2011, 3, 26, 23, 23, 53, 334, > + column_numbers, > + "zero data"); > + } > + test_value_multi_same_num(); > + { > + uint column_numbers[]= {1,2,3,4,5,6,7,2, 3, 4}; > + uint column_values[]= {1,2,3,4,5,6,7,0,30,40}; > + my_bool null_values[]= {0,0,0,0,0,0,0,1, 0, 0}; > + > + test_update_multi(column_numbers, column_values, null_values, 7, 10); > + } > + { > + uint column_numbers[]= {4,3,2,1, 1,2,3,4}; > + uint column_values[]= {4,3,2,1, 0,0,0,0}; > + my_bool null_values[]= {0,0,0,0, 1,1,1,1}; > + > + test_update_multi(column_numbers, column_values, null_values, 4, 8); > + } > + { > + uint column_numbers[]= {4,3,2,1, 4,3,2,1}; > + uint column_values[]= {4,3,2,1, 0,0,0,0}; > + my_bool null_values[]= {0,0,0,0, 1,1,1,1}; > + > + test_update_multi(column_numbers, column_values, null_values, 4, 8); > + } > + return 0; > +} Regards, Monty

2 2

[Maria-discuss] NHibernate and MariaDB
by Jake Drew 05 Apr '11

05 Apr '11

Hello, I have recently been converting 3 SQL Server Databases to MariaDB for a website our company is repackaging. One of the developers is requesting that during our updates we implement HHibernate as an ORM tool for each database. I am not familiar with NHibernate. I am also wondering, if anyone has used this technology with MariaDB or otherwise? If so, what are the performance implications and/or benefits within the context of MariaDB? Sent from my iPhone

3 2

[Maria-discuss] Does server reads /root/.my.cnf
by Πρεκατές Αλέξανδρος 05 Apr '11

05 Apr '11

Hi. # less .my.cnf [mysqld_safe] log-error=/var/log/mysql/error.log [mysqld] log-error=/var/log/mysql/error.log Also i have disabled syslog. But after restarting the server no errol.log is created. So does mysqld reads /root/.my.cnf ? Alexandros

3 3

[Maria-discuss] Bundle more relevant cnf files in MariaDB package
by Haidong Ji 04 Apr '11

04 Apr '11

Hi, I alluded to this in IRC maybe a couple of weeks back. That is, it is really to have intelligent default for MariaDB servers. In particular, the bundled sample my.cnf files, under /usr/local/mysql/support-files, such as my-small.cnf, my-medium.cnf, my-large.cnf, and my-huge.cnf, are laughable in today's world. In the my-huge.cnf, it talks about memory between 1G and 2G as huge. It will be good that MariaDB can bundle a different set, like what has been mentioned here: http://datastrangler.com/windpipe/2011/02/24/custom-mysql-config-files-to-e… I think the sample cnf files in the above blog post is a good starting point. Thanks, Haidong "Alex" Ji PS: I modified http://kb.askmonty.org/v/installing-mariadb-binary-tarballs with the addition of modifying $PATH so a casual user will be able to use various MariaDB clients after the install.

6 14

[Maria-discuss] The Plugins & Storage Engines Summit for MySQL/MariaDB/Drizzle 2011
by Colin Charles 01 Apr '11

01 Apr '11

Hi! Are you a developers who is writing a storage engines or plugins, knowing the plugin architecture of either MySQL, the extensions in MariaDB as well as the differences in Drizzle? Or are you writing User defined functions (UDF)? Or are you interested in developing something related to the MariaDB ecosystem? Then you should be at the summit on April 15 2011 Find out more at: http://kb.askmonty.org/v/storage-engine-summit-2011 -- Colin Charles, http://bytebot.net/blog/ | twitter: @bytebot | skype: colincharles MariaDB: Community developed. Feature enhanced. Backward compatible. Download it at: http://www.mariadb.org/ Open MariaDB/MySQL documentation at the Knowledgebase: http://kb.askmonty.org/

2 1