June 2015 - discuss - lists.mariadb.org

[Maria-discuss] will maria db overcome mysqls feature limitations? (foreign keys+triggers, recursive triggers)
by Ludwig Gramberg 19 Jul '15

19 Jul '15

Hi, I was wondering if mariadb plans to overcome mysqls limitations such as - foreign key operations do not start triggers - triggers can’t be recursive (error 1442) I know that mariadb wants to be compatible with mysql but maybe these features could be optional? The mysql/mariadb comparison shows additional features which wont break compatibility I guess because they don’t exist in mysql (yet?). But besides additional features, is there a chance that mariadb could ever overcome limitations? Is this even a goal of this project? So far I only found postgres to support these features. Background of this question: I am developing an object relational mapper and my goal is to have the database enforce the consistency. So triggers and foreign key constraints working together are vital for this. regards Ludwig

4 5

[Maria-discuss] INSERT IGNORE and triggers
by Federico Razzoli 19 Jul '15

19 Jul '15

Hello. As we all know, IGNORE "catches" some errors and turns them into warnings. But I've noticed that it does not catch the same errors if they were issued by a trigger (using SIGNAL). * Is this by design? * Is this standard SQL behaior? Here is a trigger example to show what I mean: CREATE TRIGGER bi_t BEFORE INSERT ON t FOR EACH ROW BEGIN SIGNAL SQLSTATE '23000' SET MYSQL_ERRNO = 1048; END Regards Federico

2 1

Re: [Maria-discuss] Can't connect to local MySQL server through socket
by Sylvain Raybaud 01 Jul '15

01 Jul '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi I'll try hard to fix the problem with rsync, even if I switch to mysqldump or xtrabackup-v2 in the future. Some context : mariadb and galera are built in buildroot and run on raspberry pis (ARMv6). Mariadb is started manually. I fixed the config file as you suggested yesterday (wsrep_cluster_address=gcomm://IP1,IP2,IP3 in my.cnf on all three nodes). I bootstrap the cluster on node #1 with --wsrep-new-cluster and I just start mysqld_safe and nodes #2 and #3. Running: mysql -u root --execute="SHOW GLOBAL STATUS WHERE Variable_name IN ('wsrep_ready', 'wsrep_cluster_size', 'wsrep_cluster_status', 'wsrep_connected');" on node #1 gives me: +----------------------+---------+ | Variable_name | Value | +----------------------+---------+ | wsrep_cluster_size | 3 | | wsrep_cluster_status | Primary | | wsrep_connected | ON | | wsrep_ready | ON | +----------------------+---------+ and on nodes #2 and #3: ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/tmp/mysql.sock' (111 "Connection refused") If I start mariadb outside a cluster on nodes #2 and #3 it works as expected. It seems nodes #2 and #3 are never synced since SYNCED never appears in error log. wsrep_sst_method is rsync. On 24/06/2015 15:00, Guillaume Lefranc wrote: >> Does this mean that mariadb tries to sync nodes but for some >> reason the script hangs, the nodes are never sync and remain >> unusable? > > I'm afraid that must be something along those lines. I have the > following suspicions: > > * SELinux or Apparmor not disabled, causing the SST to hang > forever. * Ports not open on the firewall (for the record you need > 3306, but also 4444, 4567 and 4568). Neither SELinux or Apparmor is enabled and there is no firewall on any of the boxes. They are all connected to the same ethernet switch. I'm investigating wsrep_sst_rsync script. Here are the processes running: # ps auxf | grep mysql 128 root {mysqld_safe} /bin/sh /usr/bin/mysqld_safe - --defaults-file=/etc/mysql/my.cnf 422 mysql /usr/bin/mysqld --defaults-file=/etc/mysql/my.cnf - --basedir=/usr --datadir=/var/lib/mysql --plugin-dir=/usr/lib/plugin - --user=mysql --wsrep_provider=/usr/lib/libgalera_smm.so - --log-error=/var/lib/mysql/buildroot.err --pid-file=/tmp/mysql.pid - --socket=/tmp/mysql.sock --port=3306 - --wsrep_start_position=00000000-0000-0000-0000-000000000000:-1 429 mysql sh -c wsrep_sst_rsync --role 'joiner' --address '192.168.1.80' --auth '' --datadir '/var/lib/mysql/' --defaults-file '/etc/mysql/my.cnf' --parent '422' --binlog '/var/lib/mysql/mariadb-bin' 430 mysql {wsrep_sst_rsync} /bin/bash -ue /usr//bin/wsrep_sst_rsync --role joiner --address 192.168.1.80 --auth --datadir /var/lib/mysql/ --defaults-file /etc/mysql/my.cnf --parent 422 --binlog /var/lib/mysql/mariadb-bin 458 mysql rsync --daemon --no-detach --port 4444 --config /var/lib/mysql//rsync_sst.conf 26966 mysql sleep 0.2 Note the sleep 0.2: it shows up often. It appears in wsrep_sst_rsync in two places: lines 136--140: # wait for tables flushed and state ID written to the file while [ ! -r "$FLUSHED" ] && ! grep -q ':' "$FLUSHED" > /dev/null 2>&1 do sleep 0.2 done lines 281--284: until check_pid_and_port $RSYNC_PID $RSYNC_REAL_PID $RSYNC_PORT do sleep 0.2 done Is it possible that one these loops never terminates? If I run the same commands invoked by mysql manually, they terminate with errors because SST_PROGRESS_FILE and WSREP_SST_OPT_ROLE aren't defined but this is probably not significant. I'll be happy to read any idea you might have. Maybe I should also send this message to galera mailing list? Cheers, - -- Sylvain Raybaud www.green-communications.fr -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBAgAGBQJVi9d9AAoJEEkkwl4JtJ9yE6EP/3PVzEXO7KVX9UrKrQSLXXM/ EWuV2a2KKxB8GkH1uDBISrn84futPR6M7/gdbMV8DeRNWAbCWgXWkrY/HVALvLxu jze4znZMmn+mxqDzmhp1klon+w9WAyH7lSfIC4AGgSiAe6ZFP5c8CSfbLNJPlSM+ buoJTQz9BFo+NTh4w7gbZUjAJVEm/7CpM8TwMPsu7+mMvbn4yMMLU2RkjhysGGKI YAJ9dXYjmD+49Z3Z2B54lRGeIbZNMDRjlQ/+F61Ml9XbQYJtDb8gHGN5a4FIiaFh pvOtjCi5foXdGfGv/nPbSkrMqkKBJHL0xbnKeze/OdIdZ1aOVN7Sy5tZJirlCJV3 q/48hmrIIMVU1FuC9F0zW7lGHsgsKiQvLM0X8C/ZdX0ZTvTjWWefoWLa/fSv/vYp z9E5HJxJ47gbnGeSEBby1+TmV/GoXvjiyH3oRXzEuyEP5xQtKH4Kvrh9MhwZdZpv sJc5QO9qfAHPecavhRQ1luuv6JCSqLPGpF+3RB80rB+BRUkwi0dfO0RmBzzmKBGZ vryGxAVBNZmpIatuCWY4cvvrkQm9kF7JMAR1rNTRylxLtyI5TR42c5r24tSasWct P6gICSrMBKVgoCdxanTI2q+faqAur/NDq4W6tgeqRnV/mk9zQW4oxJxfwQlS0zr6 YiUMXGeRi6IT0MTKwChk =goS7 -----END PGP SIGNATURE-----

2 5

[Maria-discuss] New Question: Data Type
by AskMonty KB 29 Jun '15

29 Jun '15

Hello, A new question has been asked in "MariaDB Community" by bhumika. Please answer it at http://mariadb.com/kb/en/data-type/ as the person asking the question may not be subscribed to the mailing list. -------------------------------- Hello, Can I create my own custom Data type in Maria DB , Can you please provide me some help on this. -------------------------------- To view or answer this question please visit: http://mariadb.com/kb/en/data-type/

1 0

[Maria-discuss] New Question: ipv6
by AskMonty KB 28 Jun '15

28 Jun '15

Hello, A new question has been asked in "MariaDB FAQ" by gerald_schade_g. Please answer it at http://mariadb.com/kb/en/ipv6/ as the person asking the question may not be subscribed to the mailing list. -------------------------------- does, will or when (and how) will MariaDB support client-connections via ipv6? -------------------------------- To view or answer this question please visit: http://mariadb.com/kb/en/ipv6/

1 0

[Maria-discuss] doubt about index
by Roberto Spadim 26 Jun '15

26 Jun '15

hi guys, i`m with a doubt... when i have a primary key i know that's a unique key when i have a index with primary key + any other column, does mariadb consider that it's unique too? i`m thinking more about SELECT optimization

4 31

[Maria-discuss] FedereratedX ODBC Source
by Darin Keever 25 Jun '15

25 Jun '15

This is regarding: https://mariadb.com/kb/en/mariadb/about-federatedx/ Specifically, the last section bullet - Support for other RDBMS vendors using ODBC My employer started a project to add a generic ODBC source to the FederatedX plugin. Once into the project, it was decided that creating a specific source to our COM server would be faster. The ODBC source did work, but it was buttoned up after read-access was completed. I'm not sure if it will ever be released, but I thought we should distribute the code regardless. Please find an incredibly boring page here: http://stonebond.com/mariadb-contributions/ Included in the zip are the changes to source files, as well as two additional files for connecting to ODBC and to our COM dll. These were only compiled on windows, so likely are not ready for inclusion in the source tree. Let me know if you have any questions.

2 2

[Maria-discuss] More love for Dynamic Columns - support in Sequel Pro
by Tom Worster 24 Jun '15

24 Jun '15

Just a little bundle plugin to view the values in a dyncol blob but very handy all the same. If you use dyncols, which I do. https://github.com/tom--/sequel-pro-maria-dynamic-column In other dyncol news, we've improved the ORM extension <https://github.com/tom--/dynamic-ar> that I mentioned in a previous email. I'm using it in a project and it's really nice not to have to either mess with the schema every day or EAV. Having a nosql document in every row of a table is real swell. Tom

1 0

Re: [Maria-discuss] Can't connect to local MySQL server through socket
by Sylvain Raybaud 24 Jun '15

24 Jun '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Guillaume, Nirbhay, On 24/06/2015 15:35, Guillaume Lefranc wrote: > If you want to try xtrabackup SST: * xtrabackup must be installed > on all servers * you need to set wsrep_sst_method=xtrabackup-v2 > (the older method is full of horrible bugs) * you need to set > wsrep_sst_auth to a user account which has permissions to do > backup, e.g. : RELOAD, LOCK TABLES, REPLICATION CLIENT at the > minimum > > I cannot stress it enough but re-read the docs thoroughly before > doing anything :-) > In my case it means creating a buildroot package for xtrabackup, which is definitely on my TODO list, but wasn't scheduled just now :) Since SST fails both with rsync and mysqldump (even when I set credentials properly, or think I do), I think I should fix that before trying to switch to another method. I think this mariadb problem is hiding a more fundamental communication problem between my buildroot boxes. I'll let you know. - -- Sylvain Raybaud www.green-communications.fr -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBAgAGBQJVisWEAAoJEEkkwl4JtJ9yPmsQALxq44ZbyqqHhnUStSo5P29H RVvUztKZ9cfG11ksPToFeCIlcuMiVhL6j5nzLQ/nskEIavVPeSCovmUVlYNTqLAm ZufNhGY0xAvUoaaDow125dy7wB0Sxq246cAFytNMP1ru/T770h955uObSCpEu7ql PW18Qd2DMoNDb1xReyAmGiUa2wHdWJMLHP7G5tn4nIauESgymRRMh5Ha/7BpBIWw WoEFr3BPPXvzdm/SHY/rjWRR5pl5xKlKv3gzweuNWw64d5T2ppO906bId3b8fZWz iSEwhmX57Pgkgpn2iPjx3eCQVkRI5Du7rMifhbA0Os5tsHXB+Ia3seVeXs+DMkvL tQTnQIMgzRC7M6zCBOt7axZwQVH0DDuZwBfPDzPbF2EiiSTkwULPZN90Mp/itOR3 84xkC7b2hZG6porEJv2/gNk/SBop8Elvx91JcSv7t7RNDMGggq4q3ZXz6ai4vGMY nIWH/hNqiybeUFrVBRWoVpiRSejLLB+SVf1v74yiB7JeXbuIa8WnbgVek0cle3j5 u4wBk+MkewrcVhDxXB6d1x9k/e0QP1MaohUPMFeyrw25MtoyFx/RfjhI8cMtPSdI 9lF39YqNMDrZ+wlwZ9v1ylh56popD0faYjMaSQwXKMBNH08dMisqUj9Vt94JY2pe Dz2TSVIvCDLlyBGT73nN =yjW8 -----END PGP SIGNATURE-----

