- 14 Dec, 2004 3 commits
-
-
ram@gw.mysql.r18.ru authored
-
sergefp@mysql.com authored
into mysql.com:/dbdata/psergey/mysql-4.1-merge-fix
-
sergefp@mysql.com authored
* Backport of safety measures from 5.0: make numeorous replaces: s/item->fix_fields()/if (!item->fixed) item->fix_fields()
-
- 13 Dec, 2004 28 commits
-
-
jimw@mysql.com authored
into mysql.com:/home/jwinstead2/mysql-4.1
-
sergefp@mysql.com authored
* Added Item_ref::set_properties * Item_ref::Item_ref now expects to get in *item either NULL - then fix_fields() will be called later or ptr to Item it will refer to - then an equivalent of fix_fields() call is performed
-
guilhem@mysql.com authored
into mysql.com:/home/mysql_src/mysql-4.1-clean
-
lenz@mysql.com authored
without the PS protocol
-
mwagner@here.mwagner.org authored
s/spaces/TAB/
-
mwagner@here.mwagner.org authored
Add running of test suite with --ps-protocol to 'test' target
-
jimw@mysql.com authored
into mysql.com:/home/jwinstead2/mysql-4.1
-
sergefp@mysql.com authored
into mysql.com:/dbdata/psergey/mysql-4.1-merge
-
sergefp@mysql.com authored
-
sergefp@mysql.com authored
-
sergefp@mysql.com authored
The problem in 4.1 was the same as in 4.0 - fix_fields() not called for created Item_ref. The fix is similar too - initialize Item_refs in ctor (but don't interfere with cases when Item_ref is used by subselects).
-
guilhem@mysql.com authored
into mysql.com:/home/mysql_src/mysql-4.1-clean
-
acurtis@pcgem.rdg.cyberkinetica.com authored
into pcgem.rdg.cyberkinetica.com:/usr/home/acurtis/work/wl2274.2
-
guilhem@mysql.com authored
-
tomas@poseidon.ndb.mysql.com authored
into poseidon.ndb.mysql.com:/home/tomas/mysql-4.1-clean
-
tomas@poseidon.ndb.mysql.com authored
quick fix for wrong allocation of size
-
bell@sanja.is.com.ua authored
into sanja.is.com.ua:/home/bell/mysql/bk/mysql-4.1
-
bell@sanja.is.com.ua authored
-
tomas@poseidon.ndb.mysql.com authored
into poseidon.ndb.mysql.com:/home/tomas/mysql-4.1-clean
-
tomas@poseidon.ndb.mysql.com authored
changed back to just restricting max meta objects in dict to make sure we can "always" configure ourselves out of unforseen limits
-
bell@sanja.is.com.ua authored
into sanja.is.com.ua:/home/bell/mysql/bk/work-ref-4.1
-
bell@sanja.is.com.ua authored
-
tomas@poseidon.ndb.mysql.com authored
-
acurtis@pcgem.rdg.cyberkinetica.com authored
UPDATE clause conflicts with SELECT for use of item_list field. Alter UPDATE clause to use new lex field update_list Tests included
-
-
tomas@poseidon.ndb.mysql.com authored
+ fixed testcase
-
marko@hundin.mysql.fi authored
dict_load_table(): detect the new table format of MySQL 5.0.3
-
bell@sanja.is.com.ua authored
-
- 12 Dec, 2004 5 commits
-
-
tomas@poseidon.ndb.mysql.com authored
into poseidon.ndb.mysql.com:/home/tomas/mysql-4.1-clean
-
tomas@poseidon.ndb.mysql.com authored
changed help text
-
tomas@poseidon.ndb.mysql.com authored
added start backup parameter to enable setting wait state and set different timeouts depending on waitstate moved listen of backup event out of backup and into separete thread thread created at connect() and destroyed at disconnect() added start backup command options "nowait" "wait completed" "wait started" fixed log level settings
-
bell@sanja.is.com.ua authored
into sanja.is.com.ua:/home/bell/mysql/bk/work-ref-4.1
-
bell@sanja.is.com.ua authored
-
- 11 Dec, 2004 4 commits
-
-
sergefp@mysql.com authored
-
sergefp@mysql.com authored
into mysql.com:/dbdata/psergey/mysql-4.0-bug6976
-
sergefp@mysql.com authored
In Item_ref::Item_ref set maybe_null (and other fields fix_fields sets) to be the same as in (*ref), because Item_ref::fix_fields() will not be called. Previously maybe_null was 0 always and this produced a bogus state where maybe_null==0 && is_null() == true which broke evaluation for some upper-level Items, like AND and OR.
-
bell@sanja.is.com.ua authored
refernces if subqueri is not in HAVING clause (BUG#7079) and the same used for subquery transformetion
-