[kepler-dev] [Bug 4164] New: - Associated Data - wf_exec_id behavior

[bugzilla-daemon at ecoinformatics.org]

http://bugzilla.ecoinformatics.org/show_bug.cgi?id=4164

           Summary: Associated Data - wf_exec_id behavior
           Product: Kepler
           Version: 1.x dev
          Platform: Other
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: provenance
        AssignedTo: crawl at sdsc.edu
        ReportedBy: leinfelder at nceas.ucsb.edu
         QAContact: kepler-dev at kepler-project.org
                CC: barseghian at nceas.ucsb.edu


Derik and I are running into a rather odd problem when querying the
ASSOCIATED_DATA table for records. It appears that the WF_EXEC_ID column is
behaving as a varchar column even though everything says it is an integer.
After running a workflow (with WRP suite) I see 3 rows in the table for
execution id 0, but only if I look for them with the like '%0%' syntax:

SELECT data.md5, ad.* FROM ASSOCIATED_DATA ad, DATA data WHERE data.md5 =
ad.data_id and ad.wf_exec_id like '%0%'

using a numeric operator (=) does not return records (even though the table
"looks" like it should yield them:

SELECT data.md5, ad.* FROM ASSOCIATED_DATA ad, DATA data WHERE data.md5 =
ad.data_id and ad.wf_exec_id = 0

My DB browser shows the column as an INTEGER. And the prepared statements all
use setInt() methods when interacting with the table...at my wits' end!