./databases/mysql51-client, MySQL 5, a free SQL database (client)

[ CVSweb ] [ Homepage ] [ RSS ] [ Required by ] [ Add to tracker ]


Branch: CURRENT, Version: 5.1.72nb3, Package name: mysql-client-5.1.72nb3, Maintainer: pkgsrc-users

MySQL is a SQL (Structured Query Language) database server. SQL is the
most popular database language in the world. MySQL is a client-server
implementation that consists of a server daemon `mysqld' and many
different client programs/libraries.

The main goals of MySQL are speed and robustness.

The base upon which MySQL is built is a set of routines that have been
used in a highly demanding production environment for many years. While
MySQL is still in development it already offers a rich and highly useful
function set.

The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL).

This package contains the MySQL client programs and libraries.


Required to run:
[lang/perl5]


Package options: embedded-server, mysqlmanager, ndb-cluster, pstack, ssl

Master sites: (Expand)

SHA1: af1f46e56402b38a085ac592cd7df3aa25e9cea2
RMD160: a5ba8bedf4027af90a4612a1a7f3a848999cfbf5
Filesize: 23480.799 KB

Version history: (Expand)


CVS history: (Expand)


   2014-08-20 11:04:57 by OBATA Akio | Files touched by this commit (3)
Log message:
File::Temp was first released with perl v5.6.1, so no need to install it
from pkgsrc in these days.
   2014-05-30 01:38:20 by Thomas Klausner | Files touched by this commit (3049)
Log message:
Bump for perl-5.20.0.
Do it for all packages that
* mention perl, or
* have a directory name starting with p5-*, or
* depend on a package starting with p5-
like last time, for 5.18, where this didn't lead to complaints.
Let me know if you have any this time.
   2014-05-28 12:16:55 by Mark Davies | Files touched by this commit (2)
Log message:
Dont find gethostbyname_r() on NetBSD.  The API differs resulting in
segfaults on 6.1_STABLE.
   2014-04-14 02:02:50 by Blue Rats | Files touched by this commit (9)
Log message:
Don't hardcode PID file. Instead, give the user the option to set it. The
rc.d script overrides my.cnf directives. Hardcoding the PID can cause a
problem on systems transitioning to MySQL packages from pkgsrc.
   2014-02-13 00:18:57 by Matthias Scheler | Files touched by this commit (1568)
Log message:
Recursive PKGREVISION bump for OpenSSL API version bump.
   2013-12-05 15:20:02 by Thomas Klausner | Files touched by this commit (6)
Log message:
Remove CONFLICTS with ${PKGBASE}, these are automatic.

Avoids unnecessary pkgin warning.
   2013-10-01 13:00:39 by Adam Ciarcinski | Files touched by this commit (4) | Package updated
Log message:
Changes 5.1.72:
* InnoDB: The row_sel_sec_rec_is_for_clust_rec function would incorrectly \ 
prepare to compare a NULL column prefix in a secondary index with a non-NULL \ 
column in a clustered index.
* InnoDB: An incorrect purge would occur when rolling back an update to a \ 
delete-marked record.
* InnoDB: InnoDB would rename a user-defined foreign key constraint containing \ 
the string “_ibfk_” in its name, resulting in a duplicate constraint.
* InnoDB: Rolling back an INSERT after a failed BLOB write would result in an \ 
assertion failure. The assertion has been modified to allow NULL BLOB pointers \ 
if an error occurs during a BLOB write.
* InnoDB: The srv_master_thread background thread, which monitors server \ 
activity and performs activities such as page flushing when the server is \ 
inactive or in a shutdown state, runs on a one second delay loop. \ 
srv_master_thread would fail to check if the server is in a shutdown state \ 
before sleeping.
* InnoDB: An infinite loop could occur in buf_page_get_gen when handling \ 
compressed-only pages.
* Within a stored program, comparison of the value of a scalar subquery with an \ 
IN clause resulted in an error for the first execution and raised an assertion \ 
for the second execution.
* The my_strtoll10() function could incorrectly convert some long string-format \ 
numbers to numeric values and fail to set the overflow flag.
* For queries that accessed an INFORMATION_SCHEMA table in a subquery, and \ 
attempt to lock a mutex that had already been locked could cause a server crash.
* For DIV expressions, assignment of the result to multiple variables could \ 
cause a server crash.
* mysqldump wrote SET statements as SET OPTION, which failed when reloaded \ 
because the deprecated OPTION keyword has been removed from SET syntax.
* If one connection changed its default database and simultaneously another \ 
connection executed SHOW PROCESSLIST, the second connection could access invalid \ 
memory when attempting to display the first connection's default database. \ 
memory.
   2013-08-04 12:20:24 by Adam Ciarcinski | Files touched by this commit (8)
Log message:
Changes 5.1.71:

Functionality Added or Changed
* comp_err now checks to make sure that new errors are not being added to MySQL \ 
5.1 or 5.5 because the set of errors for these series is frozen.

Bugs Fixed
* InnoDB: During an insert buffer merge, InnoDB would invoke \ 
lock_rec_restore_from_page_infimum() on a potentially invalid record pointer.
* InnoDB: The page_zip_validate() consistency check would fail after compressing \ 
a page, in page_zip_compress(). This problem was caused by \ 
page_zip_decompress(), which would fail to set heap_no correctly when a record \ 
contained no user data bytes. A record with no user data bytes occurs when, for \ 
example, a primary key is an empty string and all secondary index fields are \ 
NULL or an empty string.
* InnoDB: The pthread_mutex, commit_threads_m, which was initialized but never \ 
used, has been removed from the code base.
* Partitioning: When dropping a partitioned table, the table's .par file was \ 
deleted first, before the table definition or data. This meant that, if the \ 
server failed during the drop operation, the table could be left in an \ 
inconsistent state in which it could neither be accessed nor dropped.
* Shared-compatibility conflict errors occurred for RPM install operations, even \ 
if no shared-compatibility RPMs were already installed.
* A user variable referenced during execution of a prepared statement is set to \ 
memory that is freed at the end of execution. A second execution of the \ 
statement could result in Valgrind warnings when accessing this memory.
* Misoptimization of left expressions in prepared statements could cause a \ 
server exit.
* Subsequent to Prepared statement needs to be re-prepared errors, inserts into \ 
DECIMAL columns caused a server exit.
* Assigning the result of a subquery to a user variable raised an assertion when \ 
the outer query included DISTINCT and GROUP BY.