Percona is glad to announce the first RC release of Percona XtraDB Cluster 5.6 on December 18th, 2013. Binaries are available from downloads area or from our software repositories.
Based on Percona Server 5.6.15-63.0 including all the bug fixes in it, Galera Replicator 3.2 and on Codership wsrep API 5.6.15-25.2 is now the first …
[Read more]Today, we congratulate the Fedora community on their newest release. We believe it is a great platform to run the real, official MySQL on, and today we are adding Fedora 20 support in our Yum repos. We have the latest MySQL Server 5.6, the latest 5.7 development release and Connector ODBC ready for you on […]
If you have been using certain DBMSs, or reading recent versions
of the SQL standard, you are probably aware of the so-called
“WITH clause” of SQL.
Some call it Subquery Factoring. Others call
it Common Table Expression. A form of the WITH
CLAUSE, “WITH RECURSIVE”, allows to design a
recursive query: a query which repeats itself again and again,
each time using the results of the previous iteration. This can
be quite useful to produce reports based on hierarchical data.
And thus is an alternative to Oracle’s CONNECT BY. MySQL does not
natively support WITH RECURSIVE, but it is easy to emulate it
with a generic, reusable stored procedure. Read the full article
…
Currently, if you want to search a key using JSON UDFs you have
to specify each its part as a separate argument to the function:
JSON_CONTAINS_KEY(doc, 'root', 'child', 'child of child',
'child of child of child', etc.....). This way of working
with parameters is easy for developer, less error-prone, but can
be not very beautiful.
I was suggested by some of users to change it to
'/parent/child/child-of-child/...' or to
'parent:child:child-of-child:...' There are, probably, can
be other suggestions. What do you like the best? How do you feel
about current style with separate argument for each key element?
Should we change or extend this syntax?
Thank you Aaron! The first query is quite a find! Note that I just barely recognized the blog name from your profile on DBA.SE, though this post I found via Googling for MySQL indexes.
This is the first release which ships a 64 bit version along with
the 32 bit one. The installer includes both versions. Installing
over an existing 32 bit instance will again install the 32 bit
version. So if you prefer 64 bit you will need to uninstall
first.
Get it from the download page.
Here are the most noticable changes and new features:
* 64 bit version allows HeidiSQL to use much more of your
memory than the 2GB in 32 bit mode
* New feature: Fast table status for databases with InnoDB
tables. (Disable Session > Advanced > [X] Get full
table status)
* New feature: Favorites in database tree
* New feature: Append parameter names for procedures and
functions in completion proposal
* New …
This is the first release which ships a 64 bit version along with
the 32 bit one. The installer includes both versions. Installing
over an existing 32 bit instance will again install the 32 bit
version. So if you prefer 64 bit you will need to uninstall
first.
Get it from the download page.
Here are the most noticable changes and new features:
* 64 bit version allows HeidiSQL to use much more of your
memory than the 2GB in 32 bit mode
* New feature: Fast table status for databases with InnoDB
tables. (Disable Session > Advanced > [X] Get full
table status)
* New feature: Favorites in database tree
* New feature: Append parameter names for procedures and
functions in completion proposal
* New feature: Compressed .sql file export
* Migration to the brand new Delphi XE …
This is the first release which ships a 64 bit version along with
the 32 bit one. The installer includes both versions. Installing
over an existing 32 bit instance will again install the 32 bit
version. So if you prefer 64 bit you will need to uninstall
first.
Get it from the download page.
Here are the most noticable changes and new features:
* 64 bit version allows HeidiSQL to use much more of your
memory than the 2GB in 32 bit mode
* New feature: Fast table status for databases with InnoDB
tables. (Disable Session > Advanced > [X] Get full
table status)
* New feature: Favorites in database tree
* New feature: Append parameter names for procedures and
functions in completion proposal
* …
So how do you get MySQL 5.5, 5.6, or 5.7 on the latest Oracle Linux? Morgan had a great post on Installing MySQL 5.7 DMR3 with the official yum repos. This blog is about uprading from Oracle Linux 6.4 to 6.5 and getting a recent version of MySQL installed.
The first step, if you are running Oracle Linux 6.4, is to type yum install to upgrade to 6.5. Be sure to read the release notes and that you are pointing to the Public Yum Repository.
Use can use the Add/Remove Software tool to install MySQL 5.1. But who wants to run an old version of MySQL on a new, hot Linux. But let’s pretend you did install 5.1 when you installed 6.4 and now you are all sixes and sevens. So what do you do?
…
[Read more]I clicked around for a few moments but didn’t immediately see a license mentioned for the MariaDB knowledgebase. As far as I know, the MySQL documentation is not licensed in a way that would allow copying or derivative works, but at least some of the MariaDB Knowledge Base seems to be pretty similar to the corresponding MySQL documentation. See for example LOAD DATA LOCAL INFILE: MariaDB, MySQL.
Oracle’s MySQL documentation has a licensing notice that states:
You may create a printed copy of this documentation solely for your own personal use. Conversion to other formats is allowed as long as the actual content is not altered or edited in any way. You shall not publish or …
[Read more]