mariadb

Tree: 69b789aafd

Author	SHA1	Message	Date
joerg@trift2.	69b789aafd	Merge trift2.:/MySQL/M50/mysql-5.0 into trift2.:/MySQL/M50/push-5.0	19 years ago
kostja@bodhi.(none)	d0dc51b4f7	Fix an unstable test. It was reliant on the current time.	19 years ago
kostja@bodhi.(none)	1bf318b895	Merge bk-internal.mysql.com:/home/bk/mysql-5.0 into bodhi.(none):/opt/local/work/mysql-5.0-runtime	19 years ago
kent@kent-amd64.(none)	01ad489356	Merge kboortz@bk-internal.mysql.com:/home/bk/mysql-5.0-build into mysql.com:/home/kent/bk/config_h/mysql-5.0-build	19 years ago
kent@mysql.com/kent-amd64.(none)	a9d2569cba	Generate "config.h" directly into the "include" directory, later copied to "my_config.h". Not to pollute the top directory, and to get more control over what is included. Made the include path for "libedit" pick up its own "config.h" first.	19 years ago
kent@kent-amd64.(none)	a0571dedb3	Merge mysql.com:/home/kent/bk/config_h/mysql-4.1-build into mysql.com:/home/kent/bk/config_h/mysql-5.0-build	19 years ago
kent@mysql.com/kent-amd64.(none)	e99df6fd02	my_pthread.c: Backport of correction for Mac OS X build problem, global variable not initiated is "common" and can't be used in shared libraries, unless special flags are used (bug#26218)	19 years ago
kent@kent-amd64.(none)	038357dd43	Merge kboortz@bk-internal.mysql.com:/home/bk/mysql-5.0-build into mysql.com:/home/kent/bk/tmp3/mysql-5.0-build	19 years ago
kostja@bodhi.(none)	80b48aea43	Fix a compilation warning.	19 years ago
joerg@trift2.	79a90dad8e	Merge trift2.:/MySQL/M50/mysql-5.0 into trift2.:/MySQL/M50/push-5.0	19 years ago
thek@adventure.(none)	64c5f996d1	Clean up patch - Removed unused variable.	19 years ago
jperkin@production.mysql.com	88ef9a4214	Merge jperkin@bk-internal.mysql.com:/home/bk/mysql-5.0-build into production.mysql.com:/usersnfs/jperkin/bk/mysql-5.0	19 years ago
jperkin@production.mysql.com	7731aad613	Merge jperkin@bk-internal.mysql.com:/home/bk/mysql-5.0-build into production.mysql.com:/usersnfs/jperkin/bk/mysql-5.0	19 years ago
kent@mysql.com/kent-amd64.(none)	519ebab04e	SSL/Makefile.am mysql-test/Makefile.am: Moved CERT files to where they are used, avoids conflict between two make files trying to install the same CERTs SSL/.pem, Move: SSL/.pem -> mysql-test/std_data/	19 years ago
thek@adventure.(none)	8f5fad2c34	Merge adventure.(none):/home/thek/Development/cpp/bug29929/my50-bug29929 into adventure.(none):/home/thek/Development/cpp/mysql-5.0-runtime	19 years ago
thek@adventure.(none)	889b4ebcee	Bug #29929 LOCK TABLES does not pre-lock tables used in triggers of the locked tables When a table was explicitly locked with LOCK TABLES no associated tables from any related trigger on the subject table were locked. As a result of this the user could experience unexpected locking behavior and statement failures similar to "failed: 1100: Table'xx' was not locked with LOCK TABLES". This patch fixes this problem by making sure triggers are pre-loaded on any statement if the subject table was explicitly locked with LOCK TABLES.	19 years ago
jperkin@production.mysql.com	d5293e4584	More fixes and cleanups for bug#28585: - make the 'dist-hook' from top-level Makefile work again. - we can find my_print_defaults from --basedir by parsing command line arguments prior to running my_print_defaults. - take advantage of additional command line parsing and allow the --no-defaults etc arguments to work anywhere rather than having to be the first argument. - find SQL files either from binary archive or source install. - consolidate and tidy code and error messages.	19 years ago
kostja@bodhi.(none)	11c57540f7	A fix and a test case for Bug#24918 drop table and lock / inconsistent between perm and temp tables. Review fixes. The original bug report complains that if we locked a temporary table with LOCK TABLES statement, we would not leave LOCK TABLES mode when this temporary table is dropped. Additionally, the bug was escalated when it was discovered than when a temporary transactional table that was previously locked with LOCK TABLES statement was dropped, futher actions with this table, such as UNLOCK TABLES, would lead to a crash. The problem originates from incomplete support of transactional temporary tables. When we added calls to handler::store_lock()/handler::external_lock() to operations that work with such tables, we only covered the normal server code flow and did not cover LOCK TABLES mode. In LOCK TABLES mode, ::external_lock(LOCK) would sometimes be called without matching ::external_lock(UNLOCK), e.g. when a transactional temporary table was dropped. Additionally, this table would be left in the list of LOCKed TABLES. The patch aims to address this inadequacy. Now, whenever an instance of 'handler' is destroyed, we assert that it was priorly external_lock(UNLOCK)-ed. All the places that violate this assert were fixed. This patch introduces no changes in behavior -- the discrepancy in behavior will be fixed when we start calling ::store_lock()/::external_lock() for all tables, regardless whether they are transactional or not, temporary or not.	19 years ago
svoj@june.mysql.com	81905ee14f	Merge svojtovich@bk-internal.mysql.com:/home/bk/mysql-5.0-engines into mysql.com:/home/svoj/devel/mysql/BUG29957/mysql-5.0-engines	19 years ago
svoj@mysql.com/june.mysql.com	9d1bfec265	BUG#29957 - alter_table.test fails INSERT/DELETE/UPDATE followed by ALTER TABLE within LOCK TABLES may cause table corruption on Windows. That happens because ALTER TABLE writes outdated shared state info into index file. Fixed by removing obsolete workaround. Affects MyISAM tables on Windows only.	19 years ago
joerg@debian.(none)	db5ad35ec9	Merge debian.(none):/M50/rowlock-5.0 into debian.(none):/M50/push-5.0	19 years ago
joerg@debian.(none)	1e455b4c28	Remove the "row_lock" suite from the sources. For more information, see WL#3866 and the bugs numbered 28685 and 20390.	19 years ago
acurtis/antony@ltamd64.xiphis.org	c2080430c3	Merge xiphis.org:/anubis/antony/work/mysql-5.0-engines into xiphis.org:/anubis/antony/work/mysql-5.0-engines.merge	19 years ago
joerg@debian.(none)	cb52840f13	Merge debian.(none):/M41/push-4.1 into debian.(none):/M50/push-5.0	19 years ago
joerg@debian.(none)	2a71b66517	Merge debian.(none):/M50/bug16635-5.0 into debian.(none):/M50/push-5.0	19 years ago
joerg@debian.(none)	1bf0b2f655	Merge debian.(none):/M50/mysql-5.0 into debian.(none):/M50/push-5.0	19 years ago
joerg@debian.(none)	c3264eaa0f	Merge debian.(none):/M41/bug16635-4.1 into debian.(none):/M41/push-4.1	19 years ago
joerg@debian.(none)	fa040bba06	Merge debian.(none):/M41/bug16635-4.1 into debian.(none):/M50/bug16635-5.0	19 years ago
jperkin@production.mysql.com	d2936fad10	mysql_install_db.sh: Fix error in previous change, correct --language argument.	19 years ago
jperkin@production.mysql.com	2c95b97787	Apply a few more cleanups to improve the robustness of mysql_install_db	19 years ago
jperkin@production.mysql.com	8f87bd6008	Clean up the mysql_install_db script to ensure that a sane environment is available and reduce the chance of failure. This should fix bug#28585 which is caused by the script being quite random in how it finds files it requires and not giving very good feedback to the user about what went wrong. Also update make_binary_distribution so that it provides the correct path to the required SQL scripts when generating mysql_install_db. The script only previously worked because of the permissive behaviour which looked around the current working directory before the "correct" location. This could lead to severe problems if the user happened to run the script from a location which contained older or even broken copies of the SQL scripts. We now require either a complete binary release (and the mysql_install_db script ran from inside the extracted archive), or an installed compiled tree, as this is the only way we can be sure everything that we need is available and ready to run. While working on this fix, also clean up the mysql_install_db script a lot to make it simpler, easier to read, and hopefully less prone to bugs in the future.	19 years ago
joerg@debian.(none)	560cad771a	Raise the 64 character limit for path names in the error messages to 150 or 107 characters for those messages which are generated by the embedded server during release builds. This fixes bug#16635: Error messages wrong: absolute path names, "%s" format code See the bug report or the changelog for "sql/share/english/errmsg.txt" for instructions how to do that with other languages, even at the customer site, and for the restrictions to keep.	19 years ago
acurtis/antony@xiphis.org/ltamd64.xiphis.org	2cc508b3f4	fix pushbuild failures	19 years ago
gshchepa/uchum@gleb.loc	bb22e3667e	Merge gleb.loc:/home/uchum/work/bk/5.0 into gleb.loc:/home/uchum/work/bk/5.0-opt	19 years ago
acurtis/antony@xiphis.org/ltamd64.xiphis.org	fbcd70a494	Bug#25679 "Federated Denial of Service" Federated storage engine used to attempt to open connections within the ::create() and ::open() methods which are invoked while LOCK_open mutex is being held by mysqld. As a result, no other client sessions can open tables while Federated is attempting to open a connection. Long DNS lookup times would stall mysqld's operation and a rogue connection string which connects to a remote server which simply stalls during handshake can stall mysqld for a much longer period of time. This patch moves the opening of the connection much later, when the federated actually issues queries, by which time the LOCK_open mutex is no longer being held.	19 years ago
gshchepa/uchum@gleb.loc	2c9eb1638b	Merge gleb.loc:/home/uchum/work/bk/4.1-opt into gleb.loc:/home/uchum/work/bk/5.0-opt	19 years ago
anozdrin/alik@ibm.	9f8593e81c	Patch inspired by BUG#10491: Server returns data as charset binary SHOW CREATE TABLE or SELECT FROM I_S. The problem is that mysqldump generates incorrect dump for a table with non-ASCII column name if the mysqldump's character set is ASCII. The fix is to: 1. Switch character_set_client for the mysqldump's connection to binary before issuing SHOW CREATE TABLE statement in order to avoid conversion. 2. Dump switch character_set_client statements to UTF8 and back for CREATE TABLE statement.	19 years ago
anozdrin/alik@ibm.	20e7e9870a	Allow mysql.proc to have extra (unknown) fields. This allows 5.0 to work with 5.1 databases.	19 years ago
malff/marcsql@weblab.(none)	0b1c6b90cc	Merge malff@bk-internal.mysql.com:/home/bk/mysql-5.0-runtime into weblab.(none):/home/marcsql/TREE/mysql-5.0-29959	19 years ago
omer@linux.site	ad0c033b84	Updated/fixed test and result files to 5.0.46 Note datadict files do not include wrong is_updatable wrong value as a result of bug 30020.	19 years ago
kostja@bodhi.(none)	4c208499a4	Merge bk-internal.mysql.com:/home/bk/mysql-5.0 into bodhi.(none):/opt/local/work/mysql-5.0-runtime	19 years ago
antony@pcg5ppc.xiphis.org	3f06084e7f	fix compile on Windows for bug25714.c --- fix compile on Windows for bug25714.c	19 years ago
antony@pcg5ppc.xiphis.org	c42837a232	build bug25714 test app on Windows	19 years ago
evgen@moonbone.local	fd1a43b080	Bug#15130: CREATE .. SELECT was denied to use advantages of the SQL_BIG_RESULT. When the SQL_BIG_RESULT flag is specified SELECT should store items from the select list in the filesort data and use them when sending to a client. The get_addon_fields function is responsible for creating necessary structures for that. But this function was allowed to do so only for SELECT and INSERT .. SELECT queries. This makes the SQL_BIG_RESULT useless for the CREATE .. SELECT queries. Now the get_addon_fields allows storing select list items in the filesort data for the CREATE .. SELECT queries.	19 years ago
acurtis/antony@ltamd64.xiphis.org	bfeb65d095	Merge xiphis.org:/anubis/antony/work/p2-bug25714.1 into xiphis.org:/anubis/antony/work/p2-bug25714.1.merge-5.0	19 years ago
antony@pcg5ppc.xiphis.org	6b38c5b762	Bug#25714 "getGeneratedKeys() does not work with FEDERATED table" mysql_insert() expected the storage engine to update the row data during the write_row() operation with the value of the new auto- increment field. The field must be updated when only one row has been inserted as mysql_insert() would ignore the thd->last_insert. This patch implements HA_STATUS_AUTO support in ha_federated::info() and ensures that ha_federated::write_row() does update the row's auto-increment value. The test case was written in C as the protocol's 'id' value is accessible through libmysqlclient and not via SQL statements. mysql-test-run.pl was extended to enable running the test binary.	19 years ago
malff/marcsql@weblab.(none)	e3a8215430	Bug#29959 (Non-standard bison syntax in sql_yacc.yy) In sql/sql_yacc.yy, use the %prec construct at the end of rule join_table	19 years ago
gkodinov/kgeorge@magare.gmz	33518801fb	Merge gkodinov@bk-internal.mysql.com:/home/bk/mysql-5.0-opt into magare.gmz:/home/kgeorge/mysql/autopush/B29644-5.0-opt	19 years ago
igor@olga.mysql.com	5ae1392cb0	Merge ibabaev@bk-internal.mysql.com:/home/bk/mysql-5.0-opt into olga.mysql.com:/home/igor/mysql-5.0-opt	19 years ago
gkodinov/kgeorge@magare.gmz	bc1a6ba954	table.cc, sql_select.cc: Limit the fix for bug 28591 to InnoDB only	19 years ago

1 2 3 4 5 ...

37360 Commits (69b789aafda958fbc89c15ff095235aa6b034d76) All Branches Search

37360 Commits (69b789aafda958fbc89c15ff095235aa6b034d76)

All Branches