On Sat, Feb 18, 2006 at 08:16:07PM -0800, Bill Moseley wrote: > Is the Holy Grail encoding and lc_collate settings per column? Well yes. I've been trying to create a system where you can handle multiple collations in the same database. I posted the details to -hackers and got part of the way, but it's a lot of work. As for encodings, to be honest, I'm not sure whether it's a great idea to support multiple encodings simultaneously. Things become a lot easier if you know everything is the same encoding. If you set the client_encoding automatically on startup it has pretty much the same effect as having the server always use that encoding. It's just a bit of time wasted in conversion, but the client doesn't need to care. By way of example, see ICU which is an internationalisation library we're considering to get consistant locale support over all platforms. It supports one encoding, namely UTF-16. It has various functions to convert other encodings to or from that, but internally it's all UTF-16. So if we do use that, then all encodings (except native UTF-16) will need to conversion all the time, so you don't buy anything by having the server in some random encoding. The problem ofcourse being that the SQL standard requires some encoding support. No-one has really come up with a proposal for that yet. IMHO, that's a parser issue more than anything else. Have a nice day, -- Martijn van Oosterhout <kleptog@xxxxxxxxx> http://svana.org/kleptog/ > Patent. n. Genius is 5% inspiration and 95% perspiration. A patent is a > tool for doing 5% of the work and then sitting around waiting for someone > else to do the other 95% so you can sue them.
Attachment:
signature.asc
Description: Digital signature
