An error occurred fetching the project authors.
- 01 Dec, 2005 1 commit
-
-
gluh@eagle.intranet.mysql.r18.ru authored
SQL mode TRADITIONAL Message is chenged from 'ER_WARN_NULL_TO_NOTNULL' to 'ER_BAD_NULL_ERROR'
-
- 27 Sep, 2005 1 commit
-
-
pem@mysql.com authored
procedure variable Second version, after review. Keep the unsigned_flag in Item_decimal updated. Note that this also changed the result of several old test results - creating tables from decimal templates now gives unsigned columns and different sizes. (Several tests had Length > Max_length before.)
-
- 09 Sep, 2005 2 commits
-
-
gluh@eagle.intranet.mysql.r18.ru authored
-
gluh@eagle.intranet.mysql.r18.ru authored
This fix is cancellation of ChangeSet 1.2329 05/07/12 08:35:30 reggie@linux.site +8 -0 Bug 7142 Show Fields from fails using Borland's dbExpress interface The reason is we can't fix bug#7142 without breaking of existing applications/APIs that worked fine with earlier 4.1 bug 7142 is fixed in 5.0
-
- 23 Aug, 2005 1 commit
-
-
timour@mysql.com authored
* Provide backwards compatibility extension to name resolution of coalesced columns. The patch allows such columns to be qualified with a table (and db) name, as it is in 4.1. Based on a patch from Monty. * Adjusted tests accordingly to test both backwards compatible name resolution of qualified columns, and ANSI-style resolution of non-qualified columns. For this, each affected test has two versions - one with qualified columns, and one without.
-
- 12 Aug, 2005 1 commit
-
-
timour@mysql.com authored
"Process NATURAL and USING joins according to SQL:2003". * Some of the main problems fixed by the patch: - in "select *" queries the * expanded correctly according to ANSI for arbitrary natural/using joins - natural/using joins are correctly transformed into JOIN ... ON for any number/nesting of the joins. - column references are correctly resolved against natural joins of any nesting and combined with arbitrary other joins. * This patch also contains a fix for name resolution of items inside the ON condition of JOIN ... ON - in this case items must be resolved only against the JOIN operands. To support such 'local' name resolution, the patch introduces a stack of name resolution contexts used at parse time. NOTICE: - This patch is not complete in the sense that - there are 2 test cases that still do not pass - one in join.test, one in select.test. Both are marked with a comment "TODO: WL#2486". - it does not include a new test specific for the task
-
- 19 Jul, 2005 1 commit
-
-
jimw@mysql.com authored
-
- 18 Jul, 2005 1 commit
-
-
jimw@mysql.com authored
NO_ZERO_IN_DATE, and INVALID_DATES bits of SQL_MODE. (Bug #5906)
-
- 14 Jul, 2005 1 commit
-
-
konstantin@mysql.com authored
No separate typecode for MEDIUMTEXT/LONGTEXT is added, as we have no sound decision yet what typecodes and for what types are sent by the server (aka what constitutes a distinct type in MySQL).
-
- 12 Jul, 2005 1 commit
-
-
reggie@linux.site authored
The problem here is that columns that have an especially long type such as an enum type with many options would be longer than 40 chars but the type column returned from show columns always was defined as varchar(40). This is fixed in 5.0 using info schema.
-
- 20 Jun, 2005 1 commit
-
-
msvensson@neptunus.(none) authored
- Print warning that says display width is not supported for datatype TIMESTAMP, if user tries to create a TIMESTAMP column with display width. - Use display width for TIMESTAMP only in type_timestamp test to make sure warning is displayed correctly.
-
- 14 Jun, 2005 1 commit
-
-
mskold@mysql.com authored
-
- 07 Jun, 2005 2 commits
-
-
igor@rurik.mysql.com authored
Fixed bug #9899: erronious NOT_NULL flag for some attributes in the EXPLAIN table.
-
konstantin@mysql.com authored
error for LIMIT placeholder". The patch adds grammar support for LIMIT ?, ? and changes the type of ST_SELECT_LEX::select_limit,offset_limit from ha_rows to Item*, so that it can point to Item_param.
-
- 05 May, 2005 1 commit
-
-
holyfoot@hf-ibm.(none) authored
-
- 30 Mar, 2005 1 commit
-
-
msvensson@neptunus.(none) authored
- Add function Item_param::fix_fields which will update any subselect they are part of and indicate that the subsleect is not const during prepare phase, and thus should not be executed during prepare.
-
- 23 Mar, 2005 1 commit
-
-
serg@serg.mylan authored
corrected number of fields for --enable_metadata sql/sql_union.cc fixed a apparent typo in assert
-
- 10 Feb, 2005 1 commit
-
-
monty@mysql.com authored
After merge fixes Don't give duplicate warnings for some ::store() functions
-
- 08 Feb, 2005 1 commit
-
-
hf@deer.(none) 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.
-
- 30 Dec, 2004 2 commits
-
-
monty@mysql.com authored
-
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.
-
- 17 Dec, 2004 1 commit
-
-
mleich@mysql.com authored
longer available for most storage engines. Therefore column c18 BIT is switched TINYINT .
-
- 13 Dec, 2004 1 commit
-
-
mleich@mysql.com authored
ps-modify1 used the user variables @1, @2, @100 set within ps_query and ps_modify. That architecture was wrong, because the dependence of ps_modify1 on ps_query and ps_modify makes the test script maintenance and the use of these test cases during bug fixing/ debugging of single sub test cases very uncomfortable. Therefore these user variables (@1, @2, @100) are also set within ps-modify1. The result files of the test cases ps_2myisam, ps_3innodb, ps_4heap, ps_6bdb, ps_7ndb will be affected by that change and show 3 additional lines, but nothing else will change.
-
- 08 Dec, 2004 1 commit
-
-
bar@mysql.com authored
- CREATE TABLE t1 SELECT BINARY 'literal' now creates a VARBINARY() column, not a BINARY().
-
- 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
-
-
bar@mysql.com authored
-
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
-
- 10 Nov, 2004 1 commit
-
-
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.
-
- 05 Nov, 2004 1 commit
-
-
bar@mysql.com authored
character set with NULL, @A should be latin2 after this query sequence: SET @A=_latin2'string'; SET @A=NULL; I.e. the second query should not change the charset to the current default value, but should keep the original value assigned during the first query. In order to do it, we don't copy charset from the argument if the argument is NULL and the variable has previously been initialized.
-
- 03 Nov, 2004 1 commit
-
-
monty@mysql.com authored
FOUND is not a reserved keyword anymore Added Item_field::set_no_const_sub() to be able to mark fields that can't be substituted Added 'simple_select' method to be able to quickly determinate if a select_result is a normal SELECT Note that the 5.0 tree is not yet up to date: Sanja will have to fix multi-update-locks for this merge to be complete
-
- 30 Oct, 2004 1 commit
-
-
konstantin@mysql.com authored
-
- 11 Oct, 2004 1 commit
-
-
tomas@poseidon.ndb.mysql.com authored
-
- 07 Oct, 2004 3 commits
-
-
tomas@poseidon.ndb.mysql.com authored
-
tomas@poseidon.ndb.mysql.com authored
-
tomas@poseidon.ndb.mysql.com authored
-
- 28 Sep, 2004 1 commit
-
-
konstantin@mysql.com authored
tests were disabled due to failures caused by floating point conversion issues on optimized builds).
-
- 25 Sep, 2004 1 commit
-
-
konstantin@mysql.com authored
if possible" - many new test cases - more and improved comments New files: t/ps_7ndb.test test suite for NDB tables r/ps_7ndb.result expected results include/ps_conv.inc conversion test cases + review comments and fixes.
-
- 20 Sep, 2004 1 commit
-
-
mleich@mysql.com authored
These modifications were part of WL#1856 Conversion of client_test.c tests cases to mysqltest if possible They are separated from the other WL#1856 stuff, because they improve the behaviour of the current tests. Make the result sets (order of rows) more predictable by using ORDER BY.
-