| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
| |
cursor is interpreted latin1 character and Bug#9819 "Cursors: Mysql Server
Crash while fetching from table with 5 million records."
A fix for a possible memory leak when fetching into an SP cursor
in a long loop.
The patch uses a common implementation of cursors in the binary protocol and
in stored procedures and implements materialized cursors.
For implementation details, see comments in sql_cursor.cc
|
| |\
| |
| |
| | |
into mysql.com:/home/jimw/my/mysql-5.0-clean
|
| | | |
|
| |\ \
| | |
| | |
| | | |
into lmy004.:/work/mysql-5.0-bug11904
|
| | | | |
|
| |\ \ \
| |/ /
|/| |
| | | |
into mishka.local:/home/my/mysql-5.0
|
| | |\ \
| | |/
| | |
| | | |
into mishka.local:/home/my/mysql-5.0
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
create_tmp_field_from_item() was creating tmp field without regard to
original field type of Item. This results in wrong type being reported to
client.
To create_tmp_field_from_item() added special handling for Items with
DATE/TIME field types to preserve their type.
|
| |\ \ \
| |/ /
|/| |
| | | |
into mysql.com:/home/jimw/my/mysql-5.0-clean
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
* 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.
|
| |\ \ \
| | | |
| | | |
| | | | |
into mysql.com:/home/my/mysql-5.0
|
| | |\ \ \
| | | | |
| | | | |
| | | | | |
into mysql.com:/home/timka/mysql/src/5.0-2486-merge
|
| | | |/ /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
"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
|
| |/ / /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
restore it afterwards.
This allows us to use statement replication with functions and triggers
The following things are fixed with this patch:
- NOW() and automatic timestamps takes the value from the main event for functions and triggers (which allows these to replicate with statement level logging)
- No side effects for triggers or functions with auto-increment values(), last_insert_id(), rand() or found_rows()
- Triggers can't return result sets
Fixes bugs:
#12480: NOW() is not constant in a trigger
#12481: Using NOW() in a stored function breaks statement based replication
#12482: Triggers has side effects with auto_increment values
#11587: trigger causes lost connection error
|
| |\ \ \
| | |/
| |/|
| | | |
into xiphis.org:/usr/home/antony/work2/merge-5.0
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | | |
cursors (+ commit)" and Bug#11832 "Server crash with InnoDB + Cursors"
See comments to the changed files.
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
subqry order by server crash": failing DBUG_ASSERT(curr_join == this)
when opening a cursor.
Ensure that for top-level join curr_join == join (always),
and thus fix the failing assert.
curr_join is a hack to ensure that uncacheable subqueries can be
re-evaluated safely, and should be never different from main join
in case of top-level join.
|
| | |/
|/|
| |
| | |
CURSOR_TYPE_READ_ONLY nested queries corrupt result"
|
| |\ \
| |/
| |
| | |
into c-450ae253.1238-1-64736c10.cust.bredbandsbolaget.se:/home/pappa/mysql-5.0
|
| | |\
| | |
| | |
| | | |
into lmy002.wdf.sap.corp:/home/georg/work/mysql/prod/mysql-4.1
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
cursors. This should fix Bug#11813 when InnoDB part is in
(tested with a draft patch).
The idea of the patch is that if a storage engine supports
consistent read views, we open one when open a cursor,
set is as the active view when fetch from the cursor, and close
together with cursor close.
|
| |\ \ \
| | | |
| | | |
| | | | |
into mysql.com:/home/jimw/my/mysql-5.0-clean
|
| | | | | |
|
| | |\ \ \
| | |/ /
| | | |
| | | | |
into mysql.com:/home/jimw/my/mysql-5.0-clean
|
| | | |\ \
| | | |/
| | |/|
| | | | |
into linux.site:/home/reggie/bk/bug7142
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The problem here is that columns that have an especially long type
such as an enum type with many options would be longer than 40 chars
but the type column returned from show columns always was defined
as varchar(40).
This is fixed in 5.0 using info schema.
|
| | | |\ \
| | | | |
| | | | |
| | | | | |
into poseidon.ndb.mysql.com:/home/tomas/mysql-4.1-new
|
| | | | |/ |
|
| |/ / /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The idea of the patch
is that every cursor gets its own lock id for table level locking.
Thus cursors are protected from updates performed within the same
connection. Additionally a list of transient (must be closed at
commit) cursors is maintained and all transient cursors are closed
when necessary. Lastly, this patch adds support for deadlock
timeouts to TLL locking when using cursors.
+ post-review fixes.
|
| |\ \ \
| | | |
| | | |
| | | | |
into mishka.local:/home/my/mysql-5.0
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Changed defaults option --instance to --defaults-group-suffix
Changed option handling to allow --defaults-file, --defaults-extra-file and --defaults-group-suffix to be given in any order
Changed MYSQL_INSTANCE to MYSQL_GROUP_SUFFIX
mysql_print_defaults now understands --defaults-group-suffix
Remove usage of my_tempnam() (not safe function)
if( -> if ( and while( to while (
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | | |
test_client_character_set
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
When all rows are fetched subsequent calls to mysql_stmt_fetch return
now MYSQL_NO_DATA instead of errorcode 1.
|
| |\ \ \ \
| | |/ /
| |/| |
| | | | |
into mysql.com:/opt/local/work/mysql-5.0-root
|
| | | | |
| | | |
| | | |
| | | | |
information about error".
|
| |\ \ \ \
| |/ / /
| | | |
| | | | |
into mysql.com:/opt/local/work/mysql-5.0-root
|
| | | |/
| |/|
| | |
| | |
| | |
| | |
| | | |
No separate typecode for MEDIUMTEXT/LONGTEXT is added, as we
have no sound decision yet what typecodes and for what types are
sent by the server (aka what constitutes a distinct type in MySQL).
|
| | | |
| | |
| | |
| | | |
in cursors.
|
| | | | |
|
| | | |
| | |
| | |
| | | |
'double_data == o_double_data')
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | | |
Added api function mysql_get_character_set_info which provides
information about the current client character set.
|
| |\ \ \
| |/ / |
|
| | | |
| | |
| | |
| | |
| | | |
Added -I$(top_builddir)/include for searching
generated header files, when builddir != srcdir
|
