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
jimw@mysql.com
99297e44d4
Merge mysql.com:/home/jimw/my/mysql-4.1-14155
...
into mysql.com:/home/jimw/my/mysql-5.0-clean
2005-11-28 10:50:23 -08:00
jimw@mysql.com
81cb8ad37d
Fix handling of maximum value for MAX_ROWS on 64-bit platforms. (Bug #14155 )
2005-11-23 17:05:59 -08:00
sergefp@mysql.com
c914a03066
BUG#14480 post-fix: merge to 5.0
2005-11-09 14:47:58 +03:00
sergefp@mysql.com
c6a902f20c
Merge mysql.com:/home/psergey/mysql-4.1-nov08-push
...
into mysql.com:/home/psergey/mysql-5.0-oct08-push
2005-11-09 10:12:58 +03:00
sergefp@mysql.com
f12212f74e
BUG#14480: post-fix: use the default field value from CREATE list too.
2005-11-09 09:34:46 +03:00
sergefp@mysql.com
c5276ebcb0
Merge, will need post-merge fixes.
2005-11-08 11:22:51 +03:00
sergefp@mysql.com
edd094b194
BUG#14480, attempt2: In CREATE ... SELECT ..., don't count the same field twice
...
when calculating table->null_fields.
2005-11-07 09:23:43 +03:00
sergefp@mysql.com
4ad3313cd7
BUG#14139 - Merge to 5.0
2005-10-31 09:22:33 +03:00
sergefp@mysql.com
09a4d0c7a7
4.1->5.0 merge
2005-10-29 02:36:57 +04:00
sergefp@mysql.com
2219ada7f6
BUG#14139: When handling "CREATE TABLE(field_X type_spec,...) SELECT smth AS field_X, ...."
...
avoid multiplying length of field_X by charset->mbmaxlen twice when calculating space
required for field_X in the new table.
2005-10-26 00:56:17 +04:00
andrey@lmy004.
72549b13c2
Merge ahristov@bk-internal.mysql.com:/home/bk/mysql-4.1
...
into lmy004.:/work/mysql-4.1-bug12913
2005-09-20 06:55:23 +03:00
jani@a193-229-222-105.elisa-laajakaista.fi
e760a58f07
Merged from 4.1 to 5.0.
2005-09-13 01:44:50 +03:00
jani@a193-229-222-105.elisa-laajakaista.fi
01ce8a8aa9
Merge a193-229-222-105.elisa-laajakaista.fi:/home/my/bk/mysql-4.1
...
into a193-229-222-105.elisa-laajakaista.fi:/home/my/bk/mysql-5.0
2005-09-12 20:18:49 +03:00
gluh@eagle.intranet.mysql.r18.ru
d9bd3c11e4
Fix for bug #6008 : MySQL does not create warnings when creating database and using IF NOT EXISTS
...
produce warning for 'create database if not exists' if database exists
do not update database options in this case
produce warning for 'create table if not exists' if table exists
2005-09-12 17:09:19 +05:00
andrey@lmy004.
f75ac7fb82
fix for bug#12913
...
(Simple SQL can crash server or connection)
(not initialized member leads to server crash)
2005-09-01 00:13:02 +02:00
evgen@moonbone.local
41fc00641c
create.test, create.result, sql_select.cc, item.cc:
...
After merge fix for bug #12537
2005-08-31 22:06:34 +04:00
evgen@moonbone.local
f917803e0c
Manual merged
2005-08-31 21:24:25 +04:00
evgen@moonbone.local
d76f9471cb
Fix bug #12537 UNION produces longtext instead of varchar
...
Item::tmp_table_field_from_field_type() and create_tmp_field_from_item()
was converting string field to blob depending on byte-wise length instead of
character length, which results in converting valid varchar string with
length == 86 to longtext.
Made that functions above take into account max width of character when
converting string fields to blobs.
2005-08-30 16:19:53 +04:00
jimw@mysql.com
2da798c991
Update test results
2005-08-04 14:38:48 -07:00
georg@lmy002.wdf.sap.corp
7251e9dbd8
Fix for bug #6859 (after Sanja's review)
...
Added check which throws ER_WRONG_OBJECT error in case the .frm
doesn't contain a valid table type (e.g. view or trigger)
2005-08-03 07:29:48 +02:00
jimw@mysql.com
49e5636410
Merge mysql.com:/home/jimw/my/mysql-4.1-clean
...
into mysql.com:/home/jimw/my/mysql-5.0-clean
2005-07-22 12:35:15 -07:00
jimw@mysql.com
6eae678f56
Fix error message generated when trying to create a table in a
...
non-existent database. (Bug #10407 )
2005-07-21 20:08:54 -07:00
acurtis@xiphis.org
3b8c3bd7e1
Merge
2005-06-09 17:15:06 +01:00
acurtis@xiphis.org
304bb0c66d
Bug#11028 Crash on create table like
...
Report error instead of crashing
2005-06-09 16:06:15 +01:00
hf@deer.(none)
6c148a7969
Fix for bug #9764 (DISTINCT IFNULL truncates data)
2005-06-08 20:35:37 +05:00
monty@mysql.com
775f17667b
Merge with 4.1
2005-06-07 00:31:53 +03:00
serg@serg.mylan
dc0df7ee5a
after mergemerge
2005-06-04 07:15:11 +02:00
serg@serg.mylan
aaa4c11d11
mergemerged
2005-06-03 21:24:13 +02:00
serg@serg.mylan
5b810bc607
after merge fixes
2005-06-03 21:08:45 +02:00
ingo@mysql.com
0a1e38b7ed
Bug#10224 - ANALYZE TABLE crashing with simultaneous CREATE ... SELECT statement.
...
Manual merge from 4.1.
2005-06-01 11:15:21 +02:00
ingo@mysql.com
effd338f67
Merge
2005-05-31 20:55:42 +02:00
ingo@mysql.com
40b53eab23
Bug#10224 - ANALYZE TABLE crashing with simultaneous CREATE ... SELECT statement.
...
After merge fix.
2005-05-31 20:45:41 +02:00
ingo@mysql.com
c420599581
Bug#10224 - ANALYZE TABLE crashing with simultaneous CREATE ... SELECT statement.
...
Hand merged from 4.0.
2005-05-31 19:37:24 +02:00
acurtis@xiphis.org
c4f37eda65
Bug#10413 - Invalid column name is not rejected
...
Stop ignoring name parts and check for validity
2005-05-31 18:06:54 +01:00
ingo@mysql.com
51d80960ea
Bug#10224 - ANALYZE TABLE crashing with simultaneous CREATE ... SELECT statement.
...
1.) Added a new option to mysql_lock_tables() for ignoring FLUSH TABLES.
Used the new option in create_table_from_items().
It is necessary to prevent the SELECT table from being reopend.
It would get new storage assigned for its fields, while the
SELECT part of the command would still use the old (freed) storage.
2.) Protected the CREATE TABLE and CREATE TABLE ... SELECT commands
against a global read lock. This prevents a deadlock in
CREATE TABLE ... SELECT in conjunction with FLUSH TABLES WITH READ LOCK
and avoids the creation of new tables during a global read lock.
3.) Replaced set_protect_against_global_read_lock() and
unset_protect_against_global_read_lock() by
wait_if_global_read_lock() and start_waiting_global_read_lock()
in the INSERT DELAYED handling.
2005-05-31 11:08:14 +02:00
antony@ltantony.mysql.com
4fe845e8d0
Merge
2005-05-07 16:50:22 +01:00
jimw@mysql.com
8c7d487ae7
Fix tests after merge
2005-05-07 08:25:59 -07:00
jimw@mysql.com
80933d9f95
Merge
2005-05-07 08:25:58 -07:00
antony@ltantony.mysql.com
a5e9523364
Merge ltantony.mysql.com:/usr/home/antony/work2/p4-bug9666
...
into ltantony.mysql.com:/usr/home/antony/work2/megapatch-4.1
2005-05-07 14:46:54 +01:00
antony@ltantony.mysql.com
1af671bf36
Bug#9666 - Can't use 'DEFAULT FALSE' for column of type bool
...
Fix bug by moving TRUE/FALSE in with other literals.
2005-05-07 13:51:29 +01:00
ramil@ram-book.(none)
bec93d485b
fix for bug #4082 : Integer lengths cause truncation with DISTINCT CONCAT and InnoDB
2005-05-06 20:11:01 +05:00
holyfoot@hf-ibm.(none)
8f3647005c
Tests and results fixed with last precision/decimal related modifications
2005-05-06 01:01:39 +05:00
gbichot@quadita2.mysql.com
b75789e3d8
Fixes for BUG#10039 "MEMORY engine is reported as HEAP",
...
BUG#9738 "SHOW VARIABLES still displays the deprecated 'log_update' in 5.0",
BUG#9542 "MySQL dies with signal 11 when it is using non-existent location of binary logs"
2005-04-23 00:05:05 +02:00
jimw@mysql.com
b95cb4e654
Merge
2005-04-05 19:45:34 -07: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
hf@deer.(none)
b94a482ee9
Precision Math implementation
2005-02-09 02:50:45 +04: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
3998da80e9
Output 'MEMORY' as table type for tables using the memory (nee heap) storage
...
engine, except when running with sql_mode & MYSQL323. (Bug #6659 )
2005-01-13 17:38:13 -08:00
gluh@gluh.mysql.r18.ru
2e912bbbe8
Don't display 'usage' privilege in TABLE_PRIVILEGES if we have columns privileges
...
mysqldump skips information_schema db
'use' now can use information_schema db
changed value of column 'Null' to 'NO' if column is not nullable
2004-12-10 12:07:11 +03:00