An error occurred fetching the project authors.
- 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).
-
- 09 Jun, 2005 1 commit
-
-
joreland@mysql.com 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.
-
- 29 Mar, 2005 2 commits
-
-
mskold@mysql.com authored
-
serg@serg.mylan authored
-
- 18 Jan, 2005 1 commit
-
-
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 1 commit
-
-
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.
-
- 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.
-
- 06 Dec, 2004 1 commit
-
-
bar@mysql.com authored
-
- 30 Nov, 2004 1 commit
-
-
tomas@poseidon.ndb.mysql.com authored
ndb now runs ps tests just like the others
-
- 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.
-
- 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.
-