Bug #69847 btr_cur_optimistic_update() incorrectly documented to allow thr == NULL arg
| Submitted: | 26 Jul 2013 9:45 | Modified: | 3 Feb 2014 10:46 |
|---|---|---|---|
| Reporter: | Laurynas Biveinis (OCA) | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Server: InnoDB storage engine | Severity: | S3 (Non-critical) |
| Version: | 5.6 | OS: | Any |
| Assigned to: | CPU Architecture: | Any |
[26 Jul 2013 9:45]
Laurynas Biveinis
[26 Jul 2013 10:00]
Laurynas Biveinis
btr_cur_pessimistic_update() too.
[27 Jul 2013 5:57]
MySQL Verification Team
Hello Laurynas, Thank you for the report. Thanks, Umesh
[27 Nov 2013 13:12]
Daniel Price
Fixed as of 5.6.16, 5.7.4. Noted in 5.6.16, 5.7.4 changelogs: Comments in "btr0cur.cc" incorrectly stated that "btr_cur_pessimistic_update()" and "btr_cur_optimistic_update()" would accept a NULL value. Thank you for the bug report.
[3 Feb 2014 10:46]
Laurynas Biveinis
5.6$ bzr log -r 5653 ------------------------------------------------------------ revno: 5653 committer: Marko Mäkelä <marko.makela@oracle.com> branch nick: mysql-5.6 timestamp: Wed 2013-11-27 12:39:25 +0200 message: Bug#17231743 BTR_CUR_OPTIMISTIC_UPDATE() INCORRECTLY DOCUMENTED TO ALLOW THR == NULL ARG btr_cur_pessimistic_update(), btr_cur_optimistic_update(): Correct the comments in btr0cur.cc. The comments in btr0cur.h were already correct.
Portions of this website are copyright © 2001, 2002 The PHP Group
Page generated in 0.040 sec. using MySQL 8.4.7-u6-cloud
Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the
respective copyright holders.
It is not reviewed in advance
by Oracle and does not necessarily represent the opinion of
Oracle or any other party.