Project

General

Profile

Actions
Copy link

Bug #4164

closed

Associated Data - wf_exec_id behavior

Added by ben leinfelder about 15 years ago. Updated about 15 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Derik Barseghian
Category:
provenance
Target version:
2.0.0-alpha1
Start date:
06/15/2009
Due date:
% Done:

0%

Estimated time:
Bugzilla-Id:
4164

Description

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!

Files

associated_data_query_weirdness.txt (4.68 KB) associated_data_query_weirdness.txt Derik Barseghian, 06/19/2009 05:02 PM

Related issues

Blocks Kepler - Bug #4197: Waterflow TPC demo - tracking bugResolvedben leinfelder06/29/2009

Actions
Actions
Copy link

Also available in: Atom PDF