openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeremy Bauer (JIRA)" <>
Subject [jira] Commented: (OPENJPA-1726) Clean up OpenJPA test case failures for PostgreSQL
Date Tue, 20 Jul 2010 14:47:49 GMT


Jeremy Bauer commented on OPENJPA-1726:

I ran into some issues with uuid-string and uuid-type4-string a while back.  This problem
isn't specific to PostgreSQL, but looks to be even more prevalent on that platform since it
stores data in UTF-8.  UTF-8 is particularly picky about character values.  To be honest,
I wouldn't ever recommend the use of uuid-string or uuid-type4-string since they generate
integral byte values and plug them in as character data without taking into account the character
encoding of either the client or database column.  Depending on the conversion, the id may
get converted to some other value or fail to convert (like we are witnessing on PostgreSQL).
 A better choice would have been to convert the values to ASCII base-10 numeric characters.
 This is not something we can change now though, since there may be existing applications
happily running with the current generation strategy.  The use of uuid-hex or uuid-type4-hex
is a much better choice since the key value includes only invariant ch!

Since this could fail intermittently on any platform a better choice might be to either discontinue
testing uuid-string or uuid-type4-string (while continuing to test uuid-hex and uuid-type4-hex)
or test the -string variants separately, excluding PostgreSQL.  I'm OK with either, or simply
excluding the test from running on PostgreSQL as you suggested.

> Clean up OpenJPA test case failures for PostgreSQL
> --------------------------------------------------
>                 Key: OPENJPA-1726
>                 URL:
>             Project: OpenJPA
>          Issue Type: Bug
>    Affects Versions: 2.1.0
>            Reporter: Fay Wang
>            Assignee: Fay Wang
>            Priority: Minor
>         Attachments: OPENJPA-1726-2.patch, OPENJPA-1726.patch

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message