RE: Would a maximum POST size be affected by named pipes-TCP/IP c hange?

---------------------------------------------------------------------------- ----------------- Disclaimer: The information contained in this email is intended only for the use of the person(s) to whom it is addressed and may be confidential or contain legally privileged information. If you are not the intended recipient you are hereby notified that any perusal, use, distribution, copying or disclosure is strictly prohibited. If you have received this email in error please immediately advise us by return email at postmaster@normandy.com.au and delete the email document without making a copy. ---------------------------------------------------------------------------- ----------------- I doubt it has anything to do with POST as i happily sumbit rather large posts all the time (from memory file uploads use POST which can be any size) What i would suggest it is something to do with TCP/IP connections or the field. I use Oracle and found that large SQL statements were causing me problems (we are talking about HUGE sql with 50 or so unions... dont ask.. there was no choice) so i ended up breaking it down into multiple selects then joined the data at the webserver. This is fine for SELECT's, but im not sure it is OK for UPDATES (can you just break it into 100K chunks and append them?). But with Oracle and TCP/IP it appears to be a problem. What i would suggest you do is think about how you are storing your info. I've personally never been happy with storing pictures / whole articles in a DB if they were reletively static. Why not just store a reference to a file name in the DB and store the article in a file? This i realise may inhibit searching of your articles but the fasted method here seems to be to build a index with words that you may wish to search on then search that. Build your index every night or every 4 hours or so. This is much more scalable (and faster) than searching through 100 artilces everytime someone wishes to find all articals on CSS or whatever. Imagine you have 100 searches being performed on your site a day, you could update your index's every 30 minutes and still be ahead in use of resources. And of course there are lots of tools that can already do this for you like htdig. mn -----Original Message----- From: Ian Evans [mailto:ianevans@friedspamdigitalhit.com] Sent: Tuesday, August 15, 2000 11:20 PM To: php-windows@lists.php.net Subject: Would a maximum POST size be affected by named pipes-TCP/IP change? The techs at my site's host and I are still struggling to solve a problem with a database insert form that stopped working. (WinNT, IIS4, PHP3) After many, many test posts I discovered that it was a matter of the size of the SQL string being submitted. One character longer and we'd get an error, one shorter and the article would insert into the database. If it was too long we'd get no error messages, if it was just a few characters over the fail point we'd get an "Unclosed quotation mark before the character string" error message even though the SQL string was formatted correctly. Obviously something was truncating the POST string and therefore omitting the closing punctutation. The odd thing is that we have successfully submitted much larger articles than the one we're having problems with now in the past. The only thing I can think of is that this started happening when they changed our ODBC connection from named pipes to TCP/IP. Can anyone think of any quirk, bug, or voodoo that would cause what appears to be a limit on the size of the HTTP POST string? Thanks. My head's sore from all the banging it's doing on the desk. -- Ian Evans