gluh@mysql.com
023317d68a
after merge fix
2006-05-25 19:20:34 +05:00
gluh@eagle.intranet.mysql.r18.ru
474ef8ed43
Fix for bug#17626 CREATE TABLE ... SELECT failure with TRADITIONAL SQL mode
...
transfer NO_DEFAULT_VALUE_FLAG flag to new field
2006-05-23 13:27:45 +05:00
msvensson@neptunus.(none)
c4b1fb68b4
Bug#10460 SHOW CREATE TABLE uses inconsistent upper/lower case
2006-02-22 10:09:59 +01:00
jimw@mysql.com
95f1b04929
Remove extra space in SHOW CREATE TABLE output. (Bug #13883 )
2006-02-02 11:39:28 -08:00
gluh@eagle.intranet.mysql.r18.ru
e9d70e4b97
Fix for bug#8294 Traditional: Misleading error message for invalid CAST to DATE
...
-issue more correct message for incorrect date|datetime|time values
-ER_WARN_DATA_OUT_OF_RANGE message is changed
-added new error message
2005-12-02 15:01:44 +04:00
gluh@eagle.intranet.mysql.r18.ru
21cc3ae561
Fix for bug#11491 Misleading error message if not NULL column set to NULL,
...
SQL mode TRADITIONAL
Message is chenged from 'ER_WARN_NULL_TO_NOTNULL' to 'ER_BAD_NULL_ERROR'
2005-12-01 15:30:11 +04:00
monty@mishka.mysql.fi
f348f62cc3
Added option --valgrind-mysqltest to mysql-test-run
...
Added flag to Field::store(longlong) to specify if value is unsigned.
This fixes bug #12750 : Incorrect storage of 9999999999999999999 in DECIMAL(19, 0)
Fixed warning from valgrind in CREATE ... SELECT
Fixed double free of mysql.options if reconnect failed
2005-09-14 01:41:44 +03:00
ramil@mysql.com
5ac378ba15
after-merge fix
2005-07-27 15:57:00 +05:00
ramil@mysql.com
e43dff67f5
Merge rkalimullin@bk-internal.mysql.com:/home/bk/mysql-5.0
...
into mysql.com:/usr/home/ram/work/mysql-5.0
2005-07-27 15:09:06 +05:00
ramil@mysql.com
afb1ad8415
a fix (bug #11546 : Bad error message from inserting out of range values, SQL_MODE='tradition').
2005-07-26 12:18:35 +05:00
ramil@mysql.com
efc8404a40
fix (bug #11964 : ALTER TABLE gives wrong error message with sql-mode TRADITIONAL (timestamp)).
2005-07-25 14:36:07 +05:00
jimw@mysql.com
d4e0d60156
Clean up after merge of bug fixes
2005-07-19 19:59:36 -07:00
jimw@mysql.com
d7fbff3ec5
Merge mysql.com:/home/jimw/my/mysql-5.0-5906
...
into mysql.com:/home/jimw/my/mysql-5.0-clean
2005-07-19 19:59:34 -07:00
jimw@mysql.com
dd2f631ec4
Fix number to date conversion so it always honors the NO_ZERO_DATE,
...
NO_ZERO_IN_DATE, and INVALID_DATES bits of SQL_MODE. (Bug #5906 )
2005-07-18 16:12:44 -07:00
ramil@mysql.com
b11d04e50a
a fix (bug #9881 : ALTER TABLE gives wrong error message with sql-mode TRADITIONAL).
2005-07-15 15:50:57 +05:00
ramil@mysql.com
524b988260
a fix (bug #6961 : Traditional: assignment of string to numeric column should fail).
2005-05-13 13:22:27 +05:00
ramil@mysql.com
152f751831
fix (Bug #8295 and #8296 : varchar and varbinary conversion)
...
select, gis & gis-tree tests fails at the moment, but
I will push this CS because it was tested before and I'm absolutely
sure it's right.
2005-05-12 15:56:04 +05:00
jimw@mysql.com
2f398fc3ae
Update tests after merge of bug fix.
2005-04-05 20:55:06 -07:00
jimw@mysql.com
b95cb4e654
Merge
2005-04-05 19:45:34 -07:00
pem@mysql.comhem.se
b18ca48c47
Additional fix for BUG#5907: Traditional mode: invalid value can be inserted via a stored procedure
...
... make the handler catch too.
2005-04-05 15:49:10 +02:00
monty@mysql.com
1be0a0c82a
Now one gets an error if one tries to insert an invalid value via a stored procedure in STRICT mode. (Bug #5907 )
2005-04-05 00:32:48 +03:00
monty@mysql.com
5ba3f707f7
Don't use -lsupc++ with gcc 3.3 and below as this gives linking problems when linking staticly
...
Fix that mysql.proc works with new VARCHAR fields
Give warnings for wrong zero dates
2005-04-04 16:43:25 +03:00
monty@mysql.com
201ee3eb78
Invalid DEFAULT values for CREATE TABLE now generates errors. (Bug #5902 )
...
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 )
2005-04-01 15:04:50 +03:00
monty@mysql.com
b43b7dc128
Enabled more tests of STR_TO_DATE()
...
Fixed that datetime gives warning for zero dates in traditional mode
2005-03-30 23:41:42 +03:00
monty@mysql.com
332b7ed4a1
Give warnings if wrong date/time/datetime argument for STR_TO_DATE
...
Small fixes while doing review of new pushed code
More test cases for decimal
2005-03-30 16:00:31 +03:00
sergefp@mysql.com
ce564b2d7f
Updated tests results for BUG#8510
2005-03-15 10:27:44 +03:00
ramil@mysql.com
ec06f3e762
a fix (bug #9029 Traditional: Wrong SQLSTATE returned for string truncation).
2005-03-10 17:08:45 +04:00
monty@mysql.com
ee8c7a3eb5
After merge fixes
2005-02-22 18:30:40 +02:00
mleich@mysql.com
48bc6d477d
Merge mysql.com:/home/matthias/Arbeit/mysql-5.0/src
...
into mysql.com:/home/matthias/Arbeit/mysql-5.0/src-WL1420
2005-02-09 11:00:15 +01:00
hf@deer.(none)
b94a482ee9
Precision Math implementation
2005-02-09 02:50:45 +04:00
mleich@mysql.com
c1c4822bf3
Insertion of additional sub test cases checking DATA/TIME/TIMESTAMP
...
functionality into the test case "strict".
The additional sub test cases are part of the SoW6 test draft
(sow6-dates.test) written by Trudy/PeterG.
sow6-dates will be no longer needed, because "strict" contains with
this extension all sub test cases of sow6-dates.
2005-02-08 13:46:04 +01:00
ram@gw.mysql.r18.ru
f131e5a925
Merge rkalimullin@bk-internal.mysql.com:/home/bk/mysql-5.0
...
into gw.mysql.r18.ru:/usr/home/ram/work/5.0.b6999
2005-01-19 12:05:59 +04:00
ram@gw.mysql.r18.ru
c24c023e8c
A fix (bug #6999 : Traditional: Wrong SQLSTATE returned for string truncation).
2005-01-19 12:04:35 +04:00
monty@mysql.com
a37e91e435
Changed interface for my_strntod() to make it more general and more portable
2005-01-15 12:28:38 +02:00
jimw@mysql.com
01ddc370f0
Enable warnings for 'no default' fields being set to default when they
...
are not specified in an insert. Most of these changes are actually to
clean up the test suite to either specify defaults to avoid warnings,
or add the warnings to the results. Related to bug #5986 .
2005-01-14 17:09:35 -08:00
jimw@mysql.com
25fde2d092
In TRADITIONAL mode, don't allow a NOT NULL field with no default be set to
...
DEFAULT (with no argument) or to the field's type's default by not being
listed in the list of fields being inserted. (Bug #5986 )
2005-01-13 18:23:34 -08:00
bar@mysql.com
28ee79a732
strict.result, strict.test:
...
Clean-up for the previous change: VARCHAR and trailing spaces.
2005-01-11 23:28:57 +04:00
bar@mysql.com
691b3283d2
If VARCHAR strips only trailing spaces, then produce
...
a note, not a warning or error.
2005-01-11 16:49:45 +04:00
monty@mysql.com
77207d19f2
Merge with new VARCHAR code
2004-12-06 19:18:35 +02:00
monty@mysql.com
67ce247965
Add support for up to VARCHAR (size up to 65535)
...
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
2004-12-06 02:00:37 +02:00
mysqldev@mysql.com
051a5820e6
strict.result:
...
Add warning line to result so that test passes
2004-12-01 00:30:42 +01:00
serg@serg.mylan
ceb0d1cf87
compatibility fixes
2004-11-29 22:47:50 +01:00
ram@gw.mysql.r18.ru
47abf905a5
Portability fix: we had problems with -1.1E-38, -2.2E-308 values
...
on 64-bit platforms (due to compiler's optimization).
-1.1E-38 replaced with -1.1E-37
-2.2E-308 replaced with -2.2E-307
2004-11-26 14:02:39 +04:00
gluh@gluh.mysql.r18.ru
4c65a9447e
WL#1437 :don't create new users with GRANT
2004-11-02 17:45:26 +03:00
serg@serg.mylan
30947b7b0e
make linux to behave (like freebsd does :)
2004-10-20 14:13:07 +02:00
bell@sanja.is.com.ua
ffc8bd5986
changing results after test changing
2004-10-08 12:05:32 +03:00
monty@mishka.local
0fa62b691b
Fixed bug in strict mode (A state was not properly cleared on successful insert/update's)
2004-10-05 01:05:15 +03:00
monty@mishka.local
be4ca46fbe
More fixes for strict mode:
...
More tests.
Better error messages.
Fixed bug when checking if we updated all needed columns for INSERT.
Give an error if we encounter a wrong float value during parsing.
Don't print DEFAULT for columns without a default value in SHOW CREATE/SHOW FIELDS.
Fixed UPDATE IGNORE when using STRICT mode.
2004-10-02 22:20:08 +03:00
monty@mishka.local
f2941380c4
Strict mode & better warnings
...
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)
2004-09-28 20:08:00 +03:00