Showing entries 15143 to 15152 of 44107
« 10 Newer Entries | 10 Older Entries »
MySQL Connector/Python 1.0.8 available for download

Last week we made a maintenance release for MySQL Connector v1.0 available. The announcement can be read in the MySQL forums and the history log is available online.

Connector/Python v1.0.8 does not introduce anything new, it only comes with bug fixes. Some are quite important and it’s probably good to upgrade.

Please use the MySQL Bugs website to report any problem.

Some useful links:

[Read more]
Merry Christmas
mysql --silent -niGHt -e "SELECT GROUP_CONCAT(val ORDER BY id SEPARATOR ' ') AS Greeting FROM mysql.greeting"
Greeting
Merry Christmas and Happy New Year
See you in 2013

mysql is the MySQL Command Line Client – my favourite tool when using MySQL. It is available on all platforms where you can install MySQL and is part of a standard installation. As you can see there are many options, including the -H which causes the output to be HTML formatted. Ok, I cheated here and created the table manually as my blog editor escapes HTML code – the actual output looked like:

<TABLE BORDER=1><TR><TH>Greeting</TH></TR><TR><TD>Merry Christmas and Happy New Year
See you in 2013</TD></TR></TABLE>

[Read more]
OurSQL Episode 121: Fun with text files

This week we discuss manipulating text data and the CSV storage engine. Ear Candy is Venn Diagrams visually showing joins, and At the Movies is about how to retain your individuality while being on a team.

Events
FOSDEM 2013 is taking place in Brussels, Belgium Sat Feb 2 - Sun Feb 3rd. Call for papers for the MySQL & Friends room closes December 21st.

Northeast LinuxFest is happening at Harvard University, Cambridge MA Saturday March 16th and Sunday March 17th, 2013. Open Database Camp will be held there. Sponsors are needed, make sure to specify you …

[Read more]
New feature: Microseconds in DATE/TIME values

MariaDB 5.3 and up and MySQL 5.6 RC introduced real support for milliseconds:
https://kb.askmonty.org/en/microseconds-in-mariadb/
http://dev.mysql.com/doc/refman/5.6/en/fractional-seconds.html

HeidiSQL now lets you define a LENGTH/SET value for data types which allow a microsecond precision (0-6, where 0 is the default). Also, when editing such TIME, TIMESTAMP or DATETIME values in a grid, HeidiSQL lets you press arrow up/down to increase/decrease the microseconds part of the underlying value. Thanks to rjgebis for the report and documentation links.

New feature: Microseconds in DATE/TIME values


MariaDB 5.3 and up and MySQL 5.6 RC introduced real support for milliseconds:
https://kb.askmonty.org/en/microseconds-in-mariadb/
http://dev.mysql.com/doc/refman/5.6/en/fractional-seconds.html

HeidiSQL now lets you define a LENGTH/SET value for data types which allow a microsecond precision (0-6, where 0 is the default). Also, when editing such TIME, TIMESTAMP or DATETIME values in a grid, HeidiSQL lets you press arrow up/down to increase/decrease the microseconds part of the underlying value. Thanks to rjgebis for the report and documentation links.

New feature: Microseconds in DATE/TIME values

MariaDB 5.3 and up and MySQL 5.6 RC introduced real support for milliseconds:
https://kb.askmonty.org/en/microseconds-in-mariadb/
http://dev.mysql.com/doc/refman/5.6/en/fractional-seconds.html

HeidiSQL now lets you define a LENGTH/SET value for data types which allow a microsecond precision (0-6, where 0 is the default). Also, when editing such TIME, TIMESTAMP or DATETIME values in a grid, HeidiSQL lets you press arrow up/down to increase/decrease the microseconds part of the underlying value. Thanks to rjgebis for the report and documentation links.

New feature: Microseconds in DATE/TIME values

MariaDB 5.3 and up and MySQL 5.6 RC introduced real support for milliseconds:
https://kb.askmonty.org/en/microseconds-in-mariadb/
http://dev.mysql.com/doc/refman/5.6/en/fractional-seconds.html

HeidiSQL now lets you define a LENGTH/SET value for data types which allow a microsecond precision (0-6, where 0 is the default). Also, when editing such TIME, TIMESTAMP or DATETIME values in a grid, HeidiSQL lets you press arrow up/down to increase/decrease the microseconds part of the underlying value. Thanks to rjgebis for the report and documentation links.

A MySQL Christmas present - Libdrizzle 5.1.0

Brian Aker and I have been working hard in the last few weeks to give you a great Christmas present, Libdrizzle 5.1.0.  The MySQL compatible, BSD licensed C connector (so static compiling with commercial software gets the thumbs up!).

The latest changes include:

  • A server-side prepared statement API
  • Improved binary log API
  • An example binary log remote retrieval utility using the binlog API called "drizzle_binlogs"
  • A new build system, DDM4 which is used by Gearman and Memcached
  • Many bugs fixes

The source and manuals can be found on the Launchpad downloads page.  Please enjoy, feel free to file bugs, questions and hack on code on our Launchpad …

[Read more]
PERFORMANCE IMPROVEMENT FROM VIEW DEFINITION CACHING IN MySQL 5.6

Every time a view is accessed in MySQL, the view definition has to be read from the .FRM file on disk. This was resulting in a huge performance bottleneck. That is why we decided to introduce “View Definition Cache” in MySQL 5.6. Caching the view definitions turns out to work even better than hoped.

With the introduction of “View Definition Caching”, the view definition is read from the .FRM file on the first access of the view and cached. Subsequent view accesses gets the view definition from cache instead of reading it again from the .FRM file, until the view is removed from the cache. The view elements from the cache are removed on LRU basis when the cache is full or when DDL operations(as ALTER, DROP) are performed on the view. The size of the cache can be configured by the system variable “table_definition_cache”(Default Value= 128).

The following experiment shows the improvement in performance with the view …

[Read more]
Handling MySQL’s warnings in Go code

I was just bitten by failing to catch a MySQL warning. It’s the old familiar tune: I inserted 100 characters into a VARCHAR(50) and it didn’t throw an error*. Of course, then subsequent SELECT statements didn’t find the value I inserted.

What’s different this time is that I was using Go as the client. There is no single official MySQL driver for Go, although there are several good-quality community-maintained ones. I was using one of those through the official Go database interface, which is a simple and lightweight way to interact with relational databases. This interface will generate errors, but I didn’t think about warnings. This is funny, because usually I’m paranoid about capturing warnings from MySQL and treating them as errors.

After I discovered my mistake, I realized that Go’s database interface doesn’t provide a way to observe the warnings …

[Read more]
Showing entries 15143 to 15152 of 44107
« 10 Newer Entries | 10 Older Entries »