Memory Limit for for HTML pages??

[Vic Spainhower]

Hello,

I have a php program that is building a grid (HTML table) from a MySQL
database. The problems started when I added a dropdown menu to the grid and
when I did the form buttons would not work when there were a few values in
the drop-down. If I removed the values so it was an empty drop-down menu the
form buttons would work. I thought there was a problem with my drop-down
which is a quite simple menu.

However, what I discovered is that it has to do with the size of the table
that I am building. I changed the query so that it would only pick up about
1/2 the records (134 vs 248) which is where it works (the 135th record
causes the buttons to quit working. It is not a data problem because I then
tested with a different set of data and it would also fail but at a
different spot.

I must be running into some kind of memory limit but I have no idea what it
is! Can someone help?

Vic

[Iván Sánchez Ortega]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Vic Spainhower wrote:

I must be running into some kind of memory limit but I have no idea what
it is! Can someone help?

You may be hitting PHP's 8 MB memory limit. That value is a default, so if
you really *need* to run a script which consumes more memory than that,
edit your php.ini file in order to change the memory limit value...

- --
- ----------------------------------
Iván Sánchez Ortega -i-punto-sanchez--arroba-mirame-punto-net

Me acuerdo de que hace años un DECman tenía que actualizar el microcódigo de
un VAX 8250 y le mandaron un floppy por mensajero. El floppy resultó
ilegible, y el decman lo devolvió con una nota en la que se podía leer:

%BADFLOPPY-F-VESPINOISNOTALLOWED; This diskette has been demagnetised. The
compatibility of this hardware with a Vespino's Magneto has not been
certified. Please use a Taxi.
--Jordi Guillaumes.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)

iD8DBQFDmh7M3jcQ2mg3Pc8RAnbFAJ4jPa6FzDCvqE7yVbTXWO enzZmR6ACeNhMc
UTC6KxItaT3cJIiDtiS57Q4=
=Dtsg
-----END PGP SIGNATURE-----

[Vic Spainhower]

Ivan,

I don't think it's the 8meg limit because the HTML is being built correctly.
I can take the generated html and create another page and it fails in the
same way.

Vic
"Iván Sánchez Ortega" <i.***************@rroba--mirame.punto.net> wrote in
message news:nf************@blackspark.escomposlinux.org.. .

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Vic Spainhower wrote:

I must be running into some kind of memory limit but I have no idea what
it is! Can someone help?

You may be hitting PHP's 8 MB memory limit. That value is a default, so if
you really *need* to run a script which consumes more memory than that,
edit your php.ini file in order to change the memory limit value...

- --
- ----------------------------------
Iván Sánchez Ortega -i-punto-sanchez--arroba-mirame-punto-net

Me acuerdo de que hace años un DECman tenía que actualizar el microcódigo
de
un VAX 8250 y le mandaron un floppy por mensajero. El floppy resultó
ilegible, y el decman lo devolvió con una nota en la que se podía leer:

%BADFLOPPY-F-VESPINOISNOTALLOWED; This diskette has been demagnetised. The
compatibility of this hardware with a Vespino's Magneto has not been
certified. Please use a Taxi.
--Jordi Guillaumes.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)

iD8DBQFDmh7M3jcQ2mg3Pc8RAnbFAJ4jPa6FzDCvqE7yVbTXWO enzZmR6ACeNhMc
UTC6KxItaT3cJIiDtiS57Q4=
=Dtsg
-----END PGP SIGNATURE-----

[maraguida]

Vic Spainhower wrote:

I have a php program that is building a grid (HTML table) from a MySQL
database. The problems started when I added a dropdown menu to the grid and
when I did the form buttons would not work when there were a few values in
the drop-down. ...

