-
Notifications
You must be signed in to change notification settings - Fork 5
Select response with empty datetime causes null pointer exception #1
Comments
Thanks! Looks like a problem with null value handling in Trireme that should be easy to fix -- let me make sure we have a comprehensive-enough test suite and we'll have something to test. |
I forgot to add that other empty fields seem to be handled without error.
|
I fixed the null handling in Trireme and I pushed a new "beta1" release to NPM. Can you please re-test: sudo npm update -g trireme The null handling should work now and you should get no NPEs. And if you're still having the "order by" issue, do you have any SQL that we can test? |
Looks good! Row: {"taskid":533,"taskname":"Ihor's Process_Expense Comparison_8","starttime":"2014-09-24T21:40:59.290Z","endtime":null} |
Glad to hear it! This was fixed in Trireme 0.8.3 so I'm closing it now. |
Response from SOAP UI test using JDBC driver, note the empty ENDTIME element:
Error I'm seeing:
The text was updated successfully, but these errors were encountered: