> > > > 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
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..)
In response to
pgsql-odbc by date
|Next:||From: Samuele Brignoli||Date: 2002-01-18 11:45:19|
|Subject: odbc error|
|Previous:||From: Bruce Momjian||Date: 2002-01-18 03:06:56|
|Subject: Re: Rep:Re: Error Writing/Reading Encrypted Values|