Steve Holden <[EMAIL PROTECTED]> writes: > I'm not suggesting this isn't an error. Simply that it's an error that > is also implemented in (among others) Oracle and MS Access, IIRC, and > that the vendors clearly aren't that concerned about it.
We have a saying here in Brazil that translates to something like "two wrongs doesn't make one right". I don't think that just because other vendors don't get it right MySQL shouldn't get it too... MS Access is nothing I would care for commercial systems (even though there's a lot of semi-standalone systems that use it here in Brazil, unfortunately). Oracle has so many configuration options that I wouldn't be surprised if there was some w.x.y.z.something.enconding that activated the correct behavior and that came with an ISO-8859-1 default so that it preserver backwards compatibility with Oracle 2... :-P :-) > Very nice demonstration of the problem, by the way. Oh well... I tried giving you the minimum work to reproduce the behavior on MySQL. It is important that somebody shows that I am wrong or that there are other parameters needed on the connection string, database setup, etc. so that other people can fix their code. -- Jorge Godoy <[EMAIL PROTECTED]> --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/turbogears?hl=en -~----------~----~----~----~------~----~------~--~---
