>>> "Craig A. Berry" <[EMAIL PROTECTED]> 11/07/03 01:18PM >>> <snip>
>Thanks for the explanation. I had a feeling I was oversimplifying >somewhat. I believe writes to files also had a similar limitation at >some point in the past but the CRTL took upon itself the task of >breaking up large writes. It would have to do the same thing for >sockets, and I agree it probably should. Regardless of if and when >that happens, I think it's reasonable to expect a Perl program that >is inserting a large number of rows in a database to make some >reasonable assumption about the maximum number of rows it can insert >in one go. But I was only inserting one row. No, really! The "row" is actually an entire HTML page that I wanted to cache. The MySQL server is locked down pretty tightly by someone bigger than me; all I had was a MySQL hammer, so the page appeared to be a row (nail). The sucking of an entire file into memory was to reproduce the "problem". The actual application doesn't do that, nossirree bob; it dots up the >64KB string over the course of several query loops :-) I have seen the error of my ways and broken the page up into 5 pieces. I still have an open case with HP and will pass along additional information as/if it becomes available. Regards, Carl B., x2796
