# Repeatable Read UPDATE WHERE clause sees latest committed (vs isolated) version

**URL:** <https://forums.percona.com/t/repeatable-read-update-where-clause-sees-latest-committed-vs-isolated-version/7250>\
**Category:** Percona Server for MySQL 5.6\
**Created:** [October 18, 2019, 12:30pm UTC](https://forums.percona.com/t/repeatable-read-update-where-clause-sees-latest-committed-vs-isolated-version/7250 "2019-10-18T12:30:38Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![billokara](https://avatars.discourse-cdn.com/v4/letter/b/898d66/32.png) [@billokara](https://forums.percona.com/u/billokara)\
**Post date:** [October 18, 2019, 12:30pm UTC](https://forums.percona.com/t/repeatable-read-update-where-clause-sees-latest-committed-vs-isolated-version/7250/1 "2019-10-18T12:30:38Z")

</div>

Hi,

With  
Version: 5.6.36-82.0 (Percona Server (GPL), Release 82.0, Revision 58e846a)

It seems like in a REPEATABLE\_READ session,

- the SELECT WHERE clause only sees the isolated version of a record (as expected)

- but the UPDATE WHERE clause sees the latest committed version (by another session, vs the isolated version) of a record

test example is as described in  
[URL][MySQL :: Repeatable Read update sees new value from another session](https://forums.mysql.com/read.php?22,678692,678692#msg-678692%5B/URL%5D)

and seemed like could potentially be related to  
[URL][MySQL Bugs: #95936: insert into ... select does not work with repeatable read](https://bugs.mysql.com/95936%5B/URL%5D)

just want to see if this behaviour is considered bug from a REPEATABLE\_READ isolation perspective? or not really?

Thanks!  
Bill