Created by MySQL RE and last modified
Get this branch:
bzr branch lp:~mysql/myconnpy/1.6
Members of Oracle/MySQL Engineering can upload to this branch. Log in for directions.

Branch merges

Related bugs

Related blueprints

Branch information

Oracle/MySQL Engineering
MySQL Connector/Python

Recent revisions

456. By Israel Gomez

BUG#19675964 : README file name in DMG packages is not congruent to other pkgs

The README file in the MySQL Utilities commercial DMG packages is being named
ReadMe.txt instead of README_com.txt unlike in other packages. Similarly, the
LICENSE file was packed as License.txt instead of LICENSE.txt. This patch
fixes the packaging code to correctly include these files with names that are
congruent with the other packages.

The license notice that appears in the Python egg for the commercial
distribution has also been corrected to be NO GPL applicable.

As part of fix BUG#19675930, the bdist command has been updated to include
the README_Fabric_com.txt instaed of README_Fabric.txt

In addition the MySQL Utilities version has been updated to be the same as
the release version (1.6).

v4 patch for mu-1.6.0

455. By Israel Gomez

BUG#19611879 : msi distribution package sets wrong permissions on installed dir

The Utilities msi distribution package was setting wrong permissions for
created installation directory, including all permissions granted for the
'Users' group. This patch removes the permissions section from the the Windows
msi package descriptor, now the only permission set for the 'Users' group
is read only.

This patch also affects the 1.6.0 branch.

BUG# Added to CHANGES.txt and incrementing tag

454. By Israel Gomez

Release 1.6.0 testing.

Added Upgrade code for release 1.6.0 in MSI package mechanism.

453. By Balasubramanian Kandasamy

Added new utilities mysqlgrants and mysqlbinlogmove

452. By Chuck Bell

Fixed version number (caps)

451. By Chuck Bell

Fixed version number (alpha release) and tag

450. By Chuck Bell

Updated CHANGES.txt for release to SysQA

449. By Paulo Jesus

WL#6187 : Binary log relocate

The binlogmove_parameters test fails on Windows due to a server issue for
the SHOW BINARY LOGS statement. This statement display unexpected and wrong
information after relocating the binary log files if it is not executed

This patches adds a workaround for this regression issue, executing a first
SHOW BINARY LOGS on Windows before relocating the binary log files. This way
the binlogmove_parameters test runs correctly on all platforms.

In addition, a new method was added to the binlogmove_privileges test in
order to ensure that all relay log files are created before running the test
case for the slave, otherwise it might fail in some situations.

448. By Paulo Jesus

Merge with 1.5.2 and fix CHANGES.txt (repeated entry for bug).

447. By Paulo Jesus

WL#6187 : Binary log relocate

This patch adds the new mysqlbinlogmove utility to move existing binary log
files (binlog or relay logs) to a new location, updating the corresponding
index file accordingly. In particular, it allows two main operations; 1)
archive older binary logs to a new location with the server running (not
moving the latest binary log) using the --server option, and 2) relocate all
binary logs with the server stopped to a new location using the --binlog-dir
option (for example, allowing the server option --log-bin to be changed
afterwards without errors when starting the server).

In addition, some improvements were made to the existing code, namely:
- Corrected the error message when an invalid end date format is used for the
  mysqlauditgrep utility;
- Improve check_dir_option() in the mysql.utilities.common.option module to
  return the absolute path of the specified directory.
- Add functions get_value_intervals_list() and check_date_time() to the
  mysql.utilities.common.option module to improve code reuse when checking
  option values with interval lists and date/time.
- Add a new message PARSE_ERR_OPTS_EXCLD template to improve error message
  reuse for option that cannot be used simultaneously;

New MUT tests were added for the new utility, as well as a new unit test for
the new common module.

Branch metadata

Branch format:
Branch format 7
Repository format:
Bazaar repository format 2a (needs bzr 1.16 or later)
Stacked on:
This branch contains Public information 
Everyone can see this information.