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

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp>
Cc: Cedar Cox <cedarc(at)visionforisrael(dot)com>, pgsql-odbc(at)postgresql(dot)org
Subject: Re: Rep:Re: Error Writing/Reading Encrypted Values
Date: 2002-01-18 03:06:56
Message-ID: 200201180306.g0I36vW03539@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
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.

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

In response to

Responses

Browse pgsql-odbc by date

  From Date Subject
Next Message Cedar Cox 2002-01-18 10:27:16 Re: Rep:Re: Error Writing/Reading Encrypted Values
Previous Message Hiroshi Inoue 2002-01-18 02:19:06 Re: Rep:Re: Error Writing/Reading Encrypted Values