1 0

Re: [Maria-discuss] Can't connect to local MySQL server through socket
by Sylvain Raybaud 24 Jun '15

24 Jun '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 24/06/2015 15:11, Guillaume Lefranc wrote: > Sylvain, > > On Wed, Jun 24, 2015 at 3:06 PM, Sylvain Raybaud > <sylvain.raybaud(a)green-communications.fr > <mailto:sylvain.raybaud@green-communications.fr>> wrote: > > >> >> I forgot to mention in my previous mail that after starting >> mariadb in the first node I run: >> >> mysql -u root --execute="SET GLOBAL >> wsrep_cluster_address='gcomm://';" >> >> >> Don't do the above. Since you are starting the cluster with >> --wsrep_new_cluster, that's enough. I'm not sure of what it >> would do but I'd rather avoid to bootstrap the cluster two >> times. > > If I don't, the cluster does not start at all, all I get is a > disconnected cluster of size 0 on node #1, exactly as described > here: > https://mariadb.com/blog/mariadb-galera-cluster-quirk-bootstrapping > > > > Yes, but this happens for a good reason and the manual is quite > clear about that: You didn't set wsrep_cluster_address in your > my.cnf. I would recommend to set it on all nodes, as it can cause > all kinds of things to go wrong in the future (imagine you reboot > your 1st node, it has no peers to reconnect to), plus some other > side effects I cannot envision. So recommendation is really to have > this set on all nodes with IP addresses of each node, in your case > wsrep_cluster_address=gcomm://192.168.1.77 > <http://192.168.1.77/>,192.168.1.80,[IP of node 3] Got it, doing that :) I tried setting wsrep_sst_method to mysqldump instead of rsync and it fails. Here are the error logs: node #1: http://pastebin.com/UXr378mC node #2: http://pastebin.com/4xEi2ncS node #3: http://pastebin.com/LWvmrdAt Still investigating. - -- Sylvain Raybaud www.green-communications.fr -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBAgAGBQJVirDlAAoJEEkkwl4JtJ9ytK4P/2d8QMDUKbN48MT1/mA4kI4x n2Y1VOahIUWxG6YZjenAHSi96VUpzIkpk5VQvzeozIRTtmsFlfhsitwZwd8pERmu Usse6+fptio2iHpzabyterMmyXrEcI9Dtdu9/4KBPBKs1WBdShDkmEvUJ279oaIU uj3cuOMWo05snac3wFuSk53edCaUPT6CJfTHUn+FkmFQbRzEE89Q2IW+FKdUW23L X9XOuabR5iu1/5FeJxmYut3yS10slByebofjQlMGFdRZ20ZD60phRjuIqr4VtgK+ Pl6wwMlAYMgrwvGxNUOzA3czm23oulfwcziFRk8DA2xkLxJyYDW8XDzGphoBWLzZ oaQIE+ikYNFEUDPGUVvBRnVigmi2NksXz7s8ND8oSROwoXqzgH+MhR1kYdcysPKp aEs94h7uwh1u+0wHVNFmd7xNwbZyJxeb+ICB7GxpTlLMk8EbUZzbuGiiEcZaWNb3 IOfifbs8sc5/eE3Jrds67cFaUsjAchyNLQ2eNraoiDN1b8KD6nflmU8M5bdJ9UYH ICfpa9CSA2+qYWHWh9XfEEwb3Ugal1i/xSqlbObkVeqAlG8/PWbA5ubeBlGhzVDF jObLYVhh5c+bKLtKXPmzi1fvvsCaSiYRvXFxetmWO+8BpL27i37dfhslyc8Fk6/j +YwjwwY+st1sIm1oE/5M =Lvhi -----END PGP SIGNATURE-----

2 1