On Wed, 12 Feb 2003, David Wheeler wrote: > On Wednesday, February 12, 2003, at 08:45 PM, Rudy Lippan wrote: > > > Just did a quick look a the patch and the Pgsql docs. I need to do > > some > > more research, but what do you think about a set_client_encoding() > > function tells the db that you want UTF8. And DBD::Pg can just figure > > out > > the current client encoding by asking libpq. Depending on the > > overhead of > > caling PQclientEncoding(), it might be possible to call it after each > > execute and set the flag there. > > I think that Tim's idea was for a new DBI attribute, CharSet: > > http:[EMAIL PROTECTED]/msg15486.html >
I am game with that. But I'd still like to do some research on the issue, and I would also like make sure that DBD::Pg goes they way DBI goes. So I don't want to rush and end up with a bad interface or one that differs from the other DBDs, if possible. > > The question then arises is whether to set the flag on the sth or on > > the > > db -- Think about interleaved cursor fetches and things like that. > > On the dbh, but overridable [sp?] on the sth. > Or both. I was saying that I don't know enough about PostgreSQL's behaviour to say, right now. > David > >
