Bug #20885 innodb_lock_wait_timeout at a session level

Description:
Hi,

I want to set innodb_lock_wait_timeout at session level.
Now, when I set innodb_lock_wait_timeout, I get following error.

| scott:scott> SET SESSION innodb_lock_wait_timeout = 1;
| ERROR 1193 (HY000): Unknown system variable 'innodb_lock_wait_timeout'

If InnoDB can set this parameter at session level,
we may consider that InnoDB supports 'SELECT ... FOR UPDATE NOWAIT' statement.
So it is very useful for to migrate from Oracle to MySQL.

Sincerely,

How to repeat:
N/A

Suggested fix:
InnoDB can set innodb_lock_wait_timeout at session level.

Thank you for a reasonable feature request.

Best solution is 'SELECT ... FOR UPDATE NOWAIT'

Yes I also will be verry happy if there was this function like in ORACLE..
Verry verry usefull. Because using GET_LOCK and RELEASE_LOCK is not always verry comfortant..

Seems to be a duplicate of bug#36285, which will be included in the InnoDB plugin.

This would be very helpfull - either to be able to set the innodb_wait_timeout
to zero - or to be able to use the NOWAIT qualifier like Oracle does.

Our application was originally designed for NOWAIT on a select for update
instruction.  It works well in Oracle - But in MySql every once in a while
we run into issues because it will wait for the record based on the innodb_wait_timeout variable.

Ideally - it would be nice to be able to set this variable to zero (system wide)
If the variable is set to a value other than zero then wait the specified amount of time.  If the SQL Select Statement has a NOWAIT clause at the end - then regardless of the variable value - don't wait.

Bug #36285 is the same incident, and is resolved by InnoDB Plugin.
http://bugs.mysql.com/bug.php?id=36285

So please close this Bug #20885.
Thanks.

Thank you for the feedback.