> Hi! Hiroshi,
> Thank you again for the big help!
> [ begin of quote ]
> > I also found in Windoz that when my encryption
> > routine aborts, the retrieved encrypted string is
> > actually corrupted - its string length is 1 byte
> > longer than it is supposed to be.
> There could be the following case.
> Windows client *nix server
> '\n' ---> '\n'
> (not preceded by 'r')
> \r\n <--- '\n'
> [ end of quote ]
> I will check this out.
> My C routine does not add the *unwanted* '\r'. I
> won't think delphi does that either. Does pgsqlODBC
> do this unwanted conversion?
Yes. Do people want a new option ?
In response to
pgsql-odbc by date
|Next:||From: Wolfgang Fürtbauer||Date: 2002-01-15 05:39:51|
|Subject: Problems with Visual Basic |
|Previous:||From: Keith Gray||Date: 2002-01-15 01:31:20|
|Subject: Re: Error Writing/Reading Encrypted Values|