… of Percona? as earlier it use to work fine on SQL. does it not support concurrent submission of a form (multiple…
Comment: Follow these basics when migrating to Percona XtraDB Cluster for MySQL
May 7, 2013 By 10 Comments
Post: Percona XtraBackup 2.0.7 for MySQL available for download
May 6, 2013 By 1 Comment
… copying failure. Bug fixed #1170806. innobackupex would fail if the SQL_MODE was set to ANSI_QUOTES. Bug fixed #945161. Missing…
Comment: Be careful when joining on CONCAT
May 6, 2013 By 16 Comments
Hi there! Is there any ways to EXPLAIN the SQL which is imported from the SOURCE command! @@
Comment: CVE-2012-4414 strikes back in MySQL 5.5.29 (and what we're doing in Percona Server 5.5.29)
May 2, 2013 By 4 Comments
…, thank you for correcting me. I am able to cause sql injection due to truncation, I have opened a new bug…
Comment: CVE-2012-4414 strikes back in MySQL 5.5.29 (and what we're doing in Percona Server 5.5.29)
May 1, 2013 By 4 Comments
Incorrect truncation is certainly a vulnerability. Why would you say otherwise? For example, if a string litteral is truncated in the middle. Then a later string litteral will be parsed as SQL expression.
Post: Follow these basics when migrating to Percona XtraDB Cluster for MySQL
May 1, 2013 By 10 Comments
… replication inside PXC has an additional overhead, this means the SQL_THREAD will not be able to execute events as fast…
Comment: Is your MySQL buffer pool warm? Make it sweat!
April 25, 2013 By 6 Comments
… similar, and I have had a lot of success writing sql queries (taken through Proxy at this stage) to a fifo…
Post: Percona Server 5.5.30-30.2 rerelease fixes non-restart issue
April 24, 2013 By Leave a Comment
… was used with –innodb-optimize-keys option it produced invalid SQL for cases when there was an explicitly named foreign key…
Post: MySQL alternative Percona Server 5.1.68 -14.6 now available
April 19, 2013 By 3 Comments
… was used with –innodb-optimize-keys option it produced invalid SQL for cases when there was an explicitly named foreign key…
Comment: 10 years of MySQL User Conferences
April 13, 2013 By 6 Comments
@Henrik, This is all due to the stup1d SQL 1-based convention (e.g SUBSTRING(s,1))!
