This content has been marked as final.
Show 1 reply
-
1. Re: Database Unique Constraint Violation on JBM_MSG MESSAGE_
clebert.suconic Dec 12, 2008 5:17 PM (in response to jkemp83)It seems to me that you created some failing condition at the DB.
In my opinion you shouldn't be dealing directly with the DB in any way. you should probably be using the API to consume data you don't want.
Regarding the maxValue issue you raised, I don't think that's possible. 203911168 is C277000 which would still be away from MAX_INT (0x7fffffff), and besides that value is a long.