Issue 353 in glassdb: UTF8 tests failing in 3.1.0.1

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Issue 353 in glassdb: UTF8 tests failing in 3.1.0.1

glassdb
Status: Accepted
Owner: [hidden email]
Labels: Type-Defect Priority-Medium GLASS-Server Version-1.0-beta.8.7.2  
Milestone-1.0-beta.8.7.3

New issue 353 by [hidden email]: UTF8 tests failing in 3.1.0.1
http://code.google.com/p/glassdb/issues/detail?id=353

turns out that the behavior for the class UTF8 changed in such a way that  
breaks the test, but does not affect the behvior in general.

Before 3.1.0.1 a UTF8 instance and a String instance with the same bytes  
compared equal. In 3.1.0.1 that is no longer the case. Seaside requires  
that UTF8 encoded bytes be kept in Strings, but in Seaside UTF8 encoded  
strings are not compared to UTF8 instances, so the tests themselves can be  
safely changed  to covert both instances to ByteArrays...

Reply | Threaded
Open this post in threaded view
|

Re: Issue 353 in glassdb: UTF8 tests failing in 3.1.0.1

glassdb
Updates:
        Status: Fixed
        Labels: Fixed-1.0-beta.8.7.3

Comment #1 on issue 353 by [hidden email]: UTF8 tests failing in  
3.1.0.1
http://code.google.com/p/glassdb/issues/detail?id=353

fixed in GsMisc 0.241.1 (dkh.103) (Utf8Encoding.310-dkh.30)