February 2013 - discuss - lists.mariadb.org

[Maria-discuss] mariasql client question (zappajs, coffeescript, nodejs)
by klrumpf 05 Feb '13

05 Feb '13

Hi, I have switched from mysql to mariadb using it with the node-mysql client and this has been runing in prod. for some time. I now want to switch to the mariasql client... inspect = require('util').inspect mdbClient = require('mariasql') ... To do the many queries and simplify the source I wanted to write a principal function for queries that simply returns an object (or array) with the query result and then I could just re-use the existing functionality for the render. So I copied this from the examples doSql = (sqlstring) -> c = new mdbClient() c.connect host: 'localhost' db: 'xyz' # NOT database user: 'abc' password: 'defghi' c.on("connect", -> console.log "Client connected" ).on("error", (err) -> console.log "Client error: " + err ).on "close", (hadError) -> console.log "Client closed" c.query(sqlstring).on("result", (res) -> res.on("row", (row) -> console.log "Result row: " + inspect(row) ).on("error", (err) -> console.log "Result error: " + inspect(err) ).on "end", (info) -> console.log "Result finished successfully, number of rows: " + info.numRows ).on "end", -> console.log "Done with all results" c.end() .... and then @get '/': (req,res) -> # LANDING PAGE) result = doSql("select pakz from pkt where pktnr=10001") console.log "919, result = ",result .... @view.... Console log in the doSql functions shows the results correctly but I have been playing around for a while and I can't get the function to return the result for further processing to the @get routine. Seems like I have not understood the scope issues here and probably a few more things, I am still green with this. My questions - what is the correct approach to do pass the query object from the function to the calling program if this is possible at all? - how do I access the individual rows the way I do it with node-mysql like so row[1].myfield ...? - should I create the instance of the mdbClient in the function or rather once at the very beginning of the program, my principal worry being stability even if the db disconnects here and there for some reason? Thanks, hope this is the right list for this, Karl -- Karl-L. Rumpf klrumpf(a)gmail.com Málaga, Spain

2 2

[Maria-discuss] Files under /etc/my.cnf.d/ read by default
by Honza Horak 05 Feb '13

05 Feb '13

Hi guys, while we were packaging MariaDB into Fedora (finally) we used the upstream's cnf files structure, which means /etc/my.cnf, that includes all files from directory /etc/my.cnf.d/* using statement !includedir. That works fine when user installs (not updates) the MariaDB packages without having them installed before. The problem is if user has changed /etc/my.cnf before updating -- then /etc/my.cnf doesn't get updated (!includedir won't be added) and we end with files under /etc/my.cnf.d/* but nothing what includes them. That is quite confusing for users that may change something in /etc/my.cnf.d/client.cnf but nothing happens. Since files under /etc/my.cnf.d/* are empty by default it shouldn't do any harm if all files corresponding with /etc/my.cnf.d/*.cnf template get loaded even without !includedir in /etc/my.cnf. Actually I believe that is what users expect to happen when they see files under /etc/my.cnf.d.. So, that's basically what I'm proposing -- read files under /etc/my.cnf.d/* by default, without a need to use !includedir. What do you think? Regards, Honza

1 1

Re: [Maria-discuss] Reading a field's default value from a trigger
by Bruce Kirkpatrick 04 Feb '13

04 Feb '13

For anyone encountering the "Field 'xxx' doesn't have a default value" when running insert/update/replace statement on MariaDB, I found that this is actually caused by the sql mode STRICT_TRANS_TABLES. This also fixes when a trigger updates the default value of the field. I believe the default options for MariaDB windows installer cause this option to be enabled, whereas I had previous never designed my application for the various modes supported. You can also fix the issue by giving every field in the table an explicit default value of 0 or '' except for text/longtext columns. I choose not to do that since I don't know how many other things change with STRICT_TRANS_TABLES. If you change my.ini / my.cnf to sql-mode="", you won't have this error occur anymore. You can run SELECT @@GLOBAL.sql_mode; on your mysql server and mariadb server to compare what the current settings are. This is my first post to the MariaDB mailing list. Sorry if I did it wrong. I've been using MySQL for over 10 years and decided to migrate to MariaDB now. -- Bruce Kirkpatrick<http://www.skyflare.com/> 386-405-4643

2 1

[Maria-discuss] MariaDB's tracking of MySQL changes
by Christian Convey 04 Feb '13

04 Feb '13

Can someone explain the relationship between MySQL and MariaDB code updates? I've read that MariaDB is a drop-in *replacement* for MySQL. But I've also read that MariaDB treats MySQL as an upstream code base. So what's the deal? Does MariaDB have alternative implementations for just some of MySQL's components, and when a new MySQL release comes out, MariaDB updates just those components for which it doesn't have its own versions? [This is a re-post from the #maria IRC channel, where I got no answer.] Thanks, Christian

2 1