An error occurred fetching the project authors.
- 04 Feb, 2005 1 commit
-
-
gluh@gluh.mysql.r18.ru authored
bug#7833: Wrong datatype of aggregate column is returned
-
- 03 Feb, 2005 1 commit
-
-
monty@mysql.com authored
-
- 24 Jan, 2005 2 commits
-
-
bell@sanja.is.com.ua authored
-
serg@serg.mylan authored
-
- 18 Jan, 2005 2 commits
-
-
bar@mysql.com authored
-
bar@mysql.com authored
not default_charset_into. It fixes the problem that in some cases numbers where treated as CHAR(N), not as BINARY(N), e.g. wrong 'charsetnr' when sent to the client side. 2. IFNULL didn't aggregate argument charsets and collations, so IFNULL(1,'a') produced a CHAR(N). Now produces a BINARY(N). 3. SELECT PROCEDURE ANALIZE now returns BINARY columns, which is much better than it worked previously: CHAR with the default character set. But in the future it's worth to fix the fields 'Field_name' and 'Optimal_fieldtype' to use UTF8, and 'Min_value' and 'Max_value' to inherit their charsets from the original items. But it is not important, and BINARY(N) is OK for now. 4. Tests were fixed accordingly. No new tests were made, as the old onces cover everything.
-
- 15 Jan, 2005 1 commit
-
-
monty@mysql.com authored
-
- 06 Jan, 2005 1 commit
-
-
monty@mysql.com authored
Split TABLE to TABLE and TABLE_SHARE (TABLE_SHARE is still allocated as part of table, will be fixed soon) Created Field::make_field() and made Field_num::make_field() to call this Added 'TABLE_SHARE->db' that points to database name; Changed all usage of table_cache_key as database name to use this instead Changed field->table_name to point to pointer to alias. This allows us to change alias for a table by just updating one pointer. Renamed TABLE_SHARE->real_name to table_name Renamed TABLE->table_name to alias Renamed TABLE_LIST->real_name to table_name
-
- 30 Dec, 2004 3 commits
-
-
monty@mysql.com authored
-
gluh@gluh.mysql.r18.ru authored
-
gluh@gluh.mysql.r18.ru authored
added syntax: 'show variables where', 'show status where', 'show open tables where'
-
- 17 Dec, 2004 1 commit
-
-
ram@gw.mysql.r18.ru authored
-
- 14 Dec, 2004 1 commit
-
-
sergefp@mysql.com authored
* Backport of safety measures from 5.0: make numeorous replaces: s/item->fix_fields()/if (!item->fixed) item->fix_fields()
-
- 13 Dec, 2004 3 commits
-
-
sergefp@mysql.com authored
* Added Item_ref::set_properties * Item_ref::Item_ref now expects to get in *item either NULL - then fix_fields() will be called later or ptr to Item it will refer to - then an equivalent of fix_fields() call is performed
-
sergefp@mysql.com authored
The problem in 4.1 was the same as in 4.0 - fix_fields() not called for created Item_ref. The fix is similar too - initialize Item_refs in ctor (but don't interfere with cases when Item_ref is used by subselects).
-
bell@sanja.is.com.ua authored
-
- 11 Dec, 2004 2 commits
-
-
sergefp@mysql.com authored
In Item_ref::Item_ref set maybe_null (and other fields fix_fields sets) to be the same as in (*ref), because Item_ref::fix_fields() will not be called. Previously maybe_null was 0 always and this produced a bogus state where maybe_null==0 && is_null() == true which broke evaluation for some upper-level Items, like AND and OR.
-
bell@sanja.is.com.ua authored
refernces if subqueri is not in HAVING clause (BUG#7079) and the same used for subquery transformetion
-
- 07 Dec, 2004 1 commit
-
-
monty@mysql.com authored
Fixed compiler warnings String results in CREATE ... SELECT are now created as CHAR(0), VARCHAR(X) or TEXT() depending on item->max_length
-
- 06 Dec, 2004 2 commits
-
-
monty@mysql.com authored
Fixed compiler warnings Fix core dump when sending SIGHUP to mysqld
-
monty@mysql.com authored
Renamed HA_VAR_LENGTH to HA_VAR_LENGTH_PART Renamed in all files FIELD_TYPE_STRING and FIELD_TYPE_VAR_STRING to MYSQL_TYPE_STRING and MYSQL_TYPE_VAR_STRING to make it easy to catch all possible errors Added support for VARCHAR KEYS to heap Removed support for ISAM Now only long VARCHAR columns are changed to TEXT on demand (not CHAR) Internal temporary files can now use fixed length tables if the used VARCHAR columns are short
-
- 26 Nov, 2004 2 commits
-
-
bell@sanja.is.com.ua authored
-
bell@sanja.is.com.ua authored
-
- 24 Nov, 2004 2 commits
-
-
bell@sanja.is.com.ua authored
correct printing of aliases
-
dlenev@brandersnatch.localdomain authored
out of order". (final version) Now instead of binding Item_trigger_field to TABLE objects during trigger definition parsing at table open, we perform pass through special list of all such objects in trigger. This allows easily check all references to fields in old/new version of row in trigger during execution of CREATE TRIGGER statement (this is more courtesy for users since we can't check everything anyway). We also report that such reference is bad by returning error from Item_trigger_field::fix_fields() method (instead of setup_field()) This means that if trigger is broken we will bark during trigger execution instead of trigger definition parsing at table open. (i.e. now we allow to open tables with broken triggers).
-
- 21 Nov, 2004 1 commit
-
-
bell@sanja.is.com.ua authored
-
- 20 Nov, 2004 1 commit
-
-
serg@serg.mylan authored
-
- 18 Nov, 2004 1 commit
-
-
timour@mysql.com authored
-
- 15 Nov, 2004 1 commit
-
-
dlenev@brandersnatch.localdomain authored
In server we assume that datetime values stored in MYSQL_TIME struct are normalized (and year is not greater than 9999), so we should perform range checks in all places then we convert something to MYSQL_TIME.
-
- 13 Nov, 2004 2 commits
-
-
bell@sanja.is.com.ua authored
-
bell@sanja.is.com.ua authored
used only one implementation of format parser of (printf) fixed multistatement
-
- 12 Nov, 2004 1 commit
-
-
bell@sanja.is.com.ua authored
-
- 11 Nov, 2004 3 commits
-
-
konstantin@mysql.com authored
-
timour@mysql.com authored
-
timour@mysql.com authored
-
- 10 Nov, 2004 3 commits
-
-
monty@mysql.com authored
-
timour@mysql.com authored
- post-review changes
-
bar@mysql.com authored
the result takes its charset/collation attributes from the character string, e.g. SELECT func(NULL, _latin2'string') now returns a latin2 result. This is done by introducing a new derivation (aka coercibility) level DERIVATION_IGNORABLE, which is used with Item_null. 2. 'Pure' NULL is now BINARY(0), not CHAR(0). I.e. NULL is now more typeless.
-
- 09 Nov, 2004 1 commit
-
-
timour@mysql.com authored
- post-review fix regarding Item_fields - added test for the changed name resolution
-
- 07 Nov, 2004 1 commit
-
-
bell@sanja.is.com.ua authored
-