DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=37254>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=37254 Summary: RDBMS store and Branching. Product: Slide Version: 2.1 Platform: All OS/Version: All Status: NEW Severity: major Priority: P1 Component: Stores AssignedTo: slide-dev@jakarta.apache.org ReportedBy: [EMAIL PROTECTED] When branching, slide add one or to number (depending the version) to the version number. 1.3 become 1.3.1 or 1.3.1.0 In the RDBMS stores, the method "public NodeRevisionDescriptors retrieveRevisionDescriptors(Connection connection, Uri uri)" call the method "String convertRevisionNumberToComparable(String revisionNumber)" to generate the orderby part of the sql query. This method generate an sql expression which cut the revision number in two part (cutted at the first '.' found) and transform them into number. "1" is a valid integer and "3.1" is a valid decimal value. but when "1.3.1.0" is split into "1" and "3.1.0", RDBMS can not convert the string "3.1.0" to a valid number. en then depending of the database this crach the query, or just evaluated as NULL (then the row is misplaced) or the row is skipped. In all case the revision 1.3.1.0 is never found. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
