monty@mysql.com
6e58a7c49e
Code cleanup
2003-12-18 01:13:52 +02:00
vva@eagle.mysql.r18.ru
07f520b73e
Merge vvagin@bk-internal.mysql.com:/home/bk/mysql-4.0
...
into eagle.mysql.r18.ru:/home/vva/work/BUG_2023/mysql-4.0
2003-12-17 13:15:57 -04:00
vva@eagle.mysql.r18.ru
7aad55d97d
fixed small error in types in sql/field.cc
...
(char * -> const char*)
2003-12-17 13:15:01 -04:00
monty@mysql.com
e0cc6799ec
Merge with 4.0.17
2003-12-17 17:35:34 +02:00
ram@gw.mysql.r18.ru
795c88517e
proper fix for the bug #2077 : accented characters in enum/defaul values are reported incorrectly.
...
note: bar asked me to use res.charset in ::sql_type() functions to be more consistent.
2003-12-16 17:39:33 +04:00
monty@mysql.com
30e318311b
Fixes for last pull
2003-12-16 14:40:57 +02:00
Sinisa@sinisa.nasamreza.org
923422c247
Merge sinisa@bk-internal.mysql.com:/home/bk/mysql-4.0
...
into sinisa.nasamreza.org:/mnt/work/mysql-4.0
2003-12-13 15:41:20 +02:00
vva@eagle.mysql.r18.ru
5eb8fa9eaf
refixed last vva patch with monty's instructions
2003-12-12 22:02:50 -04:00
vva@eagle.mysql.r18.ru
00d339c4de
added checking for old cuted value in Field_enum::store
...
(bug #2023 )
2003-12-12 21:26:44 -04:00
Sinisa@sinisa.nasamreza.org
a888caa7bc
Merge sinisa@bk-internal.mysql.com:/home/bk/mysql-4.0
...
into sinisa.nasamreza.org:/mnt/work/mysql-4.0
2003-12-11 16:01:37 +02:00
konstantin@mysql.com
124c4ca346
cleanup: if there is return from if-part, we don't need else statement
2003-12-10 22:26:31 +03:00
dlenev@mysql.com
e4d2cbc0da
Fix undeterministic behaviour of year check
...
if we failed to classify integer as datetime
in Field_datetime::store().
Stylistic clean-ups.
2003-12-04 19:02:48 +03:00
dlenev@mysql.com
dd37ef055b
Fix for Bug #1448 "Date parsing fails, and fails to complain
...
about it". Now numbers representing illegal timestamps are
converted to 0 value if they are stored as timestamp or
datetime. This behaviour is consistent with manual and with
behaviour of string -> timestamp conversion.
2003-12-02 20:25:45 +03:00
guilhem@mysql.com
292b0a1892
Fix for BUG#1960 "date_format() returns spurious '-' for valid dates".
...
It was a forgotten ltime->neg=0 (neg was the only forgotten variable).
I scanned field.cc for other places where we would forget to set neg, found none.
A test for the bug.
2003-11-26 17:06:24 +01:00
bell@sanja.is.com.ua
afe48d3ce4
after review fixes
2003-11-23 21:26:43 +02:00
monty@mysql.com
7c6113a39f
Merge key cache structures to one
...
Fixed compiler warnings (IRIX C compiler and VC++)
2003-11-20 22:06:25 +02:00
Sinisa@sinisa.nasamreza.org
f6ca9afdbd
Fix for bug when zeros are to be prepended to decimal field
2003-11-18 15:58:27 +02:00
serg@serg.mylan
501c337ac4
test a correct flag in Field::optimize_range
2003-11-13 17:39:41 +01:00
monty@narttu.mysql.fi
6b79cd5c23
Merge
2003-11-03 22:48:03 +02:00
monty@narttu.mysql.fi
a444a3449f
Simplified 'wrong xxx name' error messages by introducing 'general' ER_WRONG_NAME error
...
Cleaned up (and disabled part of) date/time/datetime format patch. One can't anymore change default read/write date/time/formats.
This is becasue the non standard datetime formats can't be compared as strings and MySQL does still a lot of datetime comparisons as strings
Changed flag argument to str_to_TIME() and get_date() from bool to uint
Removed THD from str_to_xxxx functions and Item class.
Fixed core dump when doing --print-defaults
Move some common string functions to strfunc.cc
Dates as strings are now of type my_charset_bin instead of default_charset()
Introduce IDENT_QUOTED to not have to create an extra copy of simple identifiers (all chars < 128)
Removed xxx_FORMAT_TYPE enums and replaced them with the old TIMESTAMP_xxx enums
Renamed some TIMESTAMP_xxx enums to more appropriate names
Use defines instead of integers for date/time/datetime string lengths
Added to build system and use the new my_strtoll10() function.
2003-11-03 14:01:59 +02:00
serg@serg.mylan
6e17f4f20d
fixes to Bitmap class
2003-10-24 22:44:48 +02:00
serg@serg.mylan
f944fd4a65
merged
2003-10-21 11:58:43 +02:00
gluh@gluh.mysql.r18.ru
4bed4abb62
Merge commit
2003-10-20 13:45:28 +05:00
gluh@gluh.mysql.r18.ru
62b0b8b800
Scrum task 835 - text-to-datetime conversion function
2003-10-20 13:24:18 +05:00
serg@serg.mylan
8cc3951c8f
key_map with more that 64 bits width
2003-10-11 13:06:55 +02:00
bar@bar.mysql.r18.ru
83c6946232
Bug fix:
...
http://bugs.mysql.com/bug.php?id=1264
2003-09-16 15:43:17 +05:00
monty@mashka.mysql.fi
7538242e4f
merge with 4.1 tree
2003-09-11 20:31:40 +03:00
bar@bar.mysql.r18.ru
6fa45cec53
mysql_create_table now accepts field lengths in CREATE form, not in internal form.
...
This is to simplify fixing indexes to mean number of chars rather than bytes too.
2003-09-10 17:25:26 +05:00
monty@narttu.mysql.fi
77a70a0a24
merge with 4.0.15
2003-08-29 13:44:35 +03:00
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.
2003-08-22 04:07:40 +03:00
monty@narttu.mysql.fi
359846f052
Fixed some varnings from valgrind
...
Set min value of max_allowed_packet to 1024
Fixed problem with UNION's without braces and SQL_CALC_FOUND_ROWS, LIMIT #,#
and ORDER BY...LIMIT
2003-08-20 16:25:44 +03:00
monty@mashka.mysql.fi
10c4acfb4f
merge
2003-08-19 00:10:21 +03:00
monty@mashka.mysql.fi
4f7512160b
After merge fixes
...
Use server character set if --default-character-set is not used
Added convert_string() for more efficient alloc+character-set convert of strings
2003-08-19 00:08:08 +03:00
serg@serg.mylan
147b34e2f4
snprintf compatibility fix
2003-08-12 15:28:36 +02:00
bar@bar.mysql.r18.ru
786af34146
Fix: create table t1 (a char(10) character set cp1251) SELECT _koi8r'blabla' as a
...
The above query created a field of koi8r charset, not cp1251
Change:
CREATE TABLE a (a CHAR(1) CHARACTER SET utf8)
Length now means character length, not byte length.
The above creates a field that guarantees can store a multibyte value
1 character long. For utf8 the above creates a field that can store
3 bytes.
2003-08-11 18:18:34 +05:00
gluh@gluh.mysql.r18.ru
e6eef74812
Merge gluh@gw:/home/bk/mysql-4.1
...
into gluh.mysql.r18.ru:/home/gluh/mysql-4.1.DTFUNC
2003-07-08 12:57:00 +05:00
serg@serg.mylan
55115e0f9d
timestamp MYD-4.0 format compatibility fix
2003-06-28 23:01:33 +02:00
gluh@gluh.mysql.r18.ru
91e3245b67
Merge gluh@gw:/home/bk/mysql-4.1
...
into gluh.mysql.r18.ru:/home/gluh/mysql-4.1.DTFUNC
2003-06-23 13:02:28 +05:00
gluh@gluh.mysql.r18.ru
66af4b5c9a
Internal commit
2003-06-23 12:56:44 +05:00
wax@kishkin.ru
ed02be687c
Merge kishkin.ru:/home/wax/mysql-4.1 into kishkin.ru:/home/wax/mysql-4g
2003-06-07 02:28:11 +06:00
monty@narttu.mysql.fi
dad0664579
merge with public tree
2003-06-05 00:12:45 +03:00
monty@narttu.mysql.fi
40109c574a
Merge with 4.0.13
2003-06-04 19:21:51 +03:00
wax@kishkin.ru
61f7821323
Merge kishkin.ru:/home/wax/mysql-4n into kishkin.ru:/home/wax/mysql-4g
2003-06-03 17:07:46 +06:00
bar@bar.mysql.r18.ru
759214fa41
MY_CS_NONTEXT flag for sprintf() incompatible charsets (ucs2 if the only one now)
...
Some default_charset_info were removed
2003-06-03 14:59:17 +05:00
wax@kishkin.ru
a2e9bbf2eb
URGENT
...
SCRUM
BUG
correct wrong code in group_concat
2003-05-31 15:44:19 +06:00
monty@narttu.mysql.fi
381492093e
Fixed problem with mysql prompt when server disconnect. (Bug 356)
...
Fixed problem with localtime -> gmt where some times resulted in
different (but correct) timestamps. Now MySQL should use the smallest
possible timestamp value in this case. (Bug 316)
2003-05-27 16:40:14 +03:00
monty@mashka.mysql.fi
bd4b9522e4
Merge bk-internal.mysql.com:/home/bk/mysql-4.1
...
into mashka.mysql.fi:/home/my/mysql-4.1-narttu
2003-05-26 19:03:25 +03:00
monty@mashka.mysql.fi
68a159b1fa
New 4.1 protocol; SQLSTATE, CLIENT_MULTI_RESULTS, client character set
2003-05-26 19:01:20 +03:00
bar@bar.mysql.r18.ru
8192d169a2
CHARSET_INFO structure reorganization for easier maintainance
2003-05-23 17:45:52 +05:00
bar@bar.mysql.r18.ru
a238efaa63
SHOW FIELDS changes, more SQL99 INFORMATION_SCHEMA.COLUMNS compatibility:
...
Character set is not displayed in "Type" column anymore
In "Collation" column NULL instead of BINARY is now displayd for for non-character data types
2003-05-23 13:10:25 +05:00