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

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

From: Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
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 02:19:06
Message-ID: 3C47861A.F4B6D9F@tpf.co.jp (view raw or flat)
Thread:
Lists: pgsql-odbc
Bruce Momjian wrote:
> 
> >
> > 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.

regards,
Hiroshi Inoue

In response to

Responses

pgsql-odbc by date

Next:From: Bruce MomjianDate: 2002-01-18 03:06:56
Subject: Re: Rep:Re: Error Writing/Reading Encrypted Values
Previous:From: Bruce MomjianDate: 2002-01-16 14:54:28
Subject: Re: Rep:Re: Error Writing/Reading Encrypted Values

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