mariadb

Tree: ee4d6b4fc0

Author	SHA1	Message	Date
mskold/marty@mysql.com/linux.site	6bac3b8f40	NDBAPI cleanup	19 years ago
brian@zim.(none)	baa914e66d	Cleanup of unused variables. Fixed "discover" in the handler API. Fixed problem where handlerton was not zero'ed. I need to look around, I suspect this problem is more widespread.	20 years ago
brian@zim.(none)	b518763728	This changest: Plugins now when compiled or not compiled work correctly with status variables. Status variables from plugins now set their own names (removed bit where plugin name was pre-appended this broke Innodb and Cluster) A few Makefile cleanups.	20 years ago
jonas@perch.ndb.mysql.com	a0bba5faef	correct merge	20 years ago
pekka@orca.ndb.mysql.com	9dc6087d4d	ndb - post-merge fix 5.0 to 5.0-ndb: number of frags if --without-big-tables	20 years ago
jonas@perch.ndb.mysql.com	a1420b1df8	merge	20 years ago
mskold/marty@mysql.com/linux.site	c8b93da355	Fix for bug #21059 Server crashes on join query with large dataset with NDB tables: do not release operation records for on-going read_multi_range	20 years ago
jonas@perch.ndb.mysql.com	3cd1826ef0	ndb - bug#20708 init ndb_cache_check_time and honor value in my.cnf	20 years ago
mskold/marty@mysql.com/linux.site	6a3143e2a0	ndb_lock.test, ndb_lock.result: bug #18184 SELECT ... FOR UPDATE does not work..: New test case ha_ndbcluster.h, ha_ndbcluster.cc, NdbConnection.hpp: Fix for bug #21059 Server crashes on join query with large dataset with NDB tables: Releasing operation for each intermediate batch, before next call to trans->execute(NoCommit);	20 years ago
mskold/marty@mysql.com/linux.site	2d16aa5796	ndb_lock.test, ndb_lock.result: bug #18184 SELECT ... FOR UPDATE does not work..: New test case ha_ndbcluster.h, ha_ndbcluster.cc, NdbConnection.hpp: Fix for bug #21059 Server crashes on join query with large dataset with NDB tables: Releasing operation for each intermediate batch, before next call to trans->execute(NoCommit);	20 years ago
justin.he@qa3-104.qa.cn.tlan	9d6de5c894	BUG#20848	20 years ago
justin.he@qa3-104.qa.cn.tlan	265b9cf6cd	BUG#20848 SHOW STATUS LIKE 'NDB%' should be data nodes not storage nodes use correct termninology	20 years ago
stewart@willster.(none)	9d2e6b8d23	BUG#19914 SELECT COUNT(*) sometimes returns MAX_INT on cluster tables allow handler::info to return an error code (that will be returned to the user)	20 years ago
mskold/marty@mysql.com/linux.site	a922e328af	bug #18184 SELECT ... FOR UPDATE does not work..: Added lockTuple call in close_scan	20 years ago
mskold/marty@mysql.com/linux.site	d7f8c331e1	Fix for bug #21059 Server crashes on join query with large dataset with NDB tables: Releasing operation for each intermediate batch, before next call to trans->execute(NoCommit);	20 years ago
mskold/marty@mysql.com/linux.site	3c61424563	Fix for bug #21059 Server crashes on join query with large dataset with NDB tables: Releasing operation for each intermediate batch, before next call to trans->execute(NoCommit);	20 years ago
ingo/istruewing@chilla.local	8e4c36ad4a	Bug#18775 - Temporary table from alter table visible to other threads Continued implementation of WL#1324 (table name to filename encoding) The intermediate (not temporary) files of the new table during ALTER TABLE was visible for SHOW TABLES. These intermediate files are copies of the original table with the changes done by ALTER TABLE. After all the data is copied over from the original table, these files are renamed to the original tables file names. So they are not temporary files. They persist after ALTER TABLE, but just with another name. In 5.0 the intermediate files are invisible for SHOW TABLES because all file names beginning with "#sql" were suppressed. This failed since 5.1.6 because even temporary table names were converted when making file names from them. The prefix became converted to "@0023sql". Converting the prefix during SHOW TABLES would suppress the listing of user tables that start with "#sql". The solution of the problem is to continue the implementation of the table name to file name conversion feature. One requirement is to suppress the conversion for temporary table names. This change is straightforward for real temporary tables as there is a function that creates temporary file names. But the generated path names are located in TMPDIR and have no relation to the internal table name. This cannot be used for ALTER TABLE. Its intermediate files need to be in the same directory as the old table files. And it is necessary to be able to deduce the same path from the same table name repeatedly. Consequently the intermediate table files must be handled like normal tables. Their internal names shall start with tmp_file_prefix (#sql) and they shall not be converted like normal table names. I added a flags parameter to all relevant functions that are called from ALTER TABLE. It is used to suppress the conversion for the intermediate table files. The outcome is that the suppression of #sql in SHOW TABLES works again. It does not suppress user tables as these are converted to @0023sql on file level. This patch does also fix ALTER TABLE ... RENAME, which could not rename a table with non-ASCII characters in its name. It does also fix the problem that a user could create a table like `#sql-xxxx-yyyy`, where xxxx is mysqld's pid and yyyy is the thread ID of some other thread, which prevented this thread from running ALTER TABLE. Some of the above problems are mentioned in Bug 1405, which can be closed with this patch. This patch does also contain some minor fixes for other forgotten conversions. Still known problems are reported as bugs 21370, 21373, and 21387.	20 years ago
kostja@bodhi.local	436e7a2dd9	Post-merge fixes.	20 years ago
guilhem@gbichot3.local	0594e1b84b	WL#3146 "less locking in auto_increment": this is a cleanup patch for our current auto_increment handling: new names for auto_increment variables in THD, new methods to manipulate them (see sql_class.h), some move into handler::, causing less backup/restore work when executing substatements. This makes the logic hopefully clearer, less work is is needed in mysql_insert(). By cleaning up, using different variables for different purposes (instead of one for 3 things...), we fix those bugs, which someone may want to fix in 5.0 too: BUG#20339 "stored procedure using LAST_INSERT_ID() does not replicate statement-based" BUG#20341 "stored function inserting into one auto_increment puts bad data in slave" BUG#19243 "wrong LAST_INSERT_ID() after ON DUPLICATE KEY UPDATE" (now if a row is updated, LAST_INSERT_ID() will return its id) and re-fixes: BUG#6880 "LAST_INSERT_ID() value changes during multi-row INSERT" (already fixed differently by Ramil in 4.1) Test of documented behaviour of mysql_insert_id() (there was no test). The behaviour changes introduced are: - LAST_INSERT_ID() now returns "the first autogenerated auto_increment value successfully inserted", instead of "the first autogenerated auto_increment value if any row was successfully inserted", see auto_increment.test. Same for mysql_insert_id(), see mysql_client_test.c. - LAST_INSERT_ID() returns the id of the updated row if ON DUPLICATE KEY UPDATE, see auto_increment.test. Same for mysql_insert_id(), see mysql_client_test.c. - LAST_INSERT_ID() does not change if no autogenerated value was successfully inserted (it used to then be 0), see auto_increment.test. - if in INSERT SELECT no autogenerated value was successfully inserted, mysql_insert_id() now returns the id of the last inserted row (it already did this for INSERT VALUES), see mysql_client_test.c. - if INSERT SELECT uses LAST_INSERT_ID(X), mysql_insert_id() now returns X (it already did this for INSERT VALUES), see mysql_client_test.c. - NDB now behaves like other engines wrt SET INSERT_ID: with INSERT IGNORE, the id passed in SET INSERT_ID is re-used until a row succeeds; SET INSERT_ID influences not only the first row now. Additionally, when unlocking a table we check that the thread is not keeping a next_insert_id (as the table is unlocked that id is potentially out-of-date); forgetting about this next_insert_id is done in a new handler::ha_release_auto_increment(). Finally we prepare for engines capable of reserving finite-length intervals of auto_increment values: we store such intervals in THD. The next step (to be done by the replication team in 5.1) is to read those intervals from THD and actually store them in the statement-based binary log. NDB will be a good engine to test that.	20 years ago
tomas@poseidon.ndb.mysql.com	4f7df01b4f	Bug #20843 tests fails randomly with assertion in completeClusterFailed Bug #20902 Alter table invalid schema version with statement-based binlogging (latter caused by the above)	20 years ago
tomas@poseidon.ndb.mysql.com	35938c56f3	Bug #20077 Cluster to only support partition by key, needs to error on others	20 years ago
tomas@poseidon.ndb.mysql.com	d3b52bd475	Bug #20077 Cluster to only support partition by key, needs to error on others	20 years ago
tomas@poseidon.ndb.mysql.com	98874725e0	Bug #20784 Uninitialized memory in update on table with PK not on first column - partial backport of code from 5.1, do cot compare_record for engines that do not read all columns during update	20 years ago
mskold@mysql.com	59d69f6d38	Fix for Bug #18413 Data usage for varsize columns are not correctly reported to mysqld	20 years ago
dlenev@mysql.com	d4450e6696	Fix for bug#18437 "Wrong values inserted with a before update trigger on NDB table". SQL-layer was not marking fields which were used in triggers as such. As result these fields were not always properly retrieved/stored by handler layer. So one might got wrong values or lost changes in triggers for NDB, Federated and possibly InnoDB tables. This fix solves the problem by marking fields used in triggers appropriately. Also this patch contains the following cleanup of ha_ndbcluster code: We no longer rely on reading LEX::sql_command value in handler in order to determine if we can enable optimization which allows us to handle REPLACE statement in more efficient way by doing replaces directly in write_row() method without reporting error to SQL-layer. Instead we rely on SQL-layer informing us whether this optimization applicable by calling handler::extra() method with HA_EXTRA_WRITE_CAN_REPLACE flag. As result we no longer apply this optimzation in cases when it should not be used (e.g. if we have on delete triggers on table) and use in some additional cases when it is applicable (e.g. for LOAD DATA REPLACE). Finally this patch includes fix for bug#20728 "REPLACE does not work correctly for NDB table with PK and unique index". This was yet another problem which was caused by improper field mark-up. During row replacement fields which weren't explicity used in REPLACE statement were not marked as fields to be saved (updated) so they have retained values from old row version. The fix is to mark all table fields as set for REPLACE statement. Note that in 5.1 we already solve this problem by notifying handler that it should save values from all fields only in case when real replacement happens.	20 years ago
monty@mysql.com	f62829636b	After merge fixes	20 years ago
tomas@poseidon.ndb.mysql.com	9f542ef0f4	adopted ndb handler code for tables without primary key and with unique index - added missing retrieval of hidden primary key	20 years ago
monty@mysql.com	a267b8f33c	Don't read ~/.my.cnf in mysqldump.test	20 years ago
monty@mysql.com	8eb9c06d70	Replaced assert with argument checking, as rpl_ndb_UUID caused slave to fail on x86 64 bit (It failed even if test was marked as skipped)	20 years ago
tomas@poseidon.ndb.mysql.com	5d67b05203	corrected merge error	20 years ago
tomas@poseidon.ndb.mysql.com	87460ec76a	Bug #19202 Incorrect errorhandling in select count(*) wrt temporary error	20 years ago
tomas@poseidon.ndb.mysql.com	9791d53445	partition functions to pass create_info, not only max_rows	20 years ago
stewart@mysql.com	bd54e6769b	BUG#20725 MySQLD cluster use "fast count" is broken fix based on review by tomas. conform to bug we haven't fixed yet.	20 years ago
stewart@mysql.com	bc91efe0ae	BUG#20725 MySQLD cluster use "fast count" is broken Post recent handler changes, fast count() for cluster was broken. Seeing as we maintain an exact count for ndb, we can easily use this for an optimisation. With this patch, and use_exact_count DISABLED, we will use the fast way of getting count() but not use the exact count for the optimiser. With this patch and use_exact_count ENABLED, we will use the fast way of getting count(*) and use the exact count for the optimiser.	20 years ago
tomas@poseidon.ndb.mysql.com	08bec7b954	changed signature of get_default_no_partitions	20 years ago
tomas@poseidon.ndb.mysql.com	18e008a1ba	Bug #19852 Restoring backup made from cluster with full data memory fails - correction of previous patch	20 years ago
tomas@poseidon.ndb.mysql.com	95447f9d1a	Bug #19852 Restoring backup made from cluster with full data memory fails - make sure to allocate just enough pages in the fragments by using the actual row count from the backup, to avoid over allocation of pages to fragments, and thus avoid the bug	20 years ago
stewart@mysql.com	78dd9d12bb	BUG#11459 ndb status variables not updated change names of some undocumented ndb status variables to better reflect what their values mean	20 years ago
jonas@perch.ndb.mysql.com	33339fdf40	ndb - bug#20053 make sure we can only drop files from correct file group	20 years ago
monty@mysql.com	649157954b	Fixed failure with rpl_truncate_7ndb.test when using statement based replication. is_injective -> table_flag() HA_HAS_OWN_BINLOGGING (Faster and easier to understand) Allow cluster_binlogging also in mixed replication mode.	20 years ago
jonas@perch.ndb.mysql.com	dc75269965	ndb - bug#16341 create tablespace/logfile group should "back out changes"	20 years ago
mskold@mysql.com	e77850e573	Fix for Bug #19906 REPLACE doesn't update TEXT fields correctly	20 years ago
stewart@mysql.com	917203ddd7	BUG#20073 information_schema.FILES for UNDO LOG give incorrect EXTENT_SIZE, FREE_EXTENTS,	20 years ago
monty@mysql.com	860661a2dc	unsigned char -> uchar Added missing copyright Indentation and prototype fixes Fixed compiler warning	20 years ago
knielsen@mysql.com	f8b1b46065	BUG#20498: Wrong usage of hash_first() in get_open_table(). The get_open_table() function was using the wrong key for hash lookups. This could potentially lead to unpredictable behaviour.	20 years ago
mikael@c-0409e253.1238-1-64736c10.cust.bredbandsbolaget.se	67e6e8b423	merge update	20 years ago
tomas@poseidon.ndb.mysql.com	47271c6bb1	Bug #19493 NDB does not ignore duplicate keys when using LOAD DATA LOCAL - correction of backport error	20 years ago
tomas@poseidon.ndb.mysql.com	2fcf737feb	Bug #19493 NDB does not ignore duplicate keys when using LOAD DATA LOCAL - make sure to disable bulk insert when check for duplicate key is needed	20 years ago
tomas@poseidon.ndb.mysql.com	2f6a4ad3c2	corrected merge error	20 years ago
tomas@poseidon.ndb.mysql.com	7e2323ed7e	Bug #18595 repeated create, insert, drop can cause MySQL table definition cache to corrupt - add infinite retry on drop table temporary error	20 years ago

... 2 3 4 5 6 ...

1290 Commits (ee4d6b4fc05139451a93162616d5473defb7b534)