Project

General

Profile

Bug #4227

Provenance - use Integer return type in Queryable interface

Added by ben leinfelder about 10 years ago. Updated almost 10 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
provenance
Target version:
Start date:
07/07/2009
Due date:
% Done:

0%

Estimated time:
Bugzilla-Id:
4227

Description

Found out that resultset.getInt(x) will return 0 when in fact there was a null (no result). Changed to not start IDs at 0 so as to avoid unexpected results, but a 0 can still be confusing and ambiguous.
By using an Integer return type, a NULL could be passed to the caller and handled appropriately.


Related issues

Blocks Kepler - Bug #4225: Provenance - start auto-incremented IDs at 1 not 0Resolved07/06/2009

History

#1 Updated by Daniel Crawl almost 10 years ago

These methods now return null if the query has 0 results.

#2 Updated by Redmine Admin over 6 years ago

Original Bugzilla ID was 4227

Also available in: Atom PDF