- 07 Jun, 2005 40 commits
-
-
lars@mysql.com authored
-
lars@mysql.com authored
-
petr@mysql.com authored
into mysql.com:/home/cps/mysql/trees/mysql-5.0
-
petr@mysql.com authored
-
igor@rurik.mysql.com authored
into rurik.mysql.com:/home/igor/mysql-5.0
-
igor@rurik.mysql.com authored
into rurik.mysql.com:/home/igor/mysql-5.0
-
petr@mysql.com authored
into mysql.com:/home/cps/mysql/trees/mysql-5.0
-
lenz@mysql.com authored
into mysql.com:/space/my/mysql-5.0
-
lenz@mysql.com authored
-
konstantin@mysql.com authored
into mysql.com:/opt/local/work/mysql-5.0-7306-final
-
petr@mysql.com authored
into mysql.com:/home/cps/mysql/trees/mysql-5.0
-
petr@mysql.com authored
-
igor@rurik.mysql.com authored
into rurik.mysql.com:/home/igor/dev/mysql-5.0-0
-
lars@mysql.com authored
-
konstantin@mysql.com authored
into mysql.com:/opt/local/work/mysql-5.0-7306-final
-
dlenev@mysql.com authored
into mysql.com:/home/dlenev/src/mysql-5.0-bg10015
-
dlenev@brandersnatch.localdomain authored
We should not allow explicit or implicit transaction commits inside of stored functions or triggers (so in autocommit mode we should not do commits after execution of sub-statement). Also since we don't support nested statement transactions in 5.0, we shouldn't commit or rollback stmt transactions while we are inside stored functions or triggers. This should be fixed in later (>=5.1) releases.
-
heikki@hundin.mysql.fi authored
into hundin.mysql.fi:/home/heikki/mysql-5.0
-
konstantin@mysql.com authored
-
into a193-229-222-105.elisa-laajakaista.fi:/home/my/bk/mysql-5.0
-
into a193-229-222-105.elisa-laajakaista.fi:/home/my/bk/mysql-5.0
-
lenz@mysql.com authored
into mysql.com:/space/my/mysql-5.0
-
joreland@mysql.com authored
better fix for bug#10190
-
lars@mysql.com authored
-
konstantin@mysql.com authored
error for LIMIT placeholder". The patch adds grammar support for LIMIT ?, ? and changes the type of ST_SELECT_LEX::select_limit,offset_limit from ha_rows to Item*, so that it can point to Item_param.
-
igor@rurik.mysql.com authored
into rurik.mysql.com:/home/igor/dev/mysql-5.0-0
-
igor@rurik.mysql.com authored
Fixed bug #11088: a crash for queries with GROUP BY a BLOB column + COUNT(DISTINCT...) due to an attempt to allocate a too large buffer for the BLOB field. Now the size of the buffer is limited by max_sort_length. group_by.test, group_by.result: Added a test case for bug #11088.
-
lars@mysql.com authored
into mysql.com:/home/bk/b6883-mysql-4.1
-
lars@mysql.com authored
-
lenz@mysql.com authored
-
heikki@hundin.mysql.fi authored
Update Monty's tests for AUTO-INC bug #11080 and bug #11005
-
heikki@hundin.mysql.fi authored
Update Monty's tests for AUTO-INC bug #11080 and bug #11005
-
heikki@hundin.mysql.fi authored
Update Monty's tests for AUTO-INC bug #11080 and bug #11005
-
elliot@mysql.com authored
into mysql.com:/Users/emurphy/src/work/mysql-4.1
-
elliot@mysql.com authored
-
bar@mysql.com authored
produces invalid query results mi_key.c: well_formed_length should be executed before space trimming, not after. ctype_utf8.test: ctype_utf8.result: adding test.
-
heikki@hundin.mysql.fi authored
Update the InnoDB internal auto-inc counter in ::write_row() if the statement is a REPLACE that fails in a duplicate key error: REPLACE will handle duplicate key error, and the insert will eventually succeed; note that we did NOT change InnoDB's behavior in an UPDATE, because updating the auto-inc counter in an UPDATE would require a bigger patch (Bug #11005)
-
joreland@mysql.com authored
into mysql.com:/home/jonas/src/mysql-5.0
-
because it's used also outside.
-
Moved some variable externs from sql_class.h to mysql_priv.h
-