However, what I discovered is that it has to do with the size of the table
that I am building. I changed the query so that it would only pick up about
1/2 the records (134 vs 248) which is where it works (the 135th record
causes the buttons to quit working. It is not a data problem because I then
tested with a different set of data and it would also fail but at a
different spot.

Are you sure it is not a data problem?
Can you try the dropdown with just the 135th record?

[Vic Spainhower]

Maraguida,

I changed the query so that it would only pick up records starting with the
135th record. With this set of records it is ok the button works. So I
believe this indicates that it is not a data problem.

Vic

<ma*******@gmail.com> wrote in message
news:11*********************@g14g2000cwa.googlegro ups.com...

Vic Spainhower wrote:

I have a php program that is building a grid (HTML table) from a MySQL
database. The problems started when I added a dropdown menu to the grid
and
when I did the form buttons would not work when there were a few values
in
the drop-down. ...

However, what I discovered is that it has to do with the size of the
table
that I am building. I changed the query so that it would only pick up
about
1/2 the records (134 vs 248) which is where it works (the 135th record
causes the buttons to quit working. It is not a data problem because I
then
tested with a different set of data and it would also fail but at a
different spot.

Are you sure it is not a data problem?
Can you try the dropdown with just the 135th record?

[Oli Filth]

Vic Spainhower said the following on 09/12/2005 23:30:

Hello,

I have a php program that is building a grid (HTML table) from a MySQL
database. The problems started when I added a dropdown menu to the grid and
when I did the form buttons would not work when there were a few values in
the drop-down. If I removed the values so it was an empty drop-down menu the
form buttons would work. I thought there was a problem with my drop-down
which is a quite simple menu.

However, what I discovered is that it has to do with the size of the table
that I am building. I changed the query so that it would only pick up about
1/2 the records (134 vs 248) which is where it works (the 135th record
causes the buttons to quit working. It is not a data problem because I then
tested with a different set of data and it would also fail but at a
different spot.

Can you post a URL to the site so we can take a look at the HTML?

Can you confirm that the HTML is valid?
http://validator.w3.org
--
Oli

[Mara Guida]

Vic Spainhower wrote:

I changed the query so that it would only pick up records starting with the
135th record. With this set of records it is ok the button works. So I
believe this indicates that it is not a data problem.

I'm still not convinced.
Try this:

Instead of putting the value from the database in the select put a
count of options and try all the records (or just the subset from
record 1 to record 135)

// ...
$option_count = 0;
while ($row = mysql_fetch_row()) {
### echo '<option>', $row[2], '</option>';
echo '<option>', ++$option_count, '</option>';
}
// ...

[Vic Spainhower]

*** Solved ***

It appears the problem is there is some sort of limit when using method=GET
in the HTML FORM statement and this limit was being exceeded. I changed the
form statement to method=POST and it is now working correctly. I don't know
know what the limit is for using GET and I suppose it's possible that POST
varaibles also have a limit but obviously more then GET.

I want to thank everyone for taking the time to reply to my post as it
really did help getting to the bottom of this problem.

Vic

[Mara Guida]

Vic Spainhower wrote:

*** Solved ***
Good :)
It appears the problem is there is some sort of limit when using method=GET
in the HTML FORM statement and this limit was being exceeded. I changed the
form statement to method=POST and it is now working correctly.

<snip>

<quote src="rfc2616">
The HTTP protocol does not place any a priori limit on the length of
a URI. Servers MUST be able to handle the URI of any resource they
serve, and SHOULD be able to handle URIs of unbounded length if they
provide GET-based forms that could generate such URIs. A server
SHOULD return 414 (Request-URI Too Long) status if a URI is longer
than the server can handle (see section 10.4.15).

Note: Servers ought to be cautious about depending on URI lengths
above 255 bytes, because some older client or proxy
implementations might not properly support these lengths.
</quote>
Let me just add that your initial post led us all thinking about a
problem you didn't have.

The problems started when I added a dropdown menu to the grid
and when I did the form buttons would not work when there were
a few values in the drop-down.

The form buttons have been working all the time, with 134 records or
248!
The form would be submitted -- that's what the buttons are for.

[Vic Spainhower]

>The form buttons have been working all the time, with 134 records or 248!

The form would be submitted -- that's what the buttons are for.
Mara,

The problem that I originally stated was "is there a memory limit for HTML
pages?" The form buttons did stop working when I added a dropdown menu to
the table (which was part of the form). Why do you say they were not working
Mara? I press the submit button and nothing happens! That to me is not
working. I thought there may have been a memory limit of some sort because
if was definitely related to the size of the table being constructed. If the
server was supposed to return a 414 it did not. I appologise if I anyone was
misslead as to how I stated the problem. I only stated in the best way I
could and what I was seeing.

Vic

"Mara Guida" <ma*******@gmail.com> wrote in message
news:11*********************@f14g2000cwb.googlegro ups.com... Vic Spainhower wrote:

*** Solved ***

Good :)

It appears the problem is there is some sort of limit when using
method=GET
in the HTML FORM statement and this limit was being exceeded. I changed
the
form statement to method=POST and it is now working correctly.

<snip>

<quote src="rfc2616">
The HTTP protocol does not place any a priori limit on the length of
a URI. Servers MUST be able to handle the URI of any resource they
serve, and SHOULD be able to handle URIs of unbounded length if they
provide GET-based forms that could generate such URIs. A server
SHOULD return 414 (Request-URI Too Long) status if a URI is longer
than the server can handle (see section 10.4.15).

Note: Servers ought to be cautious about depending on URI lengths
above 255 bytes, because some older client or proxy
implementations might not properly support these lengths.
</quote>
Let me just add that your initial post led us all thinking about a
problem you didn't have.

The problems started when I added a dropdown menu to the grid
and when I did the form buttons would not work when there were
a few values in the drop-down.

The form buttons have been working all the time, with 134 records or
248!
The form would be submitted -- that's what the buttons are for.

[Mara Guida]

Vic Spainhower wrote:

The form buttons have been working all the time, with 134 records or 248!
The form would be submitted -- that's what the buttons are for.
Mara,

The problem that I originally stated was "is there a memory limit for HTML
pages?"

No, for pratical purposes, there isn't.
So your problem must be something else.
The form buttons did stop working when I added a dropdown menu to
the table (which was part of the form).
No, they didn't -- and that's my point!
If the buttons had stopped working, changing the method from POST to
GET wouldn't accomplish anything.
Why do you say they were not working
Mara?
See above.
I press the submit button and nothing happens!
Nothing?
The address in the address bar doesn't get crowded?
The server log doesn't show a new request at the time you pressed the
button?
Doesn't the browser get a new page (with the same content)?
That to me is not working.

The way I read your problem it seemed something like

This works
<form action="whatever">
<input type="submit">
</form>

When I add a select it wil not work
<form action="whatever">
<select>
<option>1</option>
<option>2</option>
<option>3</option>
</select>
<!-- This is just an example -->
<!-- I'm sure adding a select does not change the input type
-->
<input type="button" value="Submit Query">
</form>
<snip>