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

Re: Rep:Re: Error Writing/Reading Encrypted Values

From: Cedar Cox <cedarc(at)visionforisrael(dot)com>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp>, pgsql-odbc(at)postgresql(dot)org
Subject: Re: Rep:Re: Error Writing/Reading Encrypted Values
Date: 2002-01-18 10:27:16
Message-ID: Pine.LNX.4.21.0201181219390.11971-100000@nanu.visionforisrael.com (view raw or flat)
Thread:
Lists: pgsql-odbc
> > > > Ok.  I understand the dilemma.  In that case, perhaps it would make sense
> > > > for it to be a compile time option, with defaults as I mentioned.  It
> > > > seems most likely to be platform dependent, and probably set only once
> > > > anyway.  This way the windows driver at least wouldn't change at all
> > > > ...back to the list.  Comments anyone?
> > > 
> > > Compile-time options are even less attractive -- perhaps some
> > > auto-sensing code that looked at the first line and determined the
> > > proper behavior.
> > 
> > Hmm I don't understand what auto-sensing means.
> > At any rate I would change the behavior in the next
> > version.
> 
> For auto-sensing, I was thinking of looking at the end of the first line
> and seeing if it is \n or \r\n and using that to handle the rest of the
> lines.

The point of this is to handle arbitrary binary data (and give people an
option of CRLF translation) right?  What if the "wrong" data appears?  
How does one auto-sense binary data?  (Perhaps I'm missing something..)

-Cedar


In response to

Responses

pgsql-odbc by date

Next:From: Samuele BrignoliDate: 2002-01-18 11:45:19
Subject: odbc error
Previous:From: Bruce MomjianDate: 2002-01-18 03:06:56
Subject: Re: Rep:Re: Error Writing/Reading Encrypted Values

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