[jira] Updated: (TUSCANY-952) DAS must support queries that reference tables in different "schemas"
[ https://issues.apache.org/jira/browse/TUSCANY-952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amita Vadhavkar updated TUSCANY-952: Attachment: JIRA952-May22.txt Code and UT with small config files > 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 >Reporter: Kevin Williams > Fix For: Java-DAS-Mx > > Attachments: DAS-JIRA-952-Apr24-Amita.txt, JIRA-952-Details.doc, > JIRA-952-Feb16-Amita.jar, JIRA-952-Mar01-Amita.jar, > JIRA-952-rdb-das-Apr26-Amita.txt, JIRA-952-tests-Apr27-Amita.txt, > JIRA-952-tuscany-das-sample-multi-schema-Apr26-Amita.txt, JIRA952-May22.txt > > > 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]
[jira] Updated: (TUSCANY-952) DAS must support queries that reference tables in different "schemas"
[ https://issues.apache.org/jira/browse/TUSCANY-952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amita Vadhavkar updated TUSCANY-952: Attachment: JIRA-952-tests-Apr27-Amita.txt files in patch for test cases:-Apr 27 old*DatabaseSetup new*MultiSchemaData new*MultiSchemaTests old*AllCommonTests new*AllTestsDerbyMultiSchema old*rdb-das pom.xml new*2 configs Problem: When added to AllCommonTests or in a separate AllTestsDerbyMultiSchema (pom changed to invoke this) getting OutOfMemory - like below. testMultiSchemaCase14(org.apache.tuscany.das.rdb.test.MultiSchemaTests) Time el apsed: 1.382 sec <<< ERROR! java.lang.OutOfMemoryError: Java heap space java.lang.OutOfMemoryError: Java heap space When the same is run under junit in eclipse, all tests run fine. Please let me know if there is a solution. > 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 >Reporter: Kevin Williams > Fix For: Java-DAS-Mx > > Attachments: DAS-JIRA-952-Apr24-Amita.txt, JIRA-952-Details.doc, > JIRA-952-Feb16-Amita.jar, JIRA-952-Mar01-Amita.jar, > JIRA-952-rdb-das-Apr26-Amita.txt, JIRA-952-tests-Apr27-Amita.txt, > JIRA-952-tuscany-das-sample-multi-schema-Apr26-Amita.txt > > > 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]
[jira] Updated: (TUSCANY-952) DAS must support queries that reference tables in different "schemas"
[ https://issues.apache.org/jira/browse/TUSCANY-952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amita Vadhavkar updated TUSCANY-952: Attachment: JIRA-952-tuscany-das-sample-multi-schema-Apr26-Amita.txt JIRA-952-rdb-das-Apr26-Amita.txt Final code changes 1) MappingWrapper 2) QualifiedColumn 3) ResultMetadata 4) ResultSetShape 5) ConfigHelper 6) ProgrammaticConfigTests 7) DeleteGenerator 8) InsertGenerator 9) UpdateGenerator 10) ChangeFactory 11) ReadCommandImpl 12) GraphMerger 13) DatabaseObject And also other files changed are Config.xsd pom.xml from das/samples There are 2 patches 1) for the sample client 2) for rdb-das The readme under the sample gives all the details. Please let me know your review comments. > 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 >Reporter: Kevin Williams > Fix For: Java-DAS-Mx > > Attachments: DAS-JIRA-952-Apr24-Amita.txt, JIRA-952-Details.doc, > JIRA-952-Feb16-Amita.jar, JIRA-952-Mar01-Amita.jar, > JIRA-952-rdb-das-Apr26-Amita.txt, > JIRA-952-tuscany-das-sample-multi-schema-Apr26-Amita.txt > > > 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]
[jira] Updated: (TUSCANY-952) DAS must support queries that reference tables in different "schemas"
[ https://issues.apache.org/jira/browse/TUSCANY-952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amita Vadhavkar updated TUSCANY-952: Attachment: JIRA-952-Details.doc DAS-JIRA-952-Apr24-Amita.txt This patch and details doc is for the rdb-das code changes. The patch does not include any test client. And with the current unit test setup, it is not possible to add test cases to it for multiple schema testing. So, a separate J2SE client sample can be provided for test purpose, based on DB2 database. Please let me know if such sample will be useful, in that case I will work on it. > 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 >Reporter: Kevin Williams > Fix For: Java-DAS-Mx > > Attachments: DAS-JIRA-952-Apr24-Amita.txt, JIRA-952-Details.doc, > JIRA-952-Feb16-Amita.jar, JIRA-952-Mar01-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]
[jira] Updated: (TUSCANY-952) DAS must support queries that reference tables in different "schemas"
[ https://issues.apache.org/jira/browse/TUSCANY-952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amita Vadhavkar updated TUSCANY-952: Attachment: JIRA-952-Mar01-Amita.jar added more code refinement and stored procedure related note in .doc. > 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, JIRA-952-Mar01-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]
[jira] Updated: (TUSCANY-952) DAS must support queries that reference tables in different "schemas"
[ https://issues.apache.org/jira/browse/TUSCANY-952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Sebastien Delfino updated TUSCANY-952: --- Patch Info: [Patch Available] > 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]
[jira] Updated: (TUSCANY-952) DAS must support queries that reference tables in different "schemas"
[ https://issues.apache.org/jira/browse/TUSCANY-952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amita Vadhavkar updated TUSCANY-952: Attachment: JIRA-952-Feb16-Amita.jar Hi, Please see the attached details documentation, patch, jar of changed files and a sample client - where the class MultiSchemaCustomerClient is the test client using standalone J2SE conneciton to test the test cases listed in the doc. It uses DB2 database for the testing. Please do the doc and code review and let me know your feedback. Based on this and some code cleanup, I can perform code changes. > 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]
