Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Tags: ttdevelopers/socketSQL

Tags

mysql-5.5.22.t5

Toggle mysql-5.5.22.t5's commit message
Twitter MySQL 5.5.22.t5

mysql-5.5.23

Toggle mysql-5.5.23's commit message
Patch for Bug#13805127: Stored program cache produces wrong result in…

… same THD.

Background:

  - as described in MySQL Internals Prepared Stored
    (http://forge.mysql.com/wiki/MySQL_Internals_Prepared_Stored),
    the Optimizer sometimes does destructive changes to the parsed
    LEX-object (Item-tree), which makes it impossible to re-use
    that tree for PS/SP re-execution.

  - in order to be able to re-use the Item-tree, the destructive
    changes are remembered and rolled back after the statement execution.

The problem, discovered by this bug, was that the objects representing
GROUP-BY clause did not restored after query execution. So, the GROUP-BY
part of the statement could not be properly re-initialized for re-execution
after destructive changes.

Those objects do not take part in the Item-tree, so they can not be saved
using the approach for Item-tree.

The fix is as follows:

  - introduce a new array in st_select_lex to store the original
    ORDER pointers, representing the GROUP-BY clause;

  - Initialize this array in fix_prepare_information().

  - restore the list of GROUP-BY items in reinit_stmt_before_use().

--BZR--
revision-id: tor.didriksen@oracle.com-20120329130754-vr7xb7e5fbvoekzg
property-branch-nick: 5.5
testament3-sha1: e6d46503ec5e864c578aeb6842802c6ca2832f96

clone-5.5.23-build

Toggle clone-5.5.23-build's commit message
Patch for Bug#13805127: Stored program cache produces wrong result in…

… same THD.

Background:

  - as described in MySQL Internals Prepared Stored
    (http://forge.mysql.com/wiki/MySQL_Internals_Prepared_Stored),
    the Optimizer sometimes does destructive changes to the parsed
    LEX-object (Item-tree), which makes it impossible to re-use
    that tree for PS/SP re-execution.

  - in order to be able to re-use the Item-tree, the destructive
    changes are remembered and rolled back after the statement execution.

The problem, discovered by this bug, was that the objects representing
GROUP-BY clause did not restored after query execution. So, the GROUP-BY
part of the statement could not be properly re-initialized for re-execution
after destructive changes.

Those objects do not take part in the Item-tree, so they can not be saved
using the approach for Item-tree.

The fix is as follows:

  - introduce a new array in st_select_lex to store the original
    ORDER pointers, representing the GROUP-BY clause;

  - Initialize this array in fix_prepare_information().

  - restore the list of GROUP-BY items in reinit_stmt_before_use().

--BZR--
revision-id: tor.didriksen@oracle.com-20120329130754-vr7xb7e5fbvoekzg
property-branch-nick: 5.5
testament3-sha1: e6d46503ec5e864c578aeb6842802c6ca2832f96

mysql-5.5.21.t4

Toggle mysql-5.5.21.t4's commit message
Twitter MySQL 5.5.21.t4

mysql-5.5.22

Toggle mysql-5.5.22's commit message
Further upmerge the yaSSL upgrade (to 2.2.0) from MySQL 5.1 to 5.5.

Also, take a syntax fix (C++ style comment in C file) in client/mysqldump.c.

--BZR--
revision-id: joerg.bruehe@oracle.com-20120302122352-g2vx9uusx5m5t2q5
property-branch-nick: clone-5.5
testament3-sha1: e7fcf89fcce81ff9ff0065a6b1a196563fd2d464

mysql-5.1.62

Toggle mysql-5.1.62's commit message
Upmerge the yaSSL upgrade (to 2.2.0) from MySQL 5.0 to 5.1.

--BZR--
revision-id: joerg.bruehe@oracle.com-20120302121812-irpz21swytr4hg50
property-branch-nick: clone-5.1
testament3-sha1: cdda802473104409ca7169dc5d279fe8db12a7b7

mysql-5.0.96

Toggle mysql-5.0.96's commit message
Further upgrade the yaSSL library to version 2.2.0

to pick up some new security fixes that are in it.

Patch provided by Georgi Kodinov.

--BZR--
revision-id: joerg.bruehe@oracle.com-20120302121207-mp0mcduz9xwh7giw
property-branch-nick: clone-5.0
testament3-sha1: c586a3af4cde7f177e6a649b0bc280d77f35a76e

clone-5.5.22-build

Toggle clone-5.5.22-build's commit message
addendum to the --builtin-innodb depreacation bug. Fixing test suite …

…output.

--BZR--
revision-id: georgi.kodinov@oracle.com-20120219073355-crtpxmeanf838b4n
property-branch-nick: merge-5.5-security
testament3-sha1: 56f48c0134542c786f89b7f7072c9dc209ab9856

clone-5.1.62-build

Toggle clone-5.1.62-build's commit message
merge mysql-5.1->mysql-5.1-security

--BZR--
revision-id: georgi.kodinov@oracle.com-20120218085819-0t03t6wrb72d3lhf
property-branch-nick: merge-5.1-security
testament3-sha1: 2d6247f607f6caa2e2199bcc77d34d03cc5f795e

clone-5.0.96-build

Toggle clone-5.0.96-build's commit message
merged mysql-5.0->mysql-5.0-security

--BZR--
revision-id: georgi.kodinov@oracle.com-20120217095114-xqo0c03ko3lt5ga0
property-branch-nick: merge-5.0-security
testament3-sha1: 4ea1ecb3e615b68c004e3eca438434396cfaed83
Morty Proxy This is a proxified and sanitized view of the page, visit original site.