August 2012 - discuss - lists.mariadb.org

[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 27 Aug '12

27 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