An error occurred fetching the project authors.
- 12 Oct, 2006 1 commit
-
-
kaa@polly.local authored
-
- 11 Oct, 2006 1 commit
-
-
Kristofer.Pettersson@naruto. authored
-
- 04 Oct, 2006 1 commit
-
-
kaa@polly.local authored
- bug #11655 "Wrong time is returning from nested selects - maximum time exists - input and output TIME values were not validated properly in several conversion functions - bug #20927 "sec_to_time treats big unsigned as signed" - integer overflows were not checked in several functions. As a result, input values like 2^32 or 3600*2^32 were treated as 0 - BIGINT UNSIGNED values were treated as SIGNED in several functions - in cases where both input string truncation and out-of-range TIME value occur, only 'truncated incorrect time value' warning was produced
-
- 02 Oct, 2006 1 commit
-
-
Kristofer.Pettersson@naruto. authored
- Type casting was not consequent, thus when adding a DATE type with a WEEK interval the result type was DATETIME and not DATE as is the norm. - By changing the order of the date internal enumerations the deviant type casting is resolved (Item_date_add_interval::fix_length_and_dec() which determines result type for this operation assumes that addition of any interval with value <= INTERVAL_DAY to date value will result in date). There are two independant places to change: interval_names[] and interval_type.
-
- 22 Sep, 2006 1 commit
-
-
Kristofer.Pettersson@naruto. authored
- The definition of the result type of a type_date function didn't include INTERVAL_WEEK - This patch adds an explicit test for INTERVAL_WEEK which results in the result type for an item_date_add_intervall operation being DATE rather than DATETIME when one parameter is INTERVAL_WEEK.
-
- 17 Aug, 2006 1 commit
-
-
jimw@rama.(none) authored
Fix when __attribute__() is stubbed out, add ATTRIBUTE_FORMAT() for specifying __attribute__((format(...))) safely, make more use of the format attribute, and fix some of the warnings that this turns up (plus a bonus unrelated one).
-
- 10 Aug, 2006 1 commit
-
-
time_format() claimed %H and %k would return at most two digits (hours 0-23), but this coincided neither with actual behaviour nor with docs. this is not visible in simple queries; forcing a temp-table is probably the easiest way to see this. adjusted the return-length appropriately; the alternative would be to adjust the docs to say that behaviour for > 99 hours is undefined. --- Bug#19844: time_format in Union truncates values time_format() claimed %H and %k would return at most two digits (hours 0-23), but this coincided neither with actual behaviour nor with docs. this is not visible in simple queries; forcing a temp-table is probably the easiest way to see this. adjusted the return-length appropriately; the alternative would be to adjust the docs to say that behaviour for > 99 hours is undefined.
-
- 07 Aug, 2006 1 commit
-
-
str_to_date() would sometimes render NULL if %D was used as rule other than last. since this was due to two pointers getting mixed up in the server, this behaviour seemed somewhat non-deterministic at SQL level.
-
- 29 Jul, 2006 1 commit
-
-
difference between timestamp in values of months and quarters.) Problem: when requesting timestamp diff in months or quarters, it would only examine the date (and not the time) for the comparison. Solution: increased precision of comparison.
-
- 18 Jul, 2006 1 commit
-
-
Please use "ul" when merging this changeset to 5.0.
-
- 12 Jul, 2006 1 commit
-
-
kostja@bodhi.local authored
-
- 04 Jul, 2006 1 commit
-
-
bar@mysql.com authored
(implemented by by Josh Chamas)
-
- 27 Jun, 2006 1 commit
-
-
kroki@mysql.com authored
Dec. 31st, 9999 is still a valid date, only starting with Jan 1st 10000 things become invalid (Bug #12356)
-
- 16 Jun, 2006 1 commit
-
-
serg@serg.mylan authored
fix Field::store(double) being used instead of store(longlong) NB: overloading functions is evil
-
- 13 Jun, 2006 1 commit
-
-
evgen@moonbone.local authored
can lead to a wrong result. All date/time functions has the STRING result type thus their results are compared as strings. The string date representation allows a user to skip some of leading zeros. This can lead to wrong comparison result if a date/time function result is compared to such a string constant. The idea behind this bug fix is to compare results of date/time functions and data/time constants as ints, because that date/time representation is more exact. To achieve this the agg_cmp_type() is changed to take in the account that a date/time field or an date/time item should be compared as ints. This bug fix is partially back ported from 5.0. The agg_cmp_type() function now accepts THD as one of parameters. In addition, it now checks if a date/time field/function is present in the list. If so, it tries to coerce all constants to INT to make date/time comparison return correct result. The field for the constant coercion is taken from the Item_field or constructed from the Item_func. In latter case the constructed field will be freed after conversion of all constant items. Otherwise the result is same as before - aggregated with help of the item_cmp_type() function. From the Item_func_between::fix_length_and_dec() function removed the part which was converting date/time constants to int if possible. Now this is done by the agg_cmp_type() function. The new function result_as_longlong() is added to the Item class. It indicates that the item is a date/time item and result of it can be compared as int. Such items are date/time fields/functions. Correct val_int() methods are implemented for classes Item_date_typecast, Item_func_makedate, Item_time_typecast, Item_datetime_typecast. All these classes are derived from Item_str_func and Item_str_func::val_int() converts its string value to int without regard to the date/time type of these items. Arg_comparator::set_compare_func() and Arg_comparator::set_cmp_func() functions are changed to substitute result type of an item with the INT_RESULT if the item is a date/time item and another item is a constant. This is done to get a correct result of comparisons like date_time_function() = string_constant.
-
- 24 May, 2006 1 commit
-
-
monty@mysql.com authored
Remove dflt_field from field structure as this was only needed when createing temporary table and I found another soultion that doesn't increase the size of the field structure for all table instances. (Better fix for bug #19089) Fixed compiler warnings Fixed valgrind warning in Item_date_add_intervall::eq. (Recoding of bugfix #19490)
-
- 16 May, 2006 1 commit
-
-
tnurnberg@mysql.com authored
if input year for date_add() / date_sub() with INTERVAL is low enough for calc_daynr() to possibly return incorrect results (calc_daynr() has no information on whether the year is low because it was a two-digit year ('77) or because it was a really low four-digit year (0077) and will indiscriminately try to turn the value into a four-digit year by adding 1900 or 2000 respectively), the functions will now throw NULL.
-
- 13 May, 2006 1 commit
-
-
igor@rurik.mysql.com authored
itself when executing queries referring to a view with GROUP BY an expression containing non-constant interval. It happened because Item_date_add_interval::eq neglected the fact that the method can be applied to an expression of the form date(col) + interval time_to_sec(col) second at the time when col could not be evaluated yet. An attempt to evaluate time_to_sec(col) in this method resulted in a crash.
-
- 04 May, 2006 2 commits
-
-
jani@ua141d10.elisa.omakaista.fi authored
TIME_FORMAT using "%l:%i" returns 36:00 with 24:00:00 in TIME column
-
jani@ua141d10.elisa.omakaista.fi authored
-
- 02 May, 2006 1 commit
-
-
ramil@mysql.com authored
-
- 25 Apr, 2006 1 commit
-
-
ramil@mysql.com authored
-
- 17 Apr, 2006 1 commit
-
-
bar@mysql.com authored
5.0 additional fix for b#18691 Handle DECIMAL the same with INT and REAL.
-
- 13 Apr, 2006 1 commit
-
-
bar@mysql.com authored
Conversion from int and real numbers to UCS2 didn't work fine: CONVERT(100, CHAR(50) UNICODE) CONVERT(103.9, CHAR(50) UNICODE) The problem appeared because numbers have binary charset, so, simple charset recast binary->ucs2 was performed instead of real conversion. Fixed to make numbers pretend to be non-binary.
-
- 11 Apr, 2006 1 commit
-
-
ramil@mysql.com authored
-
- 07 Apr, 2006 2 commits
-
-
hartmut@mysql.com authored
-
andrey@lmy004. authored
This also should fix 17493 and 17346, and probably 16397 (not tested). WL#1034 (Internal CRON) (post-review commit)
-
- 28 Mar, 2006 1 commit
-
-
msvensson@shellback. authored
-
- 02 Mar, 2006 1 commit
-
-
pem@mysql.com authored
time per connection Removed const_string() method from Item_string (it was only used in one place, in a bad way). Defer possible SP variable, and access data directly instead, in date_format item.
-
- 02 Feb, 2006 1 commit
-
-
gunnar@mysql.com. authored
manual adding the fix for bug#15828 which did not automerge
-
- 18 Jan, 2006 1 commit
-
-
andrey@lmy004. authored
Before the interval expression was considered to be in seconds, now it is just a number and the type of interval is considered. - this changeset introduces also fix for bug#16432 (Events: error re interval misrepresents the facts) the code of event_timed::set_interval() was refactored anyway so it is meaningful to fix the bug in the same changeset.
-
- 16 Jan, 2006 1 commit
-
-
gvb@phoenix.(none) authored
fix for bug #15828 after review doing val_str now before testing of null value secures the function for null values returned by dynamic functions - the fix before was incomplete andy covered constant null values
-
- 14 Jan, 2006 2 commits
-
-
gvb@phoenix.(none) authored
fix for bug #15828 after review
-
gvb@phoenix.(none) authored
fix for bug#15828 after review
-
- 13 Jan, 2006 1 commit
-
-
gvb@phoenix.(none) authored
problem was not checking 2nd parameter of str_to_date against NULL
-
- 27 Dec, 2005 1 commit
-
-
sergefp@mysql.com authored
-
- 22 Dec, 2005 1 commit
-
-
sergefp@mysql.com authored
-
- 23 Nov, 2005 1 commit
-
-
monty@mysql.com authored
The table opening process now works the following way: - Create common TABLE_SHARE object - Read the .frm file and unpack it into the TABLE_SHARE object - Create a TABLE object based on the information in the TABLE_SHARE object and open a handler to the table object Other noteworthy changes: - In TABLE_SHARE the most common strings are now LEX_STRING's - Better error message when table is not found - Variable table_cache is now renamed 'table_open_cache' - New variable 'table_definition_cache' that is the number of table defintions that will be cached - strxnmov() calls are now fixed to avoid overflows - strxnmov() will now always add one end \0 to result - engine objects are now created with a TABLE_SHARE object instead of a TABLE object. - After creating a field object one must call field->init(table) before using it - For a busy system this change will give you: - Less memory usage for table object - Faster opening of tables (if it's has been in use or is in table definition cache) - Allow you to cache many table definitions objects - Faster drop of table
-
- 21 Nov, 2005 1 commit
-
-
bar@mysql.com authored
Fixing test results accordingly. item_timefunc.cc: Displaying BINARY or CHAR in error messages, depending on the character set.
-
- 20 Nov, 2005 1 commit
-
-
bell@sanja.is.com.ua authored
Bad examples of usage of a string with its length fixed. The incorrect length in the trigger file configuration descriptor fixed (BUG#14090). A hook for unknown keys added to the parser to support old .TRG files.
-