An error occurred fetching the project authors.
- 21 Sep, 2005 1 commit
-
-
ramil@mysql.com authored
-
- 19 Jul, 2005 1 commit
-
-
monty@mishka.local authored
-
- 11 Jul, 2005 2 commits
-
-
bar@mysql.com authored
Identation fix
-
bar@mysql.com authored
Bug#11591 CHAR column with utf8 does not work properly (more chars than expected) do_cut_string didn't call well_formed_length, and copied all data, which was wrong in the case of multibyte character set. ctype_utf8.result, ctype_utf8.test: adding test case
-
- 18 Jan, 2005 1 commit
-
-
jimw@mysql.com authored
set to a negative value. (Bug #7700)
-
- 09 Nov, 2004 1 commit
-
-
monty@mysql.com authored
-
- 08 Nov, 2004 1 commit
-
-
bar@mysql.com authored
Bug #6479 ALTER TABLE ... changing charset fails for TEXT columns Fix: use do_conv_blob rather than do_copy_blob if the column's character sets are different.
-
- 07 Oct, 2004 1 commit
-
-
dlenev@brandersnatch.localdomain authored
to auto_increment in 4.1". Now we are enforcing NO_AUTO_VALUE_ON_ZERO mode during ALTER TABLE only if we are converting one auto_increment column to another auto_increment column (this also includes most common case when we don't do anything with such column). Also now when we convert some column to TIMESTAMP NOT NULL column with ALTER TABLE we convert NULL values to current timestamp, (as we do this in INSERT). One can still get old behavior by setting system TIMESTAMP variable to 0.
-
- 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.
-
- 19 Aug, 2004 1 commit
-
-
bar@mysql.com authored
-
- 18 Jun, 2004 1 commit
-
-
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.
-
- 06 Apr, 2004 1 commit
-
-
serg@serg.mylan authored
::reset(), HA_FAST_KEY_READ, disable_indexes(), enable_indexes(), start_bulk_insert(), end_bulk_insert() Field::val_str simplification, comment
-
- 29 Mar, 2004 1 commit
-
-
monty@mysql.com authored
Fixes after last merge
-
- 16 Mar, 2004 2 commits
-
-
hf@deer.(none) authored
-
hf@deer.(none) authored
-
- 13 Dec, 2003 1 commit
-
-
serg@serg.mylan authored
-
- 11 Oct, 2003 1 commit
-
-
monty@mashka.mysql.fi authored
Add warnings for single line inserts. To do this I had to convert count_cuted_fields to an enum (to be able to detect setting a NOT NULL field to NULL)
-
- 28 Jul, 2003 1 commit
-
-
vva@eagle.mysql.r18.ru authored
-
- 22 Jul, 2003 1 commit
-
-
vva@eagle.mysql.r18.ru authored
-
- 11 Jul, 2003 1 commit
-
-
bar@bar.mysql.r18.ru authored
Data was not converted when ALTER TABLE CHAGE changed a field character set.
-
- 01 Jul, 2003 1 commit
-
-
monty@mashka.mysql.fi authored
Don't set field to DEFAULT value when set to NULL
-
- 24 Jun, 2003 1 commit
-
-
hf@deer.(none) authored
Looks a bit nicer than previous one
-
- 20 Jun, 2003 1 commit
-
-
hf@deer.(none) authored
So now for the CREATE TABLE foo (id integer NOT NULL default 9) INSERT INTO foo VALUES (NULL); we get an error INSERT INTO foo VALUES (1), (NULL), (2); we get one warning and second record is set to 9 Is that what we want?
-
- 30 Apr, 2003 1 commit
-
-
venu@myvenu.com authored
Fix LOAD DATA INFILE warnings to have a better meanigful messages Fix to make the mysql command line to automatically show the warnings count for all basic commands
-
- 14 Jan, 2003 1 commit
-
-
monty@mashka.mysql.fi authored
Allocate bigger default thread stack because of problems with glibc Fixed bug in UPDATE ... not_null_field=expression_that_returns_null Fixed bug in replication when using auto_increment and LOAD DATA INFILE
-
- 19 Dec, 2002 1 commit
-
-
bar@bar.mysql.r18.ru authored
a bit more ucs2 compatibility
-
- 11 Dec, 2002 1 commit
-
-
bar@bar.mysql.r18.ru authored
-
- 03 Dec, 2002 1 commit
-
-
monty@hundin.mysql.fi authored
Optimized SELECT DISTINCT ... ORDER BY ... LIMIT Fixed reference to uninitalized variable
-
- 06 Nov, 2002 1 commit
-
-
bar@bar.mysql.r18.ru authored
-
- 16 Oct, 2002 1 commit
-
-
monty@hundin.mysql.fi authored
-
- 26 Jun, 2002 1 commit
-
-
bar@gw.udmsearch.izhnet.ru authored
Fixed that MyISAM were not working properly with non-8bit charsets in some cases CONVERT() function now works properly
-
- 21 Jun, 2002 1 commit
-
-
bar@gw.udmsearch.izhnet.ru authored
-
- 17 May, 2002 1 commit
-
-
bar@gw.udmsearch.izhnet.ru authored
SELECT func(charset2) FROM t ORDER BY 1 works in correct charset
-
- 12 Mar, 2002 1 commit
-
-
bar@gw.udmsearch.izhnet.ru authored
-
- 06 Dec, 2001 1 commit
-
-
monty@hundin.mysql.fi authored
Fixed memory leak on shutdown (Affects the embedded version & MyODBC)
-
- 08 Mar, 2001 1 commit
-
-
monty@donna.mysql.fi authored
-
- 31 Jul, 2000 1 commit
-
-
bk@work.mysql.com authored
-