I have recently had some requests for assistance with localization for
DBD::CSV. The situation is this: if a user adds "use locale" in
SQL::Statement, the DBD will be able to use a localized sort order and
localized comparison operations. If a user adds it also in SQL::Parser,
they will also be able to use a localalized definition of alphanumeric
to define valid SQL identifiers (e.g. accented characters recognized by
the locale setting become valid in table or column names without
delimiting the identifiers). As I understand it, these are both within
the spirit of ANSI SQL -- that the sort order and definition of
alphanumeric is legitimately variable depending on localization.
I am really very ignorant about localization. Is what I am proposing a
sane thing to encourage users to do? Is there any other way I can make
it user-definable without having them muck with the actual module text?
Are there any other gotchas I need to know about?
--
Jeff
- Re: Localalization Jeff Zucker
- Re: Localalization Tim Bunce
- Re: Localalization Jeff Zucker