An error occurred fetching the project authors.
- 09 Mar, 2005 1 commit
-
-
acurtis@pcgem.rdg.cyberkinetica.com authored
-
- 04 Mar, 2005 5 commits
-
-
acurtis@pcgem.rdg.cyberkinetica.com authored
Crashes with stored procedure return non-string values Also fixes Bug#2773
-
hf@deer.(none) authored
-
hf@deer.(none) authored
-
dlenev@brandersnatch.localdomain authored
and some SP-related cleanups. - We don't have separate stage for calculation of list of tables to be prelocked and doing implicit LOCK/UNLOCK any more. Instead we calculate this list at open_tables() and do implicit LOCK in lock_tables() (and UNLOCK in close_thread_tables()). Also now we support cases when same table (with same alias) is used several times in the same query in SP. - Cleaned up execution of SP. Moved all common code which handles LEX and does preparations before statement execution or complex expression evaluation to auxilary sp_lex_keeper class. Now all statements in SP (and corresponding instructions) that evaluate expression which can contain subquery have their own LEX.
-
bar@mysql.com authored
fixing test results accordingly. func_system.test: New test that illegal mix of collations does not happen anymore. item_strfunc.h: safe_charset_converter() was added for system constants. item_strfunc.cc: safe_charset_converter() was added for system constants. item_func.cc, item.h, item.cc: Bug#8291: Illegal collation mix with USER() function. After discussion with PeterG and Serge, a new coercibility level for "system constants" was introduced, between COERRIBLE and IMPLICIT. Thus: SELECT col1 = USER() FROM t1; - is done according to col1 collation. SELECT 'string' = USER(); - is done according to USER() collation. At the same time, "nagg" and "strong" members were removed as unused. item_create.cc: Version is a system constant too.
-
- 02 Mar, 2005 2 commits
-
-
guilhem@mysql.com authored
First part of fix for BUG#7998 "Replication should be more clever about when to replicate RELEASE_LOCK()" (next part is updating test results)
-
serg@serg.mylan authored
deadlock in MYSQL_LOG::new_file() style fixes
-
- 24 Feb, 2005 1 commit
-
-
jimw@mysql.com authored
-
- 22 Feb, 2005 1 commit
-
-
bar@mysql.com authored
independently from the expression it is initialized from. In other words, this change treats a user variable like a table with one column and one record. Discussed with PeterG, Serg and Lars. This change also simplifies replication allowing not to replicate variables' coercibility.
-
- 19 Feb, 2005 1 commit
-
-
monty@mysql.com authored
Lots of small fixes to multi-precision-math path Give Note for '123.4e' Added helper functions type 'val_string_from_real() Don't give warnings for end space for string2decimal() Changed storage of values for SP so that we can detect length of argument without strlen() Changed interface for str2dec() so that we must supple the pointer to the last character in the buffer
-
- 18 Feb, 2005 1 commit
-
-
georg@beethoven.site authored
-
- 11 Feb, 2005 1 commit
-
-
mskold@mysql.com authored
-
- 08 Feb, 2005 3 commits
-
-
hf@deer.(none) authored
-
pem@mysql.comhem.se authored
Collect all tables and SPs refered by a statement, and open all tables with an implicit LOCK TABLES. Do find things refered by triggers and views, we open them first (and then repeat this until nothing new is found), before doing the actual lock tables.
-
monty@mysql.com authored
Ensure that references in HAVING, ORDER BY or GROUP BY are calculated after fields in SELECT. This will ensure that any reference to these has a valid value. Generalized the code for split_sum_func()
-
- 07 Feb, 2005 1 commit
-
-
monty@mysql.com authored
(BUG 8216)
-
- 05 Feb, 2005 1 commit
-
-
monty@mysql.com authored
Cleanup during reviews of new pushed code
-
- 04 Feb, 2005 1 commit
-
-
serg@serg.mylan authored
ftbw->off wasn't cleared on reinit - Bug#8234
-
- 03 Feb, 2005 1 commit
-
-
acurtis@pcgem.rdg.cyberkinetica.com authored
Fix crash with LAST_INSERT_ID() in UPDATE, Tests included,
-
- 27 Jan, 2005 1 commit
-
-
serg@serg.mylan authored
fix for binlog+autocommit+tclog comments, style fixes
-
- 24 Jan, 2005 1 commit
-
-
bell@sanja.is.com.ua authored
fixed cols() method call (it have to be called only after fix_fields())
-
- 20 Jan, 2005 1 commit
-
-
bell@sanja.is.com.ua authored
-
- 06 Jan, 2005 1 commit
-
-
monty@mysql.com authored
Split TABLE to TABLE and TABLE_SHARE (TABLE_SHARE is still allocated as part of table, will be fixed soon) Created Field::make_field() and made Field_num::make_field() to call this Added 'TABLE_SHARE->db' that points to database name; Changed all usage of table_cache_key as database name to use this instead Changed field->table_name to point to pointer to alias. This allows us to change alias for a table by just updating one pointer. Renamed TABLE_SHARE->real_name to table_name Renamed TABLE->table_name to alias Renamed TABLE_LIST->real_name to table_name
-
- 05 Jan, 2005 1 commit
-
-
bell@sanja.is.com.ua authored
-
- 31 Dec, 2004 1 commit
-
-
monty@mysql.com authored
Cleanup of mi_print_error() handling Deleted 'merge' directory
-
- 23 Dec, 2004 1 commit
-
-
acurtis@pcgem.rdg.cyberkinetica.com authored
Implement fine-grained control over access to stored procedures Privileges are cached (same way as existing table/column privs)
-
- 20 Dec, 2004 2 commits
-
-
mskold@mysql.com authored
-
ram@gw.mysql.r18.ru authored
-
- 17 Dec, 2004 2 commits
-
-
mskold@mysql.com authored
-
sergefp@mysql.com authored
For numeric constants we only need to add, since the parser doesn't produce negative numbers. For strings we only add (we actually could substract 1 if given string is a constant and it has '-number' form but we're not doing that because * we set max_length bigger then necessary in other cases as well. * the current solution is simpler and safer (bigger max_length is better then cutting out)
-
- 14 Dec, 2004 1 commit
-
-
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 2 commits
-
-
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
-
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).
-
- 07 Dec, 2004 1 commit
-
-
monty@mysql.com authored
Fixed compiler warnings String results in CREATE ... SELECT are now created as CHAR(0), VARCHAR(X) or TEXT() depending on item->max_length
-
- 03 Dec, 2004 1 commit
-
-
mats@mysql.com authored
CREATE DATABASE statement used the current database instead of the database created when checking conditions for replication. CREATE/DROP/ALTER DATABASE statements are now replicated based on the manipulated database.
-
- 02 Dec, 2004 1 commit
-
-
serg@serg.mylan authored
-
- 28 Nov, 2004 1 commit
-
-
serg@serg.mylan authored
-
- 19 Nov, 2004 1 commit
-
-
bar@mysql.com authored
Also, Item_sum_hybrid->charset was removed as redundant, and switched to use collation.collation instead.
-
- 17 Nov, 2004 1 commit
-
-
bell@sanja.is.com.ua authored
-