mariadb

Tree: 5f4c6942bf

Author	SHA1	Message	Date
anozdrin/alik@quad.opbmk	814e2613b0	Fix tree: 1. Use 'dat' extension, because it is handled in Makefile.am; 2. Fix typo: the bug id is 35469, not 35649.	18 years ago
anozdrin/alik@quad.opbmk	2880d2081e	Fix for Bug#35469: server crash with LOAD DATA INFILE to a VIEW. The problem was that LOAD DATA code (sql_load.cc) didn't take into account that there may be items, representing references to other columns. This is a usual case in views. The crash happened because Item_direct_view_ref was casted to Item_user_var_as_out_param, which is not a base class. The fix is to 1) Handle references properly; 2) Ensure that an item is treated as a user variable only when it is a user variable indeed; 3) Report an error if LOAD DATA is used to load data into non-updatable column.	18 years ago
hezx@mail.hezx.com	a3d02647e6	BUG#33029 5.0 to 5.1 replication fails on dup key when inserting using a trig in SP For all 5.0 and up to 5.1.12 exclusive, when a stored routine or trigger caused an INSERT into an AUTO_INCREMENT column, the generated AUTO_INCREMENT value should not be written into the binary log, which means if a statement does not generate AUTO_INCREMENT value itself, there will be no Intvar event (SET INSERT_ID) associated with it even if one of the stored routine or trigger caused generation of such a value. And meanwhile, when executing a stored routine or trigger, it would ignore the INSERT_ID value even if there is a INSERT_ID value available set by a SET INSERT_ID statement. Starting from MySQL 5.1.12, the generated AUTO_INCREMENT value is written into the binary log, and the value will be used if available when executing the stored routine or trigger. Prior fix of this bug in MySQL 5.0 and prior MySQL 5.1.12 (referenced as the buggy versions in the text below), when a statement that generates AUTO_INCREMENT value by the top statement was executed in the body of a SP, all statements in the SP after this statement would be treated as if they had generated AUTO_INCREMENT by the top statement. When a statement that did not generate AUTO_INCREMENT value by the top statement but by a function/trigger called by it, an erroneous Intvar event would be associated with the statement, this erroneous INSERT_ID value wouldn't cause problem when replicating between masters and slaves of 5.0.x or prior 5.1.12, because the erroneous INSERT_ID value was not used when executing functions/triggers. But when replicating from buggy versions to 5.1.12 or newer, which will use the INSERT_ID value in functions/triggers, the erroneous value will be used, which would cause duplicate entry error and cause the slave to stop. The patch for 5.1 fixed it to ignore the SET INSERT_ID value when executing functions/triggers if it is replicating from a master of buggy versions, another patch for 5.0 fixed it not to generate the erroneous Intvar event.	18 years ago
aelkin/elkin@koti.dsl.inet.fi	c5b597bc89	bug#30435 changes due to non-determinism in value of read_buffer_size.	18 years ago
msvensson@pilot.mysql.com	d918988baa	WL#4189 - dynamic configuration support - safe process - cleanups - create new suite for fedarated	18 years ago
mats@capulet.net	a432d3dec4	BUG#31793 (log event corruption causes crash): When running mysqlbinlog on a 64-bit machine with a corrupt relay log, it causes mysqlbinlog to crash. In this case, the crash is caused because a request for 18446744073709534806U bytes is issued, which apparantly can be served on a 64-bit machine (speculatively, I assume) but this causes the memcpy() issued later to copy the data to segfault. The request for the number of bytes is caused by a computation of data_len - server_vars_len where server_vars_len is corrupt in such a sense that it is > data_len. This causes a wrap-around, with the the data_len given above. This patch adds a check that if server_vars_len is greater than data_len before the substraction, and aborts reading the event in that case marking the event as invalid. It also adds checks to see that reading the server variables does not go outside the bounds of the available space, giving a limited amount of integrity check.	18 years ago
lzhou/zhl@dev3-63.(none)	53c2c7fa3f	BUG#27543 Backup and restore can compatible with different endians for blob attribute	19 years ago
tsmith@ramayana.hindu.god	220cd12f0b	Fixes for the following bugs: Bug #30316: Some "parts" tests fail because the server uses "--secure-file-priv" Bug #30341: Test suite "parts" needs to be adapted to the new rules disallowing many functio Bug #30408: Suite "parts" needs bug numbers updated Bug #30411: Suite "parts" needs bug numbers updated: ER_UNIQUE_KEY_NEED_ALL_FIELDS_IN_PF Bug #30576: part_supported_sql_func_innodb.test tries to LOAD DATA outside of var dir Bug #30581: partition_value tests use disallowed CAST() function Included are some general fixes to allow the "parts" test suite to be run successfully. This includes disabling a few tests or parts of tests, cleaning up the test cases and their results, etc. Basically, these tests have not been run for some time, and had suffered some bit rot. The bugs were fixed as a single changeset, because in some ways they depend on each other. I couldn't be sure I'd updated all the error codes (for bugs 30408 and 30411) without also adapting to the new allowed functions rules (bug 30341), and vice versa.	19 years ago
gni@dev3-221.dev.cn.tlan	badda4b7b6	BUG#22240 Add a test case into ndb_restore_compat	19 years ago
lzhou/zhl@dev3-63.(none)	2b2d7c1920	Remove the extra files for the bug29674 exist only in 5.0	19 years ago
lzhou/zhl@dev3-63.(none)	cbe2a3c780	BUG#29674 Restore/backup are endian compatible in 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
gni@dev3-221.dev.cn.tlan	2997e6f432	BUG#22240 Upgrading from cluster 5.0 to 5.1 does not resize VARCHARS as expected. add varchar type restoring test from 5.0 backup into 5.1	19 years ago
dkatz@damien-katzs-computer.local	491d945ab6	Bug #29784 YaSSL assertion failure when reading 8k key. Fixed the yassl base64 decoding to correctly allocate a maximum decoded buffer size.	19 years ago
bar@mysql.com/bar.myoffice.izhnet.ru	d3c4f1b22b	Bug#28916 LDML doesn't work for utf8 and is not described in the manual - Adding missing initialization for utf8 collations - Minor code clean-ups: renaming variables, moving code into a new separate function. - Adding test, to check that both ucs2 and utf8 user defined collations work (ucs2_test_ci and utf8_test_ci) - Adding Vietnamese collation as a complex user defined collation example.	19 years ago
bar@mysql.com	dd0c43d5fa	Bug#15126 character_set_database is not replicated (LOAD DATA INFILE need it) This patch fixes problem that LOAD DATA could use different character sets when loading files on master and on slave sides: - Adding replication of thd->variables.collation_database - Adding optional character set clause into LOAD DATA Note, the second way, with explicit CHARACTER SET clause should be the recommended way to load data using an alternative character set. The old way, using "SET @@character_set_database=xxx" should be gradually depricated.	19 years ago
thek@kpdesk.mysql.com	19dfc42eb6	Bug#23240 --init_file statements with NOW() reports '1970-01-01 11:00:00'as the date time - Starting time of a query sent by bootstrapping wasn't initialized and starting time defaulted to 0. This later used value by NOW- item and was translated to 1970-01-01 11:00:00. - Marketing the time with thd->set_time() before the call to mysql_parse resolves this issue. - set_time was refactored to be part of the thd->init_for_queries- process.	19 years ago
thek@kpdesk.mysql.com	dd41fd5732	Bug#23240 --init-file statements with NOW() reports '1970-01-01 11:00:00'as the date time - Starting time of a query sent by file bootstrapping wasn't initialized and starting time defaulted to 0. This later used value by the Now- item and is translated to 1970-01-01 11:00:00. - marking the time with thd->set_time() before the call to mysql_parse resolves this issue.	19 years ago
holyfoot/hf@mysql.com/deer.(none)	f404488d29	bug #22372 datafile added to be used in gis.test	19 years ago
monty@mysql.com/nosik.monty.fi	f6682e2743	Added --debug-info to most clients to detect memory leaks in mysql-test-run Moved .progress files into the log directory Moved 'cluster' database tables into the MySQL database, to not have 'cluster' beeing a reserved database name Fixed bug where mysqld got a core dump when trying to use a table created by MySQL 3.23 Fixed some compiler warnings Fixed small memory leak in libmysql Note that this doesn't changeset doesn't include the new mysqldump.c code required to run some tests. This will be added when I merge 5.0 to 5.1	19 years ago
msvensson@neptunus.(none)	4c26bf9c1d	Bug#19371 VARBINARY() have trailing zeros after upgrade from 4.1 - Detect if a table has field of type MYSQL_TYPE_VAR_STRING while running "CHECK TABLE t FOR UPGRADE" and indicate it need to be fixed with "REPAIR TABLE t". - When running a "REPAIR TABLE t" or "ALTER TABLE t FORCE" on the above table, install a special copy function to trim off the trailing spaces which we safely can say that the pre 5.0 mysqld didn't put there.	19 years ago
msvensson@neptunus.(none)	458df10d85	Bug#21868 Server crashes if encrypted certificate key provided - Add test case which runs the same tests as ssl.test but with a different DES encrypted key	20 years ago
kostja@bodhi.local	3bf609b7f2	A fix for Bug#14897 "ResultSet.getString("table.column") sometimes doesn't find the column" When a user was using 4.1 tables with VARCHAR column and 5.0 server and a query that used a temporary table to resolve itself, the table metadata for the varchar column sent to client was incorrect: MYSQL_FIELD::table member was empty. The bug was caused by implicit "upgrade" from old VARCHAR to new VARCHAR hard-coded in Field::new_field, which did not preserve the information about the original table. Thus, the field metadata of the "upgraded" field pointed to an auxiliary temporary table created for query execution. The fix is to copy the pointer to the original table to the new field.	20 years ago
konstantin@mysql.com	b99e11c8bd	A fix and a test case for Bug#17843 "Certain stored procedures fail to run at startup" The server returned an error when trying to execute init-file with a stored procedure that could return multiple result sets to the client. A stored procedure can return multiple result sets if it contains PREPARE, SELECT, SHOW and similar statements. The fix is to set client_capabilites\|=CLIENT_MULTI_RESULTS in sql_parse.cc:handle_bootstrap(). There is no "client" really, so nothing is ever sent. This makes init-file feature behave consistently: the prepared statements that can be called directly in the init-file can be used in a stored procedure too. Re-committed the patch originally submitted by Per-Erik after review.	20 years ago
msvensson@neptunus.(none)	22ff4c2865	Bug#15328 Segmentation fault occured if my.cnf is invalid for escape sequence - Check that length of value is longer than 1 before decrementing length by 2. - Backport from 5.0, make it possible to use my_print_defaults in tests	20 years ago
msvensson@neptunus.(none)	f0ac0fdf06	Add an untrusted cacert used when testing	20 years ago
tomas@poseidon.ndb.mysql.com	3d8c52615f	modified ndb backup/restore to be byte order independant - the replica info was not stored in byte order indepentent format - backup/restore still compatible 5.0->5.1 - but patch makes previous 5.1 versions completely incompatible	20 years ago
tomas@poseidon.ndb.mysql.com	1fbac122de	added missing files	20 years ago
tomas@poseidon.ndb.mysql.com	424a2a7f8d	added missing files	20 years ago
tomas@poseidon.ndb.mysql.com	cc138b5a3b	Bug#18594 ndb_restore log boken in 5.1 - added compatability with 5.0 - added test case for compatability with 5.0 and 5.1	20 years ago
jimw@mysql.com	276109b155	Remove old cruft from the tree: mysqltestmanager, mysql_test_run_new, and various stuff in Docs/. Also move the certificates used for testing into mysql-test/std_data from the top-level SSL directory (now gone).	20 years ago
anozdrin@mysql.com	e03e522201	Fix for BUG#16266: Definer is not fully qualified error during replication. The idea of the fix is to extend support of non-SUID triggers for backward compatibility. Formerly non-SUID triggers were appeared when "new" server is being started against "old" database. Now, they are also created when "new" slave receives updates from "old" master.	20 years ago
lars@mysql.com	ad126d90e0	WL#1012: All changes as one single changeset. This includes both code and test cases.	20 years ago
tomas@poseidon.ndb.mysql.com	fd0cd55652	Bug #13009 No gaps allowed in node id number sequence + some small bugfixes in ndb_config + extending ndb_config to print connections and take shm option	20 years ago
jonas@perch.ndb.mysql.com	6cff2db932	ndb Add support/test for using my.cnf [cluster_config]	21 years ago
mats@mysql.com	6d924c8286	Bug#11401: Setting thd->lex so that engines (i.e., InnoDB) recognizes this as a LOAD DATA ... REPLACE INTO .. statement.	21 years ago
jimw@mysql.com	dab880274a	Fix LOAD DATA to handle having the escape and enclosed-by character be the same. (Bug #11203)	21 years ago
gbichot@quadita2.mysql.com	7b0e872695	testing repl of timezone with LOAD DATA INFILE (hourra!)	21 years ago
dlenev@brandersnatch.localdomain	f169114042	WL#874 "Extended LOAD DATA". Now one can use user variables as target for data loaded from file (besides table's columns). Also LOAD DATA got new SET-clause in which one can specify values for table columns as expressions. For example the following is possible: LOAD DATA INFILE 'words.dat' INTO TABLE t1 (a, @b) SET c = @b + 1; This patch also implements new way of replicating LOAD DATA. Now we do it similarly to other queries. We store LOAD DATA query in new Execute_load_query event (which is last in the sequence of events representing LOAD DATA). When we are executing this event we simply rewrite part of query which holds name of file (we use name of temporary file) and then execute it as usual query. In the beggining of this sequence we use Begin_load_query event which is almost identical to Append_file event	21 years ago
serg@serg.mylan	24dcb103f3	fix rpl_trunc_binlog to test the new behaviour	21 years ago
monty@mysql.com	563500994a	Update results for new varchar handling Fixed compiler warnings String results in CREATE ... SELECT are now created as CHAR(0), VARCHAR(X) or TEXT() depending on item->max_length	21 years ago
dlenev@mysql.com	fa21feda93	Fix for bug #6387 "Queried timestamp values do not match the inserted value if server runs in time zone with leap seconds". Now in my_gmt_sec() function we take into account difference between our target and estimation in seconds part.	21 years ago
serg@sergbook.mylan	606073084e	symlink, not hardlink mkdir in Makefile, not in configure chmod a-x	22 years ago
lenz@mysql.com	e306876fe1	- renamed mysql-test/t/init_file.sql to mysql-test/std_data/init_file.dat so it gets picked up by "make dist" and updated init_file test accordingly.	22 years ago
monty@mysql.com	d47deebb58	Extend max_allowed_packet to 2G in mysql and mysqldump (Bug #2105 ) Don't dump data for MRG_ISAM or MRG_MYISAM tables. (Bug #1846) Ensure that 'lower_case_table_names' is always set on case insensitive file systems. (Bug #1812) One can now configure MySQL as windows service as a normal user. (Bug #1802) Database names is now compared with lower case in ON clause when lower_case_table_names is set. (Bug #1736) IGNORE ... LINES option didn't work when used with fixed length rows. (Bug #1704) Change INSERT DELAYED ... SELECT... to INSERT .... SELECT (Bug #1983) Safety fix for service 'mysql start' (Bug #1815)	22 years ago
monty@narttu.mysql.fi	d9ff665102	Fixes after merge	23 years ago
guilhem@mysql.com	52ae1609eb	When the I/O thread was stopped while copying a long transaction, and restarted, Rotate_log_event::exec_event() believed that the relay log was corrupted. Fixed it by moving the test for corruption to Start_log_event::exec_event(). Changed Rotate_log_event::exec_event() to not increment positions when the event is seen in the middle of a transaction. I did a separate commit in 4.1 (so this should not be merged to 4.0) because code is a bit different in 4.1. A test to see if the slave detects when the master died while writing a transaction to the binlog (uses a forged truncated binlog I made).	23 years ago
guilhem@mysql.com	9854acae25	Fix for BUG#1391: "If LOAD DATA INFILE 'small_file' fails on master, slave leaves temp files" (the bug is in the master)	23 years ago
monty@narttu.mysql.fi	efa85aad49	Move test that uses many tables (in query_cache.test) to separate test so that we can get it 'skipped' instead of 'failed' on system where we can't open many files.	23 years ago
vva@eagle.mysql.r18.ru	09348e271a	fixed 'STARTING BY' in replication	23 years ago

1 2 3 4

199 Commits (5f4c6942bfc6b88a8e934decfcf2f991bce6628e)