An error occurred fetching the project authors.
- 25 Apr, 2005 1 commit
-
-
dlenev@brandersnatch.localdomain authored
"'func_sapdb' fails on 64bit build hosts")
-
- 04 Apr, 2005 1 commit
-
-
monty@mysql.com authored
Don't generate message in send_kill_message() if wrong data. (Caused core dump for wrong data in ALTER TABLE on some system)
-
- 01 Apr, 2005 1 commit
-
-
monty@mysql.com authored
CAST() now produces warnings when casting a wrong INTEGER or CHAR values. This also applies to implicite string to number casts. (Bug #5912) ALTER TABLE now fails in STRICT mode if it generates warnings. Inserting a zero date in a DATE, DATETIME or TIMESTAMP column during TRADITIONAL mode now produces an error. (Bug #5933)
-
- 30 Mar, 2005 1 commit
-
-
monty@mysql.com authored
Small fixes while doing review of new pushed code More test cases for decimal
-
- 28 Mar, 2005 1 commit
-
-
dlenev@brandersnatch.localdomain authored
result" (and similar bug in ADDTIME/SUBTIME). Both Item_func_add_time/Item_func_timediff::val_str() now use calc_time_diff() function which was backported from 5.0 (and which was was fixed to properly handle microseconds part of its second argument). Also now we correctly set sign of result in case when first argument is negative and second is positive.
-
- 27 Jan, 2005 1 commit
-
-
bar@mysql.com authored
CAST now always return a well-formed character string.
-
- 26 Jan, 2005 1 commit
-
-
dlenev@brandersnatch.localdomain authored
does not work well together". Now using simplier and more correct implementation of st_lex::unlink_first_table()/link_first_table_back() (It also nicely handles case when global table list is created because of implictly used time zone tables). (2nd attempt) Fix for bug #7705 "CONVERT_TZ() crashes with subquery/WHERE on index column". Implemented new approach for caching objects for constant time zone arguments. Now instead of determining whenever these arguments are constants and performing time zone lookup at fix_fields() stage, we do it on first get_date() invocation. Cleanup of global @@time_zone variable handling.
-
- 24 Jan, 2005 1 commit
-
-
serg@serg.mylan authored
-
- 15 Jan, 2005 1 commit
-
-
dlenev@brandersnatch.localdomain authored
to 5.0 tree (since it was lost during last merge).
-
- 12 Jan, 2005 1 commit
-
-
dlenev@brandersnatch.localdomain authored
-
- 30 Dec, 2004 3 commits
-
-
dlenev@brandersnatch.localdomain authored
correctly even with zero month and day" and bug #7515 "from_unixtime(0) now returns NULL instead of the Epoch" into 4.1 tree.
-
dlenev@mysql.com authored
the Epoch". (With after review fixes).
-
dlenev@brandersnatch.localdomain authored
When we cast datetime value to DATE (TIME) type we should throw away its time (date) part. This was not done properly if CAST() function was used in datetime expressions.
-
- 22 Dec, 2004 1 commit
-
-
dlenev@brandersnatch.localdomain authored
STR_TO_DATE() function if there is another format specifier after %f in format string". Also small cleanup of STR_TO_DATE() implementation. (After review version.)
-
- 15 Nov, 2004 1 commit
-
-
dlenev@mysql.com authored
values for too big argument". Added range checking for from_unixtime() argument, cleaned up code a bit.
-
- 09 Nov, 2004 1 commit
-
-
monty@mysql.com authored
Fix for valgrind/purify for variables that the compiler touches but that doesn't affect the outcome of the tests
-
- 07 Nov, 2004 1 commit
-
-
monty@mysql.com authored
Now thd->mem_root is a pointer to thd->main_mem_root and THR_MALLOC is a pointer to thd->mem_root. This gives us the following benefits: - Allow us to easily detect if arena has already been swapped before (this fixes a bug in setup_conds() where arena was swaped twice in some cases) - Faster swaps of arenas (as we don't have to copy the whole MEM_ROOT) - We don't anymore have to call my_pthread_setspecific_ptr(THR_MALLOC,...) to change where memory is alloced. Now it's enough to set thd->mem_root
-
- 29 Oct, 2004 1 commit
-
-
bar@mysql.com authored
"uint *errors" is now a non-optional parameter in String:copy() and copy_and_convert().
-
- 25 Oct, 2004 1 commit
-
-
bar@mysql.com authored
-
- 20 Oct, 2004 1 commit
-
-
bell@sanja.is.com.ua authored
net_printf/send_error calls replaced by my_error family functions -1/1 (sent/unsent) error reporting removed (WL#2133)
-
- 15 Oct, 2004 1 commit
-
-
konstantin@mysql.com authored
statements and negative time/date values". The bug was in wrong sprintf format used in the client library. The fix moves TIME -> string conversion functions to sql-common and utilized them in the client library.
-
- 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.
-
- 28 Sep, 2004 1 commit
-
-
monty@mishka.local authored
Under strict mode MySQL will generate an error message if there was any conversion when assigning data to a field. Added checking of date/datetime fields. If strict mode, give error if we have not given value to field without a default value (for INSERT)
-
- 07 Sep, 2004 1 commit
-
-
bar@mysql.com authored
-
- 01 Sep, 2004 1 commit
-
-
bell@sanja.is.com.ua authored
-
- 17 Aug, 2004 1 commit
-
-
dlenev@brandersnatch.localdomain authored
hpux11 compiler dislikes empty array initializers.
-
- 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
Added support of converion specifiers mentioned in manual but missing in code.
-
- 20 Jul, 2004 1 commit
-
-
serg@serg.mylan authored
-
- 16 Jul, 2004 1 commit
-
-
dlenev@brandersnatch.localdomain authored
-
- 24 Jun, 2004 1 commit
-
-
konstantin@mysql.com authored
work (prepared statements)" and after-review fixes: - str_to_TIME renamed to str_to_datetime to pair with str_to_time - functions str_to_time and str_to_TIME moved to sql-common - send_data_str now supports MYSQL_TYPE_TIME, MYSQL_TIME_DATE, MYSQL_TIME_DATETIME types of user input buffers. - few more comments in the client library - a test case added.
-
- 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.
-
- 24 May, 2004 1 commit
-
-
konstantin@mysql.com authored
after Monty's review. - Item_param was rewritten. - it turns out that we can't convert string data to character set of connection on the fly, because they first should be written to the binary log. To support efficient conversion we need to rewrite prepared statements binlogging code first.
-
- 06 May, 2004 1 commit
-
-
monty@mysql.com authored
Change strtoll -> my_strtoll10() Fixed bug in my_strntoul() and my_strntol() where we got different values on 32 and 64 bit systems (Bug #3472)
-
- 05 May, 2004 1 commit
-
-
monty@mysql.com authored
-
- 03 May, 2004 1 commit
-
-
serg@serg.mylan authored
-
- 28 Apr, 2004 1 commit
-
-
monty@mysql.com authored
Output TIMESTAMP in 4.1 format for 4.1 tables (or for TIMESTAMP(19)) (portability fix) Fixed that INTERVAL can handle big integers. (Bug #3498) Fixed that hostname="" works identical as hostname="%" for table/column grants (Bug #3473)
-
- 23 Mar, 2004 1 commit
-
-
hf@deer.(none) authored
Item_func_from_days::get_date didn't change 'hr', 'min' and some other fields of incoming ltime, so they got random values. bzeroing of the ltime added
-
- 18 Mar, 2004 1 commit
-
-
bell@sanja.is.com.ua authored
small optimisation in signed_literal
-
- 15 Mar, 2004 1 commit
-
-
gluh@gluh.mysql.r18.ru authored
-