An error occurred fetching the project authors.
- 04 Oct, 2004 1 commit
-
-
dlenev@brandersnatch.localdomain authored
treated as DEFAULT NULL columns (independently from their position in table). (still to be discussed with Monty, Brian, Trudy et al. before push)
-
- 01 Oct, 2004 1 commit
-
-
dlenev@brandersnatch.localdomain authored
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.
-
- 16 Sep, 2004 1 commit
-
-
bell@sanja.is.com.ua authored
-
- 13 Sep, 2004 1 commit
-
-
serg@serg.mylan authored
-
- 10 Sep, 2004 1 commit
-
-
ingo@mysql.com authored
Added code to adjust the field_length of user variables in dependence on the field type. Aded new constants for numeric field widths.
-
- 08 Sep, 2004 1 commit
-
-
bell@sanja.is.com.ua authored
-
- 04 Sep, 2004 1 commit
-
-
serg@serg.mylan authored
-
- 31 Aug, 2004 1 commit
-
-
bell@sanja.is.com.ua authored
-
- 27 Aug, 2004 1 commit
-
-
ram@gw.mysql.r18.ru authored
-
- 25 Aug, 2004 1 commit
-
-
monty@mysql.com authored
Update to new valgrind
-
- 24 Aug, 2004 1 commit
-
-
konstantin@mysql.com authored
execute crashes server": we were deleting lex->result after each execute, but prepared statements assumed that it's left intact. The fix adds cleanup() method to select_result hierarchy, so that result objects can be reused. Plus we now need to delete result objects more wisely.
-
- 20 Aug, 2004 2 commits
-
-
konstantin@mysql.com authored
a second time". The bug was caused by incompatibility of negations elimination algorithm and PS: during first statement execute a subtree with negation was replaced with equivalent subtree without NOTs. The problem was that although this transformation was permanent, items of the new subtree were created in execute-local memory. The patch adds means to check if it is the first execute of a prepared statement, and if this is the case, to allocate items in memory of the prepared statement. The implementation: - backports Item_arena from 5.0 - adds Item_arena::is_stmt_prepare(), Item_arena::is_first_stmt_execute(). - deletes THD::allocate_temporary_pool_for_ps_preparing(), THD::free_temporary_pool_for_ps_preparing(); they were redundant. and adds a few invariants: - thd->free_list never contains junk (= freed items) - thd->current_arena is never null. If there is no prepared statement, it points at the thd. The rest of the patch contains mainly mechanical changes and cleanups.
-
guilhem@mysql.com authored
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.
-
- 19 Aug, 2004 2 commits
-
-
guilhem@mysql.com authored
Fix for BUG#4971 "CREATE TABLE ... TYPE=HEAP SELECT ... stops slave (wrong DELETE in binlog)": replacing the no_log argument of mysql_create_table() by some safer method (temporarily setting OPTION_BIN_LOG to 0) which guarantees that even the automatic DELETE FROM heap_table does not get into the binlog when a not-yet-existing HEAP table is opened by mysql_create_table().
-
pem@mysql.comhem.se authored
-
- 18 Aug, 2004 1 commit
-
-
guilhem@mysql.com authored
replacing the no_log argument of mysql_create_table() by some safer method (temporarily setting OPTION_BIN_LOG to 0) which guarantees that even the automatic DELETE FROM heap_table does not get into the binlog when a not-yet-existing HEAP table is opened by mysql_create_table().
-
- 13 Aug, 2004 1 commit
-
-
bar@mysql.com authored
ENUM and SET type didn't compute their length correctly. That showed up for example while converting into a CHAR column.
-
- 10 Aug, 2004 1 commit
-
-
dlenev@brandersnatch.localdomain authored
Instead of trying to open time zone tables during calculation of CONVERT_TZ() function or setting of @@time_zone variable we should open and lock them with the rest of statement's table (so we should add them to global table list) and after that use such pre-opened tables for loading info about time zones.
-
- 06 Aug, 2004 1 commit
-
-
dlenev@brandersnatch.localdomain authored
We should allow 19 as length of newly created TIMESTAMP fields.
-
- 21 Jul, 2004 1 commit
-
-
bell@sanja.is.com.ua authored
-
- 12 Jul, 2004 1 commit
-
-
monty@mysql.com authored
-
- 09 Jul, 2004 1 commit
-
-
monty@mysql.com authored
Some bug fixes to last pushed code
-
- 08 Jul, 2004 1 commit
-
-
bar@mysql.com authored
also known as BUG#2326 Charset of table is determined by charset of db only if "USE db;"
-
- 26 Jun, 2004 1 commit
-
-
serg@serg.mylan authored
-
- 24 Jun, 2004 1 commit
-
-
bell@sanja.is.com.ua authored
-
- 23 Jun, 2004 1 commit
-
-
bell@sanja.is.com.ua authored
-
- 21 Jun, 2004 1 commit
-
-
konstantin@mysql.com authored
-
- 18 Jun, 2004 2 commits
-
-
guilhem@mysql.com authored
mysqld >=4.1.3 will however understand shutdown requests sent by clients <4.1.3. And mysqld <4.1.3 will understand shutdown requests sent by clients >=4.1.3 (it will ignore the level). Those shutdown level are just PLACEHOLDERS now. So this change is just to make the 4.1 API suitable before it is frozen. Later we will actually implement the shutdown levels.
-
dlenev@brandersnatch.localdomain authored
Added basic per-thread time zone functionality (based on public domain elsie-code). Now user can select current time zone (from the list of time zones described in system tables). All NOW-like functions honor this time zone, values of TIMESTAMP type are interpreted as values in this time zone, so now our TIMESTAMP type behaves similar to Oracle's TIMESTAMP WITH LOCAL TIME ZONE (or proper PostgresSQL type). WL#1266 "CONVERT_TZ() - basic time with time zone conversion function". Fixed problems described in Bug #2336 (Different number of warnings when inserting bad datetime as string or as number). This required reworking of datetime realted warning hadling (they now generated at Field object level not in conversion functions). Optimization: Now Field class descendants use table->in_use member instead of current_thd macro.
-
- 17 Jun, 2004 2 commits
-
-
heikki@hundin.mysql.fi authored
-
heikki@hundin.mysql.fi authored
-
- 15 Jun, 2004 1 commit
-
-
guilhem@mysql.com authored
Server will however still accept shutdown without specified level; so that old mysqladmin can still shut server down. I would like your comments on the names of shutdown level which I chose. You are welcome to propose better names. Please however check WL#709 before. Reason for the names I propose is to be accurate, thus leaving possibility for other levels which we may imagine in the future; that's why I have rejected names like "fast", "smart", "graceful" so far. My position is that WAIT_ALL_BUFFERS or WAIT_CRITICAL_BUFFERS say what the shutdown does, whereas for "smart", "fast" you need to remember what it does. This should be pushed in 4.1.3 but only after your comments.
-
- 13 Jun, 2004 1 commit
-
-
bell@sanja.is.com.ua authored
-
- 10 Jun, 2004 3 commits
-
-
serg@serg.mylan authored
correct prefix compare with my_strnncoll
-
guilhem@mysql.com authored
exactly it's mapped to "ALTER TABLE t; ANALYZE TABLE t;"
-
monty@mysql.com authored
-
- 09 Jun, 2004 2 commits
-
-
guilhem@mysql.com authored
-
guilhem@mysql.com authored
-
- 08 Jun, 2004 1 commit
-
-
serg@serg.mylan authored
-
- 07 Jun, 2004 1 commit
-
-
sergefp@mysql.com authored
-