AFAICS the server doesn't know (and in my opinion shouldn't care) what
platform a non-local client is running on. This appears to be purely a
client-side issue. Furthermore, on Windows, if you are writing the data
you get from Postgres to a file which you opened in non-binary mode,
Windows will do the translation for you (something we actually have to be
careful of in doing the Windows port).
cheers
andrew
ivan said:
>
>
>
> its must be in run time, server should has text with linux new line,
> and if clinet is windows, postgres would convert \n to \n\r
> but when clinet is also linux postgresa can do nothing about it
>
> :)
> any idea ?
>
> On Sat, 27 Dec 2003, [iso-8859-1] Jürgen Cappel wrote:
>
>> Hi Ivan,
>>
>> maybe your're looking for something like this:
>>
>> http://rcamera.org/cgi-bin/man2html.cgi?1+unix2dos
>>
>> HTH,
>>
>> Jürgen Cappel
>>
>>
>> ivan <[EMAIL PROTECTED]> schrieb am 27.12.2003, 14:19:10:
>> >
>> >
>> > is there same easy way to turn on translation bettwen client and
>> > server from linux new-line style (0x0A) to windows style (0x0A0D?)
>> > (something like conversions) ?
>> >
---(end of broadcast)---
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match
