An error occurred fetching the project authors.
- 23 Aug, 2005 1 commit
-
-
timour@mysql.com authored
* Provide backwards compatibility extension to name resolution of coalesced columns. The patch allows such columns to be qualified with a table (and db) name, as it is in 4.1. Based on a patch from Monty. * Adjusted tests accordingly to test both backwards compatible name resolution of qualified columns, and ANSI-style resolution of non-qualified columns. For this, each affected test has two versions - one with qualified columns, and one without.
-
- 19 Aug, 2005 1 commit
-
-
timour@mysql.com authored
- Corrected problem with N-way nested natural joins in PS mode. - Code cleanup - More asserts to check consistency of name resolution contexts - Fixed potential memory leak of name resolution contexts
-
- 18 Aug, 2005 3 commits
-
-
timour@mysql.com authored
Fixed debug printout.
-
timour@mysql.com authored
- Fixed minor error after Monty's review.
-
monty@mysql.com authored
-
- 13 Aug, 2005 1 commit
-
-
sanja@hasky.mysql.fi authored
remove unneeded multitable_view assignment sql_view.cc: fix potential memorry overrun in ref_array asssign multitable_view in time of view creation (BUG#12569)
-
- 12 Aug, 2005 1 commit
-
-
timour@mysql.com authored
"Process NATURAL and USING joins according to SQL:2003". * Some of the main problems fixed by the patch: - in "select *" queries the * expanded correctly according to ANSI for arbitrary natural/using joins - natural/using joins are correctly transformed into JOIN ... ON for any number/nesting of the joins. - column references are correctly resolved against natural joins of any nesting and combined with arbitrary other joins. * This patch also contains a fix for name resolution of items inside the ON condition of JOIN ... ON - in this case items must be resolved only against the JOIN operands. To support such 'local' name resolution, the patch introduces a stack of name resolution contexts used at parse time. NOTICE: - This patch is not complete in the sense that - there are 2 test cases that still do not pass - one in join.test, one in select.test. Both are marked with a comment "TODO: WL#2486". - it does not include a new test specific for the task
-
- 27 Jul, 2005 1 commit
-
-
monty@mysql.com authored
Change argument order to be database, tablename for some functions
-
- 22 Jul, 2005 1 commit
-
-
jimw@mysql.com authored
non-existent database. (Bug #10407)
-
- 01 Jul, 2005 1 commit
-
-
bell@sanja.is.com.ua authored
-
- 22 Jun, 2005 2 commits
-
-
jimw@mysql.com authored
-
svoj@mysql.com authored
Fix GCC 4.0 link failure. Better CXX_VERSION guessing.
-
- 19 Jun, 2005 1 commit
-
-
svoj@mysql.com authored
Fix for yaSSL link failures with Forte Developer 7, MIPSpro Compilers, Compaq C++. These compilers have problem with implicit template instantiation in archives (libyassl.a, libtaocrypt.a). Instantiate templates explicitly. Fix for yaSSL link failure on powermacg5 (gcc 3.3). When -O3 is specified gcc inlines __cxa_pure_virtual. This is wrong behavior, __cxa_pure_virtual must never be inlined.
-
- 17 Jun, 2005 2 commits
-
-
jimw@mysql.com authored
-
acurtis@xiphis.org authored
Implement new SQL mode - NO_ENGINE_SUBSTITUTION
-
- 15 Jun, 2005 1 commit
-
-
serg@serg.mylan authored
Item_buff -> Cached_item Item_arena -> Query_arena TEST_ASSERT -> YYERROR_UNLESS
-
- 01 Jun, 2005 1 commit
-
-
monty@mysql.com authored
Ensure we get error if INSERT IGNORE ... SELECT fails Fixed wrong key_part->key_length usage in index_merge
-
- 31 May, 2005 1 commit
-
-
pem@mysql.comhem.se authored
-
- 26 May, 2005 2 commits
-
-
pem@mysql.comhem.se authored
This only showed up on two known platforms, both ia64 (one HP-UX and one Linux wich icc). For some reason, they only get half the stack size they are supposed to have, which makes deep SP recursion overrun the stack before check_stack_overrun() is triggered. Also made som minor fixes in the check_stack_overrun() definition, supporting variable margins. No test case added, but the reason for the bug report was a failed existing test case on these machines, which now works.
-
monty@mysql.com authored
Moved detection of wrong decimal fields before decimal field was created to avoid ASSERT() for DECIMAL(1)
-
- 25 May, 2005 1 commit
-
-
monty@mysql.com authored
We will however give a warning when opening such a table that users should use ALTER TABLE ... FORCE to fix the table. In future release we will fix that REPAIR TABLE will be able to handle this case
-
- 18 May, 2005 1 commit
-
-
ingo@mysql.com authored
After review version. Added a condition for MERGE tables. These do not have unique indexes. But every key could be a unique key on the underlying MyISAM table. So get the maximum key length for MERGE tables instead of the maximum unique key length. This is used for buffer allocation in write_record().
-
- 10 May, 2005 1 commit
-
-
igor@rurik.mysql.com authored
Fixed bug #8528. Representation for single-table views was made similar to representation for multi-table views. view.test: Added test case for bug #8528. view.result: Added test case for bug #8528. Fixed other test cases.
-
- 07 May, 2005 1 commit
-
-
jimw@mysql.com authored
those from 5.0 with new datatypes. (Bug #10435)
-
- 12 Apr, 2005 1 commit
-
-
ramil@mysql.com authored
-
- 02 Apr, 2005 1 commit
-
-
bell@sanja.is.com.ua authored
- fixed bug in join view processing - postreview fixes (BUG#9398 & BUG#8703)
-
- 31 Mar, 2005 1 commit
-
-
joerg@mysql.com authored
Originally contained in 2005/03/03 19:51:29+01:00 serg@serg.mylan; contained in MySQL 4.1.10a; re-committed for archival purposes.
-
- 22 Mar, 2005 2 commits
-
-
jimw@mysql.com authored
the row type is dynamic (For 4.1 tables old 'VARCHAR' fields are converted to true VARCHAR in the next ALTER TABLE) This ensures that one can use MySQL 5.0 privilege tables with MySQL 4.1. (Fix imported from main 5.0 tree to 5.0.3 build tree.)
-
monty@mysql.com authored
Hack to ensure that CHAR's created in 5.0 are not converted to VARCHAR even if the row type is dynamic (For 4.1 tables old 'VARCHAR' fields are converted to true VARCHAR in the next ALTER TABLE) This ensures that one can use MySQL 5.0 privilege tables with MySQL 4.1
-
- 15 Mar, 2005 1 commit
-
-
monty@mysql.com authored
-
- 03 Mar, 2005 1 commit
-
-
serg@serg.mylan authored
-
- 26 Feb, 2005 1 commit
-
-
monty@mysql.com authored
Temporary patch to remove some warnings
-
- 23 Feb, 2005 1 commit
-
-
bell@52.0.168.192.in-addr.arpa authored
-
- 15 Feb, 2005 1 commit
-
-
igor@rurik.mysql.com authored
-
- 11 Feb, 2005 3 commits
-
-
igor@rurik.mysql.com authored
After revision of the fix for bug #7520. table.cc: Revised the fix for bug #7520. Made it compliant with 5.0 code where the bug does not exist.
-
ingo@mysql.com authored
-
igor@rurik.mysql.com authored
Added a test case for bug #7520. table.cc: Fixed bug #7520. The bug was caused by a wrong calculation of the field max_key_length for a TABLE structure when there was an index on a blob field.
-
- 10 Feb, 2005 1 commit
-
-
bell@sanja.is.com.ua authored
Better emulation correct SELECT tree for fields expressions of merging view during name resolving (BUG#6394)
-
- 31 Jan, 2005 1 commit
-
-
bell@sanja.is.com.ua authored
-
- 26 Jan, 2005 1 commit
-
-
georg@beethoven.site authored
(After review of cs georg:1.1800 by Monty)
-