Re: [ADMIN] maximum attribute record.
Has this been fixed in 6.5 beta?
On Tue, Feb 02, 1999 at 07:33:48PM +0800, Vikrant Rathore wrote:
If your query is bigger than 8192 bytes then libpq simply truncates it
without giving any warningI've read that in the docs, too (while back, didn't try it out). I have
to say, though, that I think this behaviouur is somewhat less than optimal.
Personally, I strongly prefer it if error conditions are raised by software
when it isn't able to carry out the requested function.
--
Bruce Momjian | http://www.op.net/~candle
maillist@candle.pha.pa.us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026Import Notes
Reply to msg id not found: 19990202151834.B30412@mars.mpiz-koeln.mpg.de
Bruce Momjian <maillist@candle.pha.pa.us> writes:
Has this been fixed in 6.5 beta?
On Tue, Feb 02, 1999 at 07:33:48PM +0800, Vikrant Rathore wrote:
If your query is bigger than 8192 bytes then libpq simply truncates it
without giving any warningI've read that in the docs, too (while back, didn't try it out).
That hasn't been true since at least 6.3.2:
/* check to see if the query string is too long */
if (strlen(query) > MAX_MESSAGE_LEN - 2)
{
sprintf(conn->errorMessage, "PQsendQuery() -- query is too long. "
"Maximum length is %d\n", MAX_MESSAGE_LEN - 2);
return 0;
}
Possibly the documentation needs updated, but all I can find is:
: Caveats
:
: The query buffer is 8192 bytes long, and queries over that length will
: be rejected.
Is there another place that says the wrong thing?
regards, tom lane
Import Notes
Reply to msg id not found: YourmessageofSun9May1999075357-0400199905091153.HAA16470@candle.pha.pa.us | Resolved by subject fallback