| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
| |
columns (default datatype value is assigned).
The mysql_update function has been modified to generate
an error when trying to set a NOT NULL field to NULL rather than a warning
in the set_field_to_null_with_conversions function.
|
| | |
|
| |\
| |
| |
| | |
into mysql.com:/home/gluh/MySQL/Merge/5.1-opt
|
| | |\
| | |
| | |
| | | |
into mysql.com:/misc/mysql/31177/51-31177
|
| | | |
| | |
| | |
| | | |
fixes for SLES10
|
| | |\ \
| | |/
| |/|
| | | |
into mysql.com:/home/hf/work/26921/my51-26921
|
| | | |\
| | | |
| | | |
| | | | |
into mysql.com:/home/hf/work/26921/my51-26921
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
client library only sets mysql->insert_id when query returned
no recordset. So the embedded library should behave the same way
|
| | |\ \ \
| | |/ /
| |/| |
| | | | |
into mysql.com:/home/hf/work/mrg/my51-mrg
|
| | | |/
| | |
| | |
| | |
| | |
| | | |
server status wasn't properly sent to the client after the error
by the embedded server. Wasn't noticed before as one usually stopped
retrieving results after he gets an error.
|
| | | |\
| | | |
| | | |
| | | | |
into polly.(none):/home/kaa/src/opt/mysql-5.0-opt
|
| | |\ \ \
| | | | |
| | | | |
| | | | | |
into magare.gmz:/home/kgeorge/mysql/work/B32400-5.1-opt
|
| | | |/ /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
only on some occasions
Referencing an element from the SELECT list in a WHERE
clause is not permitted. The namespace of the WHERE
clause is the table columns only. This was not enforced
correctly when resolving outer references in sub-queries.
Fixed by not allowing references to aliases in a
sub-query in WHERE.
|
| | |\ \ \
| | | | |
| | | | |
| | | | | |
into polly.(none):/home/kaa/src/opt/mysql-5.1-opt
|
| | | |\ \ \
| | | | |/
| | | |/|
| | | | | |
into polly.(none):/home/kaa/src/opt/bug32221/my51-bug31445
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
crashes.
MySQL distributions contain a number of programs that are used only by
the MySQL test suite internally, i.e. they are not indended to be
invoked directly by a user. As a result, such programs are not
documented, do not have any built-in help or proper error reporting,
which may confuse users.
This patch fixes the problem with the following changes:
- mytest, libmysqltest and all references to them were removed from the
distribution since they are not used anymore
- bug25714 now displays an error message when run with incorrect
arguments or with the --help option
- mysql_client_test now does not call abort() in case of errors,
instead it does a clean exit() with a proper error status.
|
| |\ \ \ \ \
| |/ / / /
| | | | |
| | | | | |
into janus.mylan:/usr/home/serg/Abk/mysql-5.1
|
| | |\ \ \ \
| | | | | |
| | | | | |
| | | | | | |
into mysql.com:/home/gluh/MySQL/Merge/5.1-opt
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
command and reported to a client.
The fact that a timestamp field will be set to NO on UPDATE wasn't shown
by the SHOW COMMAND and reported to a client through connectors. This led to
problems in the ODBC connector and might lead to a user confusion.
A new filed flag called ON_UPDATE_NOW_FLAG is added.
Constructors of the Field_timestamp set it when a field should be set to NOW
on UPDATE.
The get_schema_column_record function now reports whether a timestamp field
will be set to NOW on UPDATE.
|
| | | | | | | |
|
| | |\ \ \ \ \
| | |/ / / /
| |/| | | /
| | | |_|/
| | |/| | |
into endora.local:/Users/davi/mysql/bugs/31669-5.1
|
| | | |\ \ \
| | | | | |
| | | | | |
| | | | | | |
into moksha.local:/Users/davi/mysql/mysql-5.0-runtime
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
The problem is that when copying the supplied username and
database, no bounds checking is performed on the fixed-length
buffer. A sufficiently large (> 512) user string can easily
cause stack corruption. Since this API can be used from PHP
and other programs, this is a serious problem.
The solution is to increase the buffer size to the accepted
size in similar functions and perform bounds checking when
copying the username and database.
|
| | | |\ \ \ \
| | | |/ / /
| | |/| | /
| | | | |/
| | | |/| |
into mysql.com:/home/gluh/MySQL/Merge/5.0-opt
|
| | | |\ \ \
| | | | | |
| | | | | |
| | | | | | |
into mysql.com:/home/tnurnberg/15327/50-15327
|
| |\ \ \ \ \ \
| |/ / / / /
|/| | | | |
| | | | | | |
into janus.mylan:/usr/home/serg/Abk/mysql-5.1
|
| | |\ \ \ \ \
| | | | | | |
| | | | | | |
| | | | | | | |
into janus.mylan:/usr/home/serg/Abk/mysql-5.1
|
| | |\ \ \ \ \ \
| | | | | | | |
| | | | | | | |
| | | | | | | | |
into janus.mylan:/usr/home/serg/Abk/mysql-5.1
|
| | | | | | | | | |
|
| | |\ \ \ \ \ \ \
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
into pippilotta.erinye.com:/shared/home/df/mysql/build/mysql-5.1-build
|
| |\ \ \ \ \ \ \ \ \
| |_|_|_|/ / / / /
|/| | | | | | | /
| | |_|_|_|_|_|/
| |/| | | | | | |
into mysql.com:/home/gluh/MySQL/Merge/5.1-opt
|
| | |\ \ \ \ \ \ \
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
into mysql.com:/home/gluh/MySQL/Merge/5.1-opt
|
| | | |\ \ \ \ \ \ \
| | | | |_|_|_|_|/
| | | |/| | | | |
| | | | | | | | | |
into mysql.com:/home/gluh/MySQL/Merge/5.1-opt
|
| | |\ \ \ \ \ \ \ \
| | |/ / / / / / /
| |/| / / / / / /
| | |/ / / / / / |
|
| | | |\ \ \ \ \ \
| | | |_|_|_|/ /
| | |/| | | | |
| | | | | | | | |
into moonbone.local:/work/27990-bug-5.0-opt-mysql
|
| | | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
The change_to_use_tmp_fields function leaves the orig_table member of an
expression's tmp table field filled for the new Item_field being created.
Later orig_table is used by the Field::make_field function to provide some
info about original table and field name to a user. This is ok for a field
but for an expression it should be empty.
The change_to_use_tmp_fields function now resets orig_table member of
an expression's tmp table field to prevent providing a wrong info to a user.
The Field::make_field function now resets the table_name and the org_col_name
variables when the orig_table is set to 0.
|
| | | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
Post fix for the bug#29948.
|
| | | |\ \ \ \ \ \
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
into moonbone.local:/mnt/gentoo64/work/29948-bug-5.0-opt-mysql
|
| | | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
The cli_read_binary_rows function is used to fetch data from the server
after a prepared statement execution. It accepts a statement handler and gets
the connection handler from it. But when the auto-reconnect option is set
the connection handler is reset to NULL after reconnection because the
prepared statement is lost and the handler became useless. This case
wasn't checked in the cli_read_binary_rows function and caused server crash.
Now the cli_read_binary_rows function checks the connection handler to be
not NULL and returns an error if it is.
|
| |\ \ \ \ \ \ \ \ \
| | |_|_|_|_|_|/ /
| |/| | | | | | |
| | | | | | | | | |
into lambda.hsd1.co.comcast.net.:/home/malff/TREE/mysql-5.1-rt-merge
|
| | |\ \ \ \ \ \ \ \
| | |/ / / / / / /
| |/| | | | | | |
| | | | | | | | | |
into mysql.com:/home/tnurnberg/15327/51-15327
|
| | | |\ \ \ \ \ \ \
| | | | |_|_|_|_|/
| | | |/| | | | |
| | | | | | | | | |
into mysql.com:/home/tnurnberg/15327/51-15327
|
| | | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
make sure that if builder configured with a non-standard (!= 3306)
default TCP port that value actually gets used throughout. if they
didn't configure a value, assume "use a sensible default", which
will be read from /etc/services or, failing that, from the factory
default. That makes the order of preference
- command-line option
- my.cnf, where applicable
- $MYSQL_TCP_PORT environment variable
- /etc/services (unless configured --with-tcp-port)
- default port (--with-tcp-port=... or factory default)
|
| | | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
mysql_change_user().
The problem was that THD::ull was not reset in THD::cleanup().
The fix is to reset it.
|
| | | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
of SQL_BIG_SELECTS.
The bug was that SQL_BIG_SELECTS was not properly set
in COM_CHANGE_USER.
The fix is to update SQL_BIG_SELECTS properly.
|
| | | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
insert_id after succ. mysql_change_user() call.
See also WL 4066.
This bug reveals two problems:
- the problem on the client side which was described originally;
- the problem in protocol / the server side: connection context
on client and server should be like after mysql_real_connect()
and be consistent. The server however just resets character
set variables to the global defaults.
The fix seems to be as follows:
- extend the protocol so that the client be able to send
character set information in COM_CHANGE_USER command;
- change the server so that it understands client character set
in the command;
- change the client:
- reset character set to the default value (which has been
read from the configuration);
- send character set in COM_CHANGE_USER command.
|
| |/ / / / / / / /
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
insert_id after succ. mysql_change_user() call.
Supply a correct packet length to dispatch command.
|
| |\ \ \ \ \ \ \ \
| |_|_|_|_|_|/ /
|/| | | | | | /
| | |_|_|_|_|/
| |/| | | | | |
into a88-113-38-195.elisa-laajakaista.fi:/home/my/bk/mysql-5.1-marvel
|
| | | | | | | | |
|
| |\ \ \ \ \ \ \
| |/ / / / / /
|/| | | | | |
| | | | | | | |
into mysql.com:/home/my/mysql-5.1
|
