We are working towards connecting with the MySQL user community in Bangalore. Please join us on the facebook group MySQL User Camp to get updates on upcoming activities

The first meet was held @ Oracle, Kalyani Magnum on March 22nd. Sanjay Manwani and Karthik P R have blogged about it

http://remotemysqldba.blogspot.in/2013/03/bangalore-mysql-user-camp.html
…

MySQL has always given great emphasis on quality.  This has got even better in the last few years with increased investment in the dedicated test team. The Server test team tripled in size during 5.6 development and all 5.6 features have undergone thorough testing at the hands of the QA team.
I have more than 15 years experience in this industry and have worked on different products and technologies as part of test and development teams. Compared to most others I find the developers in MySQL very involved in testing. Here the developers are expected to write functional tests for their features and bug fixes. This is how it was historically and this continues today in spite of the bigger test team. This model has the following advantages

• Code is in reasonably good shape when delivered to test team
• Testers can focus on more complex tests since the straightforward tests will be written by the developers …

Annnnnd here’s the recording:

Hey all!

The Percona Live MySQL Conference and Expo is coming up in 2 weeks, meaning the last of preparations are under way. In the meantime, #DBHangOps is coming your way on Wednesday at 12:00pm PDT (19:00 GMT) with:

• Talk about Performance Schema from Mark Leith
• Some discussion on how people use and manage MySQL slow query logs in their environments
• Filesystems and MySQL — which do you use, why, and how
• What you’re excited about at Percona Live!

As always, hit up this twitter search or this blog post to grab the google hangout link to join!

See y’all on Wednesday!

Currently the English error messages are embedded in all of the tests in MySQL. This means that you can’t really update the English translations without breaking a bunch of tests. I’m not sure if there’s a standard way to fix this, but it occurs to me that it would be quite easy to have a “system” localization which just prints a language-neutral version of the error, meaning that any version of it can be updated without breaking any tests.

For example, the following simple syntax error gives a message in English:

mysql> select foo;
ERROR 1054 (42S22): Unknown column 'foo' in 'field list'

This is based on the following definition in the errmsg-utf8.txt file:

ER_BAD_FIELD_ERROR 42S22 S0022
        eng "Unknown column '%-.192s' in '%-.192s'"

In a test case this might be codified as:

--echo # Test that ER_BAD_FIELD_ERROR works.
--error ER_BAD_FIELD_ERROR
SELECT foo;

The …

Auditing of  a MySQL server activity is a request raised more and more often as compliance rules are more strict for companies. MySQL is used in more and more critical areas.

What are the various loging technologies available on a MySQL server that could be use for auditing :

The error log The slow query log [...]

Read the original article at Don’t Miss Percona Live 2013

The biggest event on the MySQL calendar is the yearly Percona Live and it’s just around the corner. This year you’ll be able to pick from a whopping 110 technical sessions by 90 different speakers from companies like Facebook, Amazon, Google and Linkedin. Learn what’s happening at the cutting edge of open source database deployments. [...]

For more articles like these go to Sean Hull's Scalable Startups

Related posts:

1. Why you should attend Percona Live 2012
2. Hacking Job …

Last week I was implementing a new report using MySQL, and some of the data was stored in JSON format. MySQL has lots of built-in string functions, but none of them work for JSON. My first idea was to use the mysql_json UDF, but then I remembered that common_schema recently added JSON parsing. Since I have common_schema 1.3 installed on all of my databases already, I tried that first.

In this particular case the JSON is pretty simple. It contains two fields: age and gender. Here's an example of the data format:

…

The Call for Papers for MySQL Connect 2013 will close this Friday.  This is the premier Oracle-sponsored MySQL conference, and a great opportunity for community users and customers alike to connect with Oracle staff from engineering, support, consulting and other organizations, as well as community partners and peers.  Maybe you’d like to talk about your experiences integrating one of the new MySQL 5.6 features.  Or maybe you’d like to share best practices you’ve developed for integrating with Hadoop.  Perhaps you’ve extended MySQL and want to tell the community about it.  Take advantage of this opportunity and submit your proposal this week!

Tableau preps IPO. Funding for SiSense and Deep. And more.

* For 451 Research clients: Citus Data brings SQL to foreign data environments, starting with Hadoop

* For 451 Research clients: With $20m in series B funding in the bag, Platfora makes its Hadoop-based analysis debut

* Tableau Software Files Registration Statement For Proposed Initial Public Offering.

* SiSense raises $10m series B funding.

* …

Last week I was implementing a new report using MySQL, and some of the data was stored in JSON format. MySQL has lots of built-in string functions, but none of them work for JSON. My first idea was to use the mysql_json UDF, but then I remembered that common_schema recently added JSON parsing. Since I have common_schema 1.3 installed on all of my databases already, I tried that first.

In this particular case the JSON is pretty simple. It contains two fields: age and gender. Here's an example of the data format:

…