[
https://issues.apache.org/jira/browse/TUSCANY-952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12476093
]
Amita Vadhavkar commented on TUSCANY-952:
-----------------------------------------
Based on the discussion on thread
http://www.mail-archive.com/tuscany-dev@ws.apache.org/msg14361.html
it was discussed that for completeness of JIRA-952, when multi schema support
is ON, the names of the stored procedures should be fully qualified (including
schema name) when these are database stored procedures. This is the convention
to be followed by user. It can not be checked programmatically, because
in case of java stored procedure, schema name is irrelevant and there is no way
to distinguish between
java stored procedure and database stored procedure. Thus, this needs to be
documented at the appropriate place in user guide.
> DAS must support queries that reference tables in different "schemas"
> ---------------------------------------------------------------------
>
> Key: TUSCANY-952
> URL: https://issues.apache.org/jira/browse/TUSCANY-952
> Project: Tuscany
> Issue Type: Bug
> Components: Java DAS RDB
> Affects Versions: Java-SCA-Mx
> Reporter: Kevin Williams
> Fix For: Java-DAS-Mx
>
> Attachments: JIRA-952-Feb16-Amita.jar
>
>
> The DAS is curently ignorant of database schema designations. This means the
> DAS will generate incorrect write statements when it processes the change
> summary from a data graph that originated from a query that uses schema names
> that are different from the default schema.
--
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]
