Re: Rep:Re: Error Writing/Reading Encrypted Values - Mailing list pgsql-odbc

From Bruce Momjian
Subject Re: Rep:Re: Error Writing/Reading Encrypted Values
Date
Msg-id 200201180306.g0I36vW03539@candle.pha.pa.us
Whole thread Raw
In response to Re: Rep:Re: Error Writing/Reading Encrypted Values  (Hiroshi Inoue <Inoue@tpf.co.jp>)
Responses Re: Rep:Re: Error Writing/Reading Encrypted Values
List 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.

--
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

pgsql-odbc by date:

Previous
From: Hiroshi Inoue
Date:
Subject: Re: Rep:Re: Error Writing/Reading Encrypted Values
Next
From: Cedar Cox
Date:
Subject: Re: Rep:Re: Error Writing/Reading Encrypted Values