-----BEGIN PGP SIGNED MESSAGE----- Hash: RIPEMD160
> Okay, put that way I understand it. I think that should be the introductory > paragraph, followed by a bulleted list explaining the situations in which > it would be off. +1. I'm going to try and find some time to make a dev version with most of what we are talking about here soonish. > I think that setting pg_encoding should always turn pg_unicode *on*. Hm...no, I think it should always be off. If someone really wants a different encoding, they probably are used to it coming back "raw". David C, I think we talked about this? >> Yeah, that's true. On the other hand, even the encoding setting is meant >> as sort of an expert knob. > Maybe. I think a lot of existing installations may find they need to > turn it off, unless they had been using pg_enable_utf8 before. Yep: no way to know until we release. David and I were thinking that the other direction (data going to database) is probably more likely to break things. > I think that setting pg_encoding should turn on pg_unicode, unless it's > set to :raw or something. Then someone could always explicitly set both > to make it do what they mean. Yep, more knobs, more knobs! ;) >> (some more of the same arguments trimmed from your reply) > Yeah, sorry. :-) No, I meant trimmed more of the stuff you said that bolstered my arguments, so no need to include it. Unless we want to really pile it on for David C. > Oh I agree, I just think it's worth putting off until this other stuff > gets sorted out. Nah, the more stuff we can fix out of the gate the better. > The truth is, unless we pay attention to what pg_enable_utf8 was set > to in such scripts -- and if it was set -- then suddenly having stuff > be encoded and decoded when it wasn't before may surprise some folks. > It *shouldn't*, but it will be different than what it was doing before. Yep. That's why this is a major release - we should not, and cannot, make everyone happy. Some people's scripts will break. Most (all?) will be able to twist some new knobs and get things working again. > Have you asked Tim Bunce about any of this stuff? I know he has > thought about adding encoding knobs to the DBI core, but I don't > know how far a long he got in thinking about a design. Good idea: I have not. Will try to do so. Or anyone else that wants to raise this on dbi-dev.... - -- Greg Sabino Mullane g...@turnstep.com End Point Corporation http://www.endpoint.com/ PGP Key: 0x14964AC8 201107211900 http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8 -----BEGIN PGP SIGNATURE----- iEYEAREDAAYFAk4or50ACgkQvJuQZxSWSsi7qQCg/DDAi2a20fUQccvXQwCQZiFv hicAn3Me90gbI0OqQ47ZJedL2T3xr5Wl =MM86 -----END PGP SIGNATURE-----
