PHP :: Bug #68522 :: two transaction very much close,the other transaction select return null

Bug #68522

two transaction very much close,the other transaction select return null

Submitted:

2014-11-28 04:05 UTC

Modified:

2020-03-22 04:22 UTC

Votes:	2
Avg. Score:	3.0 ± 2.0
Reproduced:	0 of 0 (0.0%)

From:

hwawoon at 163 dot com

Assigned:

cmb (profile)

Status:

No Feedback

Package:

PDO MySQL

PHP Version:

5.5.19

OS:

ubuntu 12.04

Private report:

CVE-ID:

None

View Add Comment Developer Edit

Anyone can comment on a bug. Have a simpler test case? Does it work for you on a different platform? Let us know!
Just going to say 'Me too!'? Don't clutter the database with that please — but make sure to vote on the bug!

Your email address: MUST BE VALID
Solve the problem: 34 - 9 = ?
Subscribe to this entry?

[2014-11-28 04:05 UTC] hwawoon at 163 dot com

Description:
------------
enviroment:mysql 5.5 innodb table, php version:5.5.14
two transaction very much close , one transaction committd in the same commit,the other transation select that just committed row using fetchAll, return null. 

Expected result:
----------------
return array()

Actual result:
--------------
return null

Patches

Add a Patch

Pull Requests

Add a Pull Request

History

AllCommentsChangesGit/SVN commitsRelated reports

[2014-11-28 05:42 UTC] requinix@php.net

-Status: Open +Status: Feedback

[2014-11-28 05:42 UTC] requinix@php.net

Thank you for this bug report. To properly diagnose the problem, we
need a short but complete example script to be able to reproduce
this bug ourselves. 

A proper reproducing script starts with <?php and ends with ?>,
is max. 10-20 lines long and does not require any external 
resources such as databases, etc. If the script requires a 
database to demonstrate the issue, please make sure it creates 
all necessary tables, stored procedures etc.

Please avoid embedding huge scripts into the report.