- 13 Jul, 2006 1 commit
-
-
evgen@moonbone.local authored
into moonbone.local:/home/evgen/bk-trees/mysql-5.0-opt
-
- 10 Jul, 2006 4 commits
-
-
gkodinov/kgeorge@macbook.gmz authored
-
gkodinov/kgeorge@macbook.gmz authored
into macbook.gmz:/Users/kgeorge/mysql/work/B14553-5.0-opt
-
gkodinov/kgeorge@macbook.gmz authored
into macbook.gmz:/Users/kgeorge/mysql/work/B14553-4.1-opt
-
To make MySQL compatible with some ODBC applications, you can find the AUTO_INCREMENT value for the last inserted row with the following query: SELECT * FROM tbl_name WHERE auto_col IS NULL. This is done with a special code that replaces 'auto_col IS NULL' with 'auto_col = LAST_INSERT_ID'. However this also resets the LAST_INSERT_ID to 0 as it uses it for a flag so as to ensure that only the first SELECT ... WHERE auto_col IS NULL after an INSERT has this special behaviour. In order to avoid resetting the LAST_INSERT_ID a special flag is introduced in the THD class. This flag is used to restrict the second and subsequent SELECTs instead of LAST_INSERT_ID.
-
- 07 Jul, 2006 1 commit
-
-
* portability fix: moved the macro call after the C declaration
-
- 06 Jul, 2006 6 commits
-
-
igor@olga.mysql.com authored
-
igor@olga.mysql.com authored
into olga.mysql.com:/home/igor/mysql-5.0-opt
-
igor@olga.mysql.com authored
into olga.mysql.com:/home/igor/mysql-4.1-opt
-
igor@olga.mysql.com authored
The implementation of the method Item_func_reverse::val_str for the REVERSE function modified the argument of the function. This led to wrong results for expressions that contained REVERSE(ref) if ref occurred somewhere else in the expressions.
-
gkodinov@rakia.(none) authored
into rakia.(none):/home/kgeorge/mysql/autopush/test
-
gkodinov@mysql.com authored
Adding decimal "digits" in multiplication resulted in signed overflow and producing wrong results. Fixed by using large enough buffers and intermediary result types : dec2 (currently longlong) to hold result of adding decimal "digits" (currently int32).
-
- 05 Jul, 2006 3 commits
-
-
tomas@poseidon.ndb.mysql.com authored
into poseidon.ndb.mysql.com:/home/tomas/mysql-5.0-main
-
tomas@poseidon.ndb.mysql.com authored
into poseidon.ndb.mysql.com:/home/tomas/mysql-5.0-main
-
tomas@poseidon.ndb.mysql.com authored
- remove some event code to get rid of some bugs
-
- 04 Jul, 2006 12 commits
-
-
knielsen@mysql.com authored
into mysql.com:/data0/knielsen/tmp-5.0
-
jonas@mc01.ndb.mysql.com authored
fix race in scan close
-
knielsen@mysql.com authored
into mysql.com:/data0/knielsen/tmp-5.0
-
jonas@perch.ndb.mysql.com authored
into perch.ndb.mysql.com:/home/jonas/src/mysql-5.0
-
tomas@poseidon.ndb.mysql.com authored
into poseidon.ndb.mysql.com:/home/tomas/mysql-5.0-main
-
knielsen@rt.int.sifira.dk authored
into rt.int.sifira.dk:/usr/local/mysql/tmp-5.0
-
tomas@poseidon.ndb.mysql.com authored
into poseidon.ndb.mysql.com:/home/tomas/mysql-5.0-release
-
tomas@poseidon.ndb.mysql.com authored
- partial backport of code from 5.1, do cot compare_record for engines that do not read all columns during update
-
sergefp@mysql.com authored
-
gkodinov@mysql.com authored
into mysql.com:/home/kgeorge/mysql/5.0/B16110
-
gkodinov@mysql.com authored
When compiling INSERT statements the check whether columns are provided values depends on the flag whether a field is used in that query (Field::query_id). However the check for updatability of VIEW columns (check_view_insertability()) was calling fix_fields() and thus setting the Field::query_id even for the view fields that are not referenced in the current INSERT statement. So the correct check for columns without default values ( check_that_all_fields_are_given_values() ) is assuming that all the VIEW columns were mentioned in the INSERT field list and was issuing no warnings or errors. Fixed check_view_insertability() to turn off the flag whether or not to set Field::query_id (THREAD::set_query_id) before calling fix fields and restore it when it's done.
-
jonas@perch.ndb.mysql.com authored
into perch.ndb.mysql.com:/home/jonas/src/mysql-5.0
-
- 03 Jul, 2006 7 commits
-
-
tomas@poseidon.ndb.mysql.com authored
into poseidon.ndb.mysql.com:/home/tomas/mysql-5.0-main
-
tnurnberg@mysql.com authored
Two functions have different ideas of what a string should look like; one of them reads memory it assumes the other one may have written. And "if you assume ..." We now use a more defensive variety of the assuming function, this fixes a warning thrown by the valgrind tool.
-
kent@mysql.com authored
Define 'mysql_get_ssl_cipher' even if no SSL built in, it is referenced in libmysql.def
-
kent@mysql.com authored
into mysql.com:/Users/kent/mysql/bk/mysql-5.0-release
-
kent@suse9-x86.mysql.com authored
Use Perl for filtering, do more filtering
-
kent@suse9-x86.mysql.com authored
Avoid duplicate symbol errors on Netware mwldnlm, mwccnlm, mwasmnlm: Filter garbage characters from output
-
gluh@mysql.com authored
into mysql.com:/home/gluh/MySQL/Merge/5.0-kt
-
- 01 Jul, 2006 5 commits
-
-
kent@mysql.com authored
Don't define __NT__ for 'Max' target
-
konstantin@mysql.com authored
into mysql.com:/opt/local/work/mysql-5.0-runtime
-
kent@mysql.com authored
Added missing parameter type change for _my_strdup_with_length()
-
sergefp@mysql.com authored
-
sergefp@mysql.com authored
into mysql.com:/home/psergey/mysql-5.0-bug16168-merge
-
- 30 Jun, 2006 1 commit
-
-
sergefp@mysql.com authored
into mysql.com:/home/psergey/mysql-5.0-bug16168-merge
-