Skip site navigation (1) Skip section navigation (2)

Re: Error Writing/Reading Encrypted Values

From: <cnliou(at)eurosport(dot)com>
To: <pgsql-odbc(at)postgresql(dot)org>
Subject: Re: Error Writing/Reading Encrypted Values
Date: 2002-01-15 06:05:56
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-odbc
Greetings! Hiroshi,

[ 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
> do this unwanted conversion?

Yes. Do people want a new option ?
[ end of quote ]

Please first pardon my ignorance of too many things
including ODBC.

I presume all people want is a "raw" data extracted
from database without any translation except for
multi-byte characters.  As in my case shows: problem
arises when char/varchar/text fields are used to
store "strange" (encrypted) characters and ODBC
"automatically" adds '\r' to these values before
returnning them to Windoz applications.

Is it reasonable and possible in technical point of
view to at least add a checkbox in ODBC indicating
enable/disable '\r' translation? Or is it true that
char/varchar/text columns were not designed to store
encrypted characters, which may contain non ascii
characters and low values, in the first place? If so,
where am I supposed to save the encrypted characters?



You too can have your own email address from Eurosport.


pgsql-odbc by date

Next:From: Hiroshi InoueDate: 2002-01-15 06:52:17
Subject: Re: Error Writing/Reading Encrypted Values
Previous:From: Wolfgang F├╝rtbauerDate: 2002-01-15 05:39:51
Subject: Problems with Visual Basic

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group