- 19 Jan, 2005 1 commit
-
-
unknown authored
-
- 18 Jan, 2005 39 commits
-
-
unknown authored
into poseidon.ndb.mysql.com:/home/tomas/mysql-5.0
-
unknown authored
-
unknown authored
client/Makefile.am: Don't use relative paths.
-
unknown authored
into mysql.com:/home/dlenev/src/mysql-5.0-merges client/Makefile.am: Auto merged strings/Makefile.am: Auto merged
-
unknown authored
into mysql.com:/home/dlenev/src/mysql-5.0-merges
-
unknown authored
into mysql.com:/home/dlenev/src/mysql-4.1-merges
-
unknown authored
into mysql.com:/usr/home/bar/mysql-5.0
-
unknown authored
after merge clean-up mysql-test/r/ps_6bdb.result: after merge clean-up mysql-test/r/ps_7ndb.result: after merge clean-up
-
unknown authored
into mysql.com:/home/dlenev/src/mysql-5.0-merges mysql-test/r/alter_table.result: Auto merged mysql-test/t/alter_table.test: Auto merged sql/field.h: Auto merged
-
unknown authored
into ua141d10.elisa.omakaista.fi:/home/my/bk/mysql-5.0
-
unknown authored
The old syntax works as well. WL#2356.
-
unknown authored
-
unknown authored
mysql-test/r/metadata.result: Auto merged sql/item_cmpfunc.cc: Auto merged
-
unknown authored
into mysql.com:/home/psergey/mysql-5.0-fix-vg1
-
unknown authored
into poseidon.ndb.mysql.com:/home/tomas/mysql-5.0
-
unknown authored
into gluh.mysql.r18.ru:/home/gluh/MySQL/mysql-5.0
-
unknown authored
-
unknown authored
compile warning: changed eq_range -> eq_r
-
unknown authored
into poseidon.ndb.mysql.com:/home/tomas/mysql-5.0
-
unknown authored
-
unknown authored
prefix", which roots were fixed in 4.0 tree. mysql-test/r/alter_table.result: Added test for bug #7884 "Able to add invalid unique index on TIMESTAMP prefix". mysql-test/t/alter_table.test: Added test for bug #7884 "Able to add invalid unique index on TIMESTAMP prefix".
-
unknown authored
-
unknown authored
client/Makefile.am: Remove explicit _DEPENDENCIES, they are not needed with automatic dependency tracking wich we started using several months ago. Don't use relative paths in makefiles. regex/Makefile.am: Remove explicit _DEPENDENCIES, they are not needed with automatic dependency tracking wich we started using several months ago. Don't use relative paths. strings/Makefile.am: Remove dead rule.
-
unknown authored
TIMESTAMP prefix" into 4.1 tree. sql/field.h: Manual merge.
-
unknown authored
into mysql.com:/home/dlenev/src/mysql-4.0-bg7884
-
unknown authored
macros. It does not fixes any bugs in 4.0. But it prevents from future error in any bugfixes that may use these macros. Also after merging into 4.1 tree this cleanup will fix bug #7884 "Able to add invalid unique index on TIMESTAMP prefix". sql/field.h: Since FIELDFLAG_INTERVAL, FIELDFLAG_BITFIELD, FIELDFLAG_BLOB and FIELDFLAG_GEOM flags occupy the same space as number of decimals for FIELDFLAG_NUMBER fields, it is safer to check in "f_is_geom()"-type macros that we have non-number field, like we already do in f_is_blob() macro.
-
unknown authored
into mysql.com:/home/psergey/mysql-5.0-fix-vg1
-
unknown authored
into mysql.com:/home/mysql_src/mysql-5.0-clean
-
unknown authored
into mysql.com:/home/psergey/mysql-5.0-fix-vg1
-
unknown authored
5.0 has a different way of knowing if master is < 3.23.57 sql/slave.cc: 5.0 has a different way of knowing if master is < 3.23.57
-
unknown authored
into mysql.com:/home/kostja/work/mysql-5.0-root configure.in: Auto merged
-
unknown authored
into mysql.com:/home/mysql_src/mysql-5.0-clean
-
unknown authored
-
unknown 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. mysql-test/r/analyse.result: 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. mysql-test/r/case.result: Test fix according to the changes mysql-test/r/metadata.result: Test fix according to the changes mysql-test/r/ps_1general.result: Test fix according to the changes mysql-test/r/ps_2myisam.result: Test fix according to the changes mysql-test/r/ps_3innodb.result: Test fix according to the changes mysql-test/r/ps_4heap.result: Test fix according to the changes mysql-test/r/ps_5merge.result: Test fix according to the changes mysql-test/r/ps_6bdb.result: Test fix according to the changes mysql-test/r/ps_7ndb.result: Test fix according to the changes mysql-test/r/union.result: Test fix according to the changes sql/item.cc: Item is now BINARY by default sql/item_cmpfunc.cc: IFNULL now collects arguments collations/charsets like other functions do.
-
unknown authored
-
unknown authored
-
unknown authored
into mysql.com:/home/mysql_src/mysql-4.1-clean
-
unknown authored
into poseidon.ndb.mysql.com:/home/tomas/mysql-5.0 client/mysql.cc: Auto merged myisam/mi_open.c: Auto merged
-
unknown authored
into mysql.com:/space/my/mysql-4.0
-