Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > Can someone explain why this fixes the problem.
>
> Think about a machine where char is signed by default. Extracting \254
> into an int will produce -2, which will not equal \254 returned by getc.
Oh, I thought that the int return
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Can someone explain why this fixes the problem.
Think about a machine where char is signed by default. Extracting \254
into an int will produce -2, which will not equal \254 returned by getc.
regards, tom lane
Can someone explain why this fixes the problem. I thought it was safe
to assign a char to an int and do a compare. The compare I see is:
if (c == delimc)
break;
---
Darcy Buskermo
Darcy Buskermolen <[EMAIL PROTECTED]> writes:
> Postgres was not compiled with Multibyte, if I replace the if (delimc == c)
> with if (strstr(delim,c)) it works as expected. This changes was
> implemented for performance reasons according to the CVS log.
Yeah, my error :-(. See Tatsuo's reply fo
This patch solves the problem.
At 09:16 PM 2/26/02 +0900, Tatsuo Ishii wrote:
>> When useing COPY FROM 'file' DELIMITER '\254' copyfrom reads past the
>> delimiter and ends up with parse errors when trying to do the insert
>>
>>
>> What the ?? why dind' tthat go through with the body of the tex
Postgres was not compiled with Multibyte, if I replace the if (delimc == c)
with if (strstr(delim,c)) it works as expected. This changes was
implemented for performance reasons according to the CVS log.
At 11:57 PM 2/25/02 -0500, Tom Lane wrote:
>Darcy Buskermolen <[EMAIL PROTECTED]> writes:
>>
> When useing COPY FROM 'file' DELIMITER '\254' copyfrom reads past the
> delimiter and ends up with parse errors when trying to do the insert
>
>
> What the ?? why dind' tthat go through with the body of the text.. *sigh*
> I'll resend in the AM..
Good catch. It's definitely a bug in copy com
Darcy Buskermolen <[EMAIL PROTECTED]> writes:
> When useing COPY FROM 'file' DELIMITER '\254' copyfrom reads past the
> delimiter and ends up with parse errors when trying to do the insert
Are you perhaps operating in a multibyte encoding in which \254 is
just the first byte of a multibyte charac
ACK! must rember which MTA I'm useing...
When useing COPY FROM 'file' DELIMITER '\254' copyfrom reads past the
delimiter and ends up with parse errors when trying to do the insert
What the ?? why dind' tthat go through with the body of the text.. *sigh*
I'll resend in the AM..
---
ACK! must rember which MTA I'm useing...
When useing COPY FROM 'file' DELIMITER '\254' copyfrom reads past the
delimiter and ends up with parse errors when trying to do the insert
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
When useing COPY FROM 'file'
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
11 matches
Mail list logo
