into  station.:/mnt/raid/alik/MySQL/devel/5.1-rt-merged-5.0-rt

into  station.:/mnt/raid/alik/MySQL/devel/5.1-rt

into  station.:/mnt/raid/alik/MySQL/devel/5.0-rt

into  bodhi.(none):/opt/local/work/mysql-5.1-runtime

into  mysql.com:/home/gluh/MySQL/Merge/5.1-opt

into  damien-katzs-computer.local:/Users/dkatz/51runtime

into  mysql.com:/Users/davi/mysql/mysql-5.1-runtime

into  mysql.com:/home/gluh/MySQL/Merge/5.1-opt

into  mysql.com:/home/gluh/MySQL/Merge/5.1-opt

into  mysql.com:/home/gluh/MySQL/Merge/5.1-opt

into  mysql.com:/home/gluh/MySQL/Merge/5.0-opt

into  mysql.com:/home/gluh/MySQL/Merge/5.0-opt

into  mysql.com:/home/psergey/mysql-5.0-bug32198

- Make conditions like "date_col $CMP$ 'datetime-const'" range-sargable

into  mysql.com:/home/gluh/MySQL/Merge/4.1-opt

into  station.:/mnt/raid/alik/MySQL/devel/5.1-rt

into  station.:/mnt/raid/alik/MySQL/devel/5.0-rt

last_insert_id introduced by the patch for Bug#12713 (part 1)

The problem is that some DDL statements (ALTER TABLE, CREATE
TRIGGER, FLUSH TABLES, ...) when under LOCK TABLES need to
momentarily drop the lock, reopen the table and grab the write
lock again (using reopen_tables). When grabbing the lock again,
reopen_tables doesn't pass a flag to mysql_lock_tables in
order to ignore the impending global read lock, which causes a
assertion because LOCK_open is being hold. Also dropping the
lock must not signal to any threads that the table has been
relinquished (related to the locking/flushing protocol).

The solution is to correct the way the table is reopenned
and the locks grabbed. When reopening the table and under
LOCK TABLES, the table version should be set to 0 so other
threads have to wait for the table. When grabbing the lock,
any other flush should be ignored because it's theoretically
a atomic operation. The chosen solution also fixes a potential
discrepancy between binlog and GRL (global read lock) because
table placeholders were being ignored, now a FLUSH TABLES WITH
READ LOCK will properly for table with open placeholders.

It's also important to mention that this patch doesn't fix
a potential deadlock if one uses two GRLs under LOCK TABLES
concurrently.

into  stella.local:/home2/mydev/mysql-5.1-axmrg

Fixed case of comment.

into  damien-katzs-computer.local:/Users/dkatz/mysql-5.1-runtime

Ensure default logging is "file" logging, for additional ways the option can be turned on. Verified on OS X, but not tested automatically.

into  bodhi.(none):/opt/local/work/mysql-5.1-12713-1

cause ROLLBACK of statement", part 1. Review fixes.

Do not send OK/EOF packets to the client until we reached the end of 
the current statement.
This is a consolidation, to keep the functionality that is shared by all 
SQL statements in one place in the server.
Currently this functionality includes:
- close_thread_tables()
- log_slow_statement().

After this patch and the subsequent patch for Bug#12713, it shall also include:
- ha_autocommit_or_rollback()
- net_end_statement()
- query_cache_end_of_result().

In future it may also include:
- mysql_reset_thd_for_next_command().

into  bodhi.(none):/opt/local/work/mysql-5.1-runtime

into  bodhi.(none):/opt/local/work/mysql-5.1-runtime

into  bodhi.(none):/opt/local/work/mysql-5.0-runtime

into  stella.local:/home2/mydev/mysql-5.1-axmrg

into  stella.local:/home2/mydev/mysql-5.1-axmrg