php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Bug #44437 Incomplete data coming at front end
Submitted: 2008-03-14 18:46 UTC Modified: 2008-03-24 01:00 UTC
Votes:3
Avg. Score:5.0 ± 0.0
Reproduced:3 of 3 (100.0%)
Same Version:3 (100.0%)
Same OS:3 (100.0%)
From: nishant dot agg at gmail dot com Assigned:
Status: No Feedback Package: Output Control
PHP Version: 5.2.5 OS: Windows Server 2003
Private report: No CVE-ID: None
View Add Comment Developer Edit
Welcome! If you don't have a Git account, you can't do anything here.
You can add a comment by following this link or if you reported this bug, you can edit this bug over here.
(description)
Block user comment
Status: Assign to:
Package:
Bug Type:
Summary:
From: nishant dot agg at gmail dot com
New email:
PHP Version: OS:

 

 [2008-03-14 18:46 UTC] nishant dot agg at gmail dot com
Description:
------------
hi,

I am retrieving some data from myql database onto my php page. The problem is that the data which is fetched from mysql is not complete. Say i have 120 rows in aparticular table in my database but when i check the record on front end it gives me less number of rows say 100 rows or 90 rows. Th bottom line is that i am unable to fetch the complete data from the database.
I am not exactly aware of whther it is an php bug or what but please do solve this issue , My project is stuck in between because of this shit.......
Please do the needfull


Patches

Add a Patch

Pull Requests

Add a Pull Request

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2008-03-14 22:58 UTC] johannes@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.
 [2008-03-15 07:52 UTC] nishant dot agg at gmail dot com
Hi thanx for that early reply.........
Due to security issue i cant provide you with the script..........
if possible kindly suggest me some points to check this problem....Also the data site performance is very very slow...........
 [2008-03-17 00:28 UTC] jani@php.net
Take the huge script you're thinking of and tear it down into the relevant small part that really is relevant here. Then you shouldn't have any "security" issues. As was requested: SHORT script, copy'n'pasteable from the report.
 [2008-03-24 01:00 UTC] php-bugs at lists dot php dot net
No feedback was provided for this bug for over a week, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".
 [2008-08-17 13:30 UTC] phpnet at ukmall dot net
Nishat is referring to tables in range of 120 rows. Someone suggests split of huge data. That amuses me because I have 600000 and 900000 rows in two tables and am looking solution to inability to fetch array, beyond those numbers. Nishant's problem must lie somewhere in scripts and not data size.
 
PHP Copyright © 2001-2022 The PHP Group
All rights reserved.
Last updated: Thu Oct 06 17:05:51 2022 UTC