[kepler-dev] [Bug 5338] New: In Database Query actor, the output behavior will be different if there is no result set found when you check or uncheck outputEachRowSeparately

[bugzilla-daemon at ecoinformatics.org]

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

           Summary: In Database Query actor, the output behavior will be
                    different if there is no result set found when you
                    check or uncheck outputEachRowSeparately
           Product: Kepler
           Version: 1.x dev
          Platform: Other
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: actors
        AssignedTo: david.v.welker at gmail.com
        ReportedBy: tao at nceas.ucsb.edu
         QAContact: kepler-dev at kepler-project.org
   Estimated Hours: 0.0


If there is result set found and the output type is "array":
no token will be sent if you select "outputEachRowSeparately" in configuration
panel;
no token will be send but a message "no match result for query ..." will be
shown if you don't select "outputEachRowSeparately".


If there is result set found and the output type is "no metadata".
no token will be sent if you select "outputEachRowSeparately" in configuration
panel;
A token ( I guess "/n") will be sent out if you don't select
"outputEachRowSeparately".

-- 
Configure bugmail: http://bugzilla.ecoinformatics.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.