StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
19569452
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
2
CommunityOwnedDate
CreationDate
2013-10-24T14:57:57.597
FavoriteCount
0
LastActivityDate
2013-10-24T21:29:45.850
LastEditDate
2013-10-24T21:29:45.850
LastEditorUserId
1137475
OwnerUserId
1137475
ParentId
19567035
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
It looks like you are using the CE JDBC transport. If this is correct then that is your problem. The CE version can not handle resultsets in calls to stored procedures. See the Feature table in the JDBC Transport documentation [1]. The reason it works in MuleStudio is that for some reason it seems that studio uses the EE JDBC transport even when the CE runtime is selected. I have reported this as a issue [2]. You can also see in the JDBC transport code[3] see that for a SQL statement that begins with CALL will result in a update on the QueryRunner. You should be able to override this by defining your own Sqlstatementstrategyfactory[4]. [1] <a href="http://www.mulesoft.org/documentation/display/current/JDBC+Transport+Reference" rel="nofollow">http://www.mulesoft.org/documentation/display/current/JDBC+Transport+Reference</a> [2] <a href="https://www.mulesoft.org/jira/browse/STUDIO-3817" rel="nofollow">https://www.mulesoft.org/jira/browse/STUDIO-3817</a> [3] <a href="https://github.com/mulesoft/mule/blob/mule-3.x/transports/jdbc/src/main/java/org/mule/transport/jdbc/sqlstrategy/DefaultSqlStatementStrategyFactory.java" rel="nofollow">https://github.com/mulesoft/mule/blob/mule-3.x/transports/jdbc/src/main/java/org/mule/transport/jdbc/sqlstrategy/DefaultSqlStatementStrategyFactory.java</a> [4] <a href="http://www.mulesoft.org/documentation/display/current/JDBC+Transport+Configuration+Reference" rel="nofollow">http://www.mulesoft.org/documentation/display/current/JDBC+Transport+Configuration+Reference</a> // Pontus
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POMule stored procedure fails when deployed
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USPontus Ullgren
UserOwnerUserId
1. USPontus Ullgren
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POMule stored procedure fails when deployed
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. COThanks that makes sense but I cant see anywhere that specifies this. I can see "Ability to invoke stored procedures on outbound endpoints. Supports IN parameters but not OUT parameters." but a cant see anything specifying no support for result sets.
 singulars
 PostPostId
 PO
 UserUserId
 USStuart
2. COYes it is true that this limitation is not that well documented. However looking at the code it seems that this is a conscious decision.
 singulars
 PostPostId
 PO
 UserUserId
 USPontus Ullgren

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.