mariadb

Tree: 2220fe2774

Author	SHA1	Message	Date
mskold/marty@mysql.com/linux.site	44e55e3b43	Bug #21072 Duplicate key error in NDB references wrong key: Re-wrote string usage to avoid valgrind warnings	19 years ago
mskold/marty@mysql.com/linux.site	240cd87dbf	Bug #21072 Duplicate key error in NDB references wrong key: use MAX_KEY to signal unknown key: Added string initialization	19 years ago
kaa@polly.local	456fe01d7e	Fix for bug #22728 "Handler_rollback value is growing". The bug is present only in 4.1, will be null-merged to 5.0 For InnoDB, check value of thd->transaction.all.innodb_active_trans instead of thd->transaction.stmt.innobase_tid to see if we really need to rollback.	19 years ago
mskold/marty@mysql.com/linux.site	c854ecebf9	Bug #21072 Duplicate key error in NDB references wrong key: wrong indent for code block	20 years ago
mskold/marty@mysql.com/linux.site	42d64e4275	Bug #21072 Duplicate key error in NDB references wrong key: use MAX_KEY to signal unknown key	20 years ago
ramil/ram@mysql.com/myoffice.izhnet.ru	b57efe738a	--{skip-}merge option added which allows the user to disable merge engine and to avoid the potential security problem. (see bug #15195: Security Breach with MERGE table)	20 years ago
msvensson@neptunus.(none)	9301123eb3	Bug #14514 Creating table with packed key fails silently - Backport from 5.0	20 years ago
tomas@poseidon.ndb.mysql.com	6ca09e8b8f	Bug #12055 NDB temp tables created by ALTER TABLE are usable - do not discover temporary files and make them visible	21 years ago
monty@mishka.local	7398252d02	Portability fixes Fixes while reviewing new pushed code NULL as argument to encrypt/decrypt should return NULL without a warning	21 years ago
msvensson@neptunus.(none)	4602b1809f	BUG10365 Cluster handler uses non-standard error code - Updated after review	21 years ago
msvensson@neptunus.(none)	8771c73258	BUG#10365 Cluster handler uses non-standard error codes - Added better error messages when trying to open a table that can't be discovered or unpacked. The most likely cause of this is that it does not have any frm data, probably since it has been created from NdbApi or is a NDB system table. - Separated functionality that was in ha_create_table_from_engine into two functions. One that checks if the table exists and another one that tries to create the table from the engine.	21 years ago
serg@serg.mylan	6a5349028c	a compiler must see '#pragma implementation' before '#pragma interface' (that comes with the #include'd header file)	21 years ago
monty@mysql.com	29fd1f2fd9	Move USE_PRAGMA_IMPLEMENTATION to proper place Ensure that 'null_value' is not accessed before val() is called in FIELD() functions Fixed initialization of key maps. This fixes some problems with keys when you have more than 64 keys Fixed that ROLLUP don't always create a temporary table. This fix ensures that func_gconcat.test results are now predictable	21 years ago
kent@mysql.com	bd48eed988	tztime.cc: Set #pragma implementation" earlier Many files: Need to include <my_global.h> before #ifdef USE_PRAGMA_IMPLEMENTATION	21 years ago
msvensson@neptunus.(none)	83d430353e	Add ifdefs to control when "#pragma implementation" should be used Added some more ifdefs for "#pragma interface"	21 years ago
msvensson@neptunus.(none)	9969e1c5ea	BUG#9911 After review fixes - Remove ha_archive::rename_table and move the fix to handler::rename_table	21 years ago
monty@mishka.local	8d919770c7	Fixed core dump with long timezone names Don't abort on bootstrap if a wrong --default-storage-engine is specified	21 years ago
jimw@mysql.com	6632ed5ce7	Check that the default storage engine is really available, and refuse to start up if it is not. (Bug #9815)	21 years ago
brian@zim.(none)	cfcedd85cd	Additional storage engine called "blackhole". Customer request, and for that matter a Zawodny request. With this you can alter table to a type of table that would never store data. Its a /dev/null for a database.	21 years ago
ingo@mysql.com	5ad151aa21	Test Bug: Memory leaks in the archive handler. Moved initialization code into a new init function. Added a new cleanup function. Added a call to close the meta file.	21 years ago
hf@deer.(none)	192715dbbb	Fix for bug #6516 (Server crash loading spatial data) (after discussion with SerG)	21 years ago
mats@mysql.com	2bbdf2403d	Bug#6391 (binlog-do-db rules ignored) CREATE DATABASE statement used the current database instead of the database created when checking conditions for replication. CREATE/DROP/ALTER DATABASE statements are now replicated based on the manipulated database.	21 years ago
serg@serg.mylan	41c33c29a3	Bug #6748 heap_rfirst() doesn't work (and never did!) range for BETWEEN typo fixed	21 years ago
guilhem@mysql.com	09da85338c	no new message in 4.1 (causes merge issues with 5.0). Using ER_UNKNOW_ERROR and hardcoded message string instead.	21 years ago
monty@mysql.com	68130e428a	Added possibility to detect if libmysqld is restarted (Needed to check if memory allocated with mysql_once_init() has been freed)	21 years ago
guilhem@mysql.com	6cd218cc56	WL#1596 "make mysqldump --master-data --single-transaction able to do online dump of InnoDB AND report reliable binlog coordinates corresponding to the dump". The good news is that now mysqldump can be used to get an online backup of InnoDB which works for point-in-time recovery and replication slave creation. Formerly, mysqldump --master-data --single-transaction used to call in fact mysqldump --master-data, so the dump was not an online dump (took big lock all time of dump). The only lock which is now taken in this patch is at the beginning of the dump: mysqldump does: FLUSH TABLES WITH READ LOCK; START TRANSACTION WITH CONSISTENT SNAPSHOT; SHOW MASTER STATUS; UNLOCK TABLES; so the lock time is in fact the time FLUSH TABLES WITH READ LOCK takes to return (can be 0 or very long, if a table is undergoing a huge update). I have done some more minor changes listed in the paragraph of mysqldump.c. WL#2237 "WITH CONSISTENT SNAPSHOT clause for START TRANSACTION": it's a START TRANSACTION which additionally starts a consistent read on all capable storage engine (i.e. InnoDB). So, can serve as a replacement for BEGIN; SELECT * FROM some_innodb_table LIMIT 1; which starts a consistent read too.	21 years ago
acurtis@pcgem.rdg.cyberkinetica.com	dd1cd8aa46	Bug#6031 - To drop database you have to execute DROP DATABASE command twice. DROP DATABASE failed because of file ext not in TYPELIB of known extensions. General solution - construct a TYPELIB at runtime instead of a static list.	21 years ago
guilhem@mysql.com	0517e7b22d	As rollback can be 30 times slower than insert in InnoDB, and user may not know there's rollback (if it's because of a dupl row), better warn that it's happening. It can also be of use for a DBA killing a connection and wondering what this connection is still doing now. Example: \| 5 \| root \| localhost \| test \| Killed \| 10 \| Rolling back \| insert into i select * from j \|	21 years ago
bar@mysql.com	217d83a69f	Bug#6202: ENUMs are not case sensitive even if declared BINARY	21 years ago
ingo@mysql.com	f32fb586c6	Fixed a typo, which prevented non-valgrind build.	21 years ago
monty@mishka.local	719c88e38f	true,false -> TRUE, FALSE Simple fixes/optimization of things discovered during review of new pushed code	21 years ago
monty@mysql.com	c27d22b44e	Reverted patch for new usage of open_count as it caused more problems than it solved Cleaned up patch for checking locks for multi-table updates	22 years ago
dlenev@brandersnatch.localdomain	2511990c97	Support for TIMESTAMP columns holding NULL values. Unlike all other column types TIMESTAMP is NOT NULL by default, so in order to have TIMESTAMP column holding NULL valaues you have to specify NULL as one of its attributes (this needed for backward compatibility). Main changes: Replaced TABLE::timestamp_default_now/on_update_now members with TABLE::timestamp_auto_set_type flag which is used everywhere for determining if we should auto-set value of TIMESTAMP field during this operation or not. We are also use Field_timestamp::set_time() instead of handler::update_timestamp() in handlers.	22 years ago
magnus@shellback.(none)	059941db21	WL#1424 Updated after review * Changed the implementation of ndbcluster_find_files to be more efficient, using only one mutex lock * Moved ha_find_files to end of mysql_find_files so that it can be passed the list that we are interested to find.	22 years ago
magnus@neptunus.(none)	0097c6d9b2	Changed WL#1424 to use the function ha_find_files. This is a simpler implementation and all handler specific code is hidden in the appropriate handler.	22 years ago
magnus@neptunus.(none)	8abbb28f8b	WL1424 Multiple MySQL Servers: SHOW TABLES etc. should detect new and delete old tables.	22 years ago
mskold@mysql.com	19a2eced82	Removed unnecessary condition	22 years ago
serg@serg.mylan	62c2f1c161	sql_print_error cleanup	22 years ago
tomas@poseidon.(none)	caf79dacfe	renamed ha_recovery_logging to ha_enable_transaction added tests to alter table for "large" alter tables and truncates in ndbcluster added debug printout in restart() in ndbcluster added flag THD::transaction.on to enable/disable transaction	22 years ago
serg@serg.mylan	326992430f	check for mysql_bin_log.is_open() before my_b_tell(&thd->transaction.trans_log in ha_commit_trans - why it didn't crash earlier ?	22 years ago
serg@serg.mylan	949348f576	after merge fix	22 years ago
guilhem@mysql.com	5db56a106b	Making FLUSH TABLES WITH READ LOCK block COMMITs of existing transactions, in a deadlock-free manner. This splits locking the global read lock in two steps. This fixes a consequence of this bug, known as: BUG#4953 'mysqldump --master-data may report incorrect binlog position if using InnoDB' And a test.	22 years ago
brian@avenger.(none)	1fe8b35bba	This is the addition of the CSV engine "aka tina". Its an example engine that works as a plain text file.	22 years ago
paul@ice.snake.net	e2d6d838e1	handler.cc: Revise output of SHOW ENGINES.	22 years ago
mskold@mysql.com	3f20e69c25	Fixed ndbcluster_print_error to use table name from failed NdbOperation	22 years ago
monty@mysql.com	f6765146c1	Added missing root user to mysql.user on windows. (Bug #4242 ) Set default max_allowed_packet to be able to read help tables even if an my.cnf file with this option is present. (Bug #3938) Don't use default arguments for ha_rnd_init() Simple code cleanups since last pull	22 years ago
mskold@mysql.com	29746be6a8	Cosmetic fixes	22 years ago
guilhem@mysql.com	d8fe091e28	Enabling the --innodb-safe-binlog option in code. If you wish to disable it, you just need to change this line of mysqld.cc: #if MYSQL_VERSION_ID >= 40103 to, say, #if MYSQL_VERSION_ID > 40103 I am noticing a failure of bdb.test; I believe this is not related to the code I added yesterday and today, but I am checking. In any case I push this changeset as it cannot by itself bring more mess that I may (or not) already have brought with previous pushes.	22 years ago
mskold@mysql.com	075d71d546	Modified index flags and added ndbcluster_print_error	22 years ago
guilhem@mysql.com	4a82bd4732	Final part of WL#1717 "innodb/binlog consistency". This is to resolve a limitation of yesterday's implementation: if there was an unfinished transaction (COMMIT not typed), and some MyISAM tables were then updated, and then mysqld crashes, then at restart the server would use the too old binlog offset known by InnoDB to cut the binlog, thus cutting the successful MyISAM updates. We fix this by reporting the binlog offset into InnoDB even if InnoDB was not affected at all by the update. But the feature is still disabled until we decide if it can go into 4.1.3.	22 years ago

1 2 3 4 5

226 Commits (2220fe2774bf2b041ba9894e33d23d2bf03a5df1)