[ 
https://issues.apache.org/jira/browse/SYNAPSE-533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rajika Kumarasiri updated SYNAPSE-533:
--------------------------------------

    Attachment: SYNAPSE-533.patch

Here is a patch which fix the problem.
Now the result element has an optional rowIndex attribute which you can specify 
the row of the result set  to get the required result when there are more than 
one entry. 
ex:
<result name="company_id" column="id" />
<result name="company_price_0" column="price" rowIndex="2"/>
<result name="company_price_1" column="price" rowIndex="4"/>

Rajika

> DBLookup extracs only first element from database
> -------------------------------------------------
>
>                 Key: SYNAPSE-533
>                 URL: https://issues.apache.org/jira/browse/SYNAPSE-533
>             Project: Synapse
>          Issue Type: Bug
>          Components: Extension Mediators, Script mediator
>    Affects Versions: 1.2
>            Reporter: minal sontakke
>             Fix For: 1.2
>
>         Attachments: SYNAPSE-533.patch
>
>   Original Estimate: 96h
>  Remaining Estimate: 96h
>
> I just realized that the DBLookup mediator extracts only the first row... :( 
> when i try to use statement like select * from mytable;  and if my table 
> called as mytable contains 3 values like test1, test2 and test 3, when i try 
> to use the same only first element gets displayed ie like test1 and i dont 
> get output as test1,test2, test3.  DBLookup needs to improve this to extract 
> multiple rows if there are multiple rows, in which case the result set will 
> be a list of results which might be a special list that needs to be implement 
> because it can get a XML representation of this list easily.
> Refer discussion at link : http://wso2.org/forum/thread/5181

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to