Andrew Sullivan wrote:
On Wed, Dec 07, 2005 at 04:37:59PM +0000, Andreas Pflug wrote:
I don't quite understand the issue. AFAIR all Japanese encodings will
happily translate from and to Unicode. pgAdmin never received complaints
about this, I'm sure at least Hiroshi Saito would have rised his voice.
They do. The trouble is that in some applications, there are issues
having to go with glyph representation and the script choice. Most
people don't actually care about this sort of thing, but there are
politicians who are always angry about having to use the wrong glyph
encoding. If you want to make your eyes hurt, follow one of the
occasional flamefests that breaks out in the IETF over this issue.
But in any case, this only touches automatic determination of client
encodings in slon. If slon is used to copy between databases that aren't
configured correctly, any automatism must fail, and only a manual
selection of client encodings would help. sl_node.no_encoding would
solve this.
Well, that still leaves open the question of whether that's legit.
I'd prefer it to be an override option, with the normal case be
"whatever's on the origin".
Whatever default is, manual override possibility is what I suggested. Do
you agree it should be configurable on the node level, not as slon cmd
line option?
Regards,
Andreas
_______________________________________________
Slony1-general mailing list
[email protected]
http://gborg.postgresql.org/mailman/listinfo/slony1-general
