| From: | Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp> |
|---|---|
| To: | cnliou(at)eurosport(dot)com |
| Cc: | pgsql-odbc(at)postgresql(dot)org |
| Subject: | Re: Rep:Re: Error Writing/Reading Encrypted Values |
| Date: | 2002-01-15 04:34:51 |
| Message-ID: | 3C43B16B.8EF64806@tpf.co.jp |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-odbc |
cnliou(at)eurosport(dot)com wrote:
>
> 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 ?
regards,
Hiroshi Inoue
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Wolfgang Fürtbauer | 2002-01-15 05:39:51 | Problems with Visual Basic |
| Previous Message | Keith Gray | 2002-01-15 01:31:20 | Re: Error Writing/Reading Encrypted Values |