Dear Pawel,
the test that was extended with UTF-8 characters after resolving your bug #2014118 appear to work fine with the code base for the upcoming May2009 release; cf., http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/Int.32.... http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/Int.32....
I also do not recall seeing this test fail with the previous Feb2009 release.
Could you please provide us with detailed instructions including a small example how to reproduce the problems that you experience?
Thanks!
Stefan
On Wed, May 27, 2009 at 04:53:10PM +0200, Pawel Lewicki wrote:
Hi, Last year I reported problems with inserting non-ascii data using ODBC interface. I submitted a bug #2014118 and it was resolved. At least I hope so. Unfortunately I had no time to play with MonetDB and had no opportunity to use it for real data. It has recently changed so I'm back with testing. I have to report that the problem is not resolved, at least it's back in Windows 32-bit Feb2009-SP2 release. I have a problem with using queries with properly encoded utf-8 data. The same data inserted using Python bindings is perfect. I have noticed that broken "LIKE" queries give proper result on broken inserted data. It means that the same characters are being recognized. ODBC driver version is 1.28.04.01 Regards,
Pawel Lewicki
Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT is a gathering of tech-side developers & brand creativity professionals. Meet the minds behind Google Creative Lab, Visual Complexity, Processing, & iPhoneDevCamp as they present alongside digital heavyweights like Barbarian Group, R/GA, & Big Spaceship. http://p.sf.net/sfu/creativitycat-com _______________________________________________ MonetDB-users mailing list MonetDB-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/monetdb-users