php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login

go to bug id or search bugs for

Bug #71176 Updating records within a limit/offset loop misses records
Submitted: 2015-12-20 23:27 UTC Modified: 2015-12-21 01:45 UTC
From: espadav8 at gmail dot com Assigned:
Status: Not a bug Package: PDO PgSQL
PHP Version: 7.0.1 OS: OS X and Linux
Private report: No CVE-ID: None
View Add Comment Developer Edit
Welcome back! If you're the original bug submitter, here's where you can edit the bug or add additional notes.
If this is not your bug, you can add a comment by following this link.
If this is your bug, but you forgot your password, you can retrieve your password here.
Password:
Status:
Package:
Bug Type:
Summary:
From: espadav8 at gmail dot com
New email:
PHP Version: OS:

 

 [2015-12-20 23:27 UTC] espadav8 at gmail dot com 
Description:
------------
When looping over all records in the database using 'limit X offset Y' to update a column, the postgres PDO driver will start to return the same records again for different offset values. It gets worse the smaller the limit size compared to the dataset size.

Test script:
---------------
https://github.com/EspadaV8/laravel-chunking-non-persistance/blob/develop/public/pg-pdo-test.php

Script assumes that there is a database with a table called `example` with columns `id` (serial), `name` (text) and `name-new` (text).

Expected result:
----------------
ID: 72 - Name: 5677360fde707 - Name new: 5677360fde707-qwe
ID: 69 - Name: 5677360fdde80 - Name new: 5677360fdde80-qwe
ID: 70 - Name: 5677360fde241 - Name new: 5677360fde241-qwe
ID: 71 - Name: 5677360fde4c3 - Name new: 5677360fde4c3-qwe

Actual result:
--------------
Depending on the limit to dataset size (limit 1, 4 records)

ID: 62 - Name: 567735dbccacd - Name new: 567735dbccacd
ID: 64 - Name: 567735dbccffc - Name new: 567735dbccffc
ID: 63 - Name: 567735dbccd4c - Name new: 567735dbccd4c-qwe
ID: 61 - Name: 567735dbcc64b - Name new: 567735dbcc64b-qwe-qwe-qwe

or (limit 3, 4 records)

ID: 72 - Name: 5677360fde707 - Name new: 5677360fde707
ID: 69 - Name: 5677360fdde80 - Name new: 5677360fdde80-qwe
ID: 70 - Name: 5677360fde241 - Name new: 5677360fde241-qwe
ID: 71 - Name: 5677360fde4c3 - Name new: 5677360fde4c3-qwe-qwe

Patches

Add a Patch

Pull Requests

Add a Pull Request

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2015-12-21 01:45 UTC] requinix@php.net
-Status: Open +Status: Not a bug
 [2015-12-21 01:45 UTC] requinix@php.net 
http://www.postgresql.org/docs/current/static/queries-limit.html
> When using LIMIT, it is important to use an ORDER BY clause that constrains the
> result rows into a unique order. Otherwise you will get an unpredictable subset
> of the query's rows. You might be asking for the tenth through twentieth rows,
> but tenth through twentieth in what ordering? The ordering is unknown, unless
> you specified ORDER BY.
 
PHP Copyright © 2001-2024 The PHP Group
All rights reserved. 		Last updated: Tue Apr 23 21:01:31 2024 UTC