[jira] [Created] (CAY-2714) Offset value is not copied to column select metadata
Arseni Bulatski created CAY-2714: Summary: Offset value is not copied to column select metadata Key: CAY-2714 URL: https://issues.apache.org/jira/browse/CAY-2714 Project: Cayenne Issue Type: Bug Components: Core Library Affects Versions: 4.2.M3 Reporter: Arseni Bulatski Fix For: 4.2.B1 Query ObjectSelect(A.class).offset().limit().column() doesn't contain offset value. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAY-2640) Unused import is adding to superclass after generation
Arseni Bulatski created CAY-2640: Summary: Unused import is adding to superclass after generation Key: CAY-2640 URL: https://issues.apache.org/jira/browse/CAY-2640 Project: Cayenne Issue Type: Bug Components: Core Library Affects Versions: 4.1.RC2, 4.2.M1 Reporter: Arseni Bulatski If user set createPkProperty to true and already has mapping to pk in objEntity, unused import of ExpressionFactory is adding to generated superclass. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (CAY-2612) Modeler: add lazy-loading to dbImport tab
[ https://issues.apache.org/jira/browse/CAY-2612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arseni Bulatski closed CAY-2612. Resolution: Fixed > Modeler: add lazy-loading to dbImport tab > - > > Key: CAY-2612 > URL: https://issues.apache.org/jira/browse/CAY-2612 > Project: Cayenne > Issue Type: Improvement > Components: Modeler >Reporter: Arseni Bulatski >Assignee: Arseni Bulatski >Priority: Major > Fix For: 4.2.M1 > > Time Spent: 20m > Remaining Estimate: 0h > > Add lazy-loading to dbImport tab. > First need to load only catalogs and schemas. > Then when user click on catalog or schema, tables should be loaded. > And finally columns should be loaded when user click on table. > This change will speed up loading of database and prepare for other > improvements. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (CAY-2612) Modeler: add lazy-loading to dbImport tab
[ https://issues.apache.org/jira/browse/CAY-2612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16920868#comment-16920868 ] Arseni Bulatski commented on CAY-2612: -- https://github.com/apache/cayenne/commit/277cf0f9716a3aeac1b999c9d370d5943232bfa4 > Modeler: add lazy-loading to dbImport tab > - > > Key: CAY-2612 > URL: https://issues.apache.org/jira/browse/CAY-2612 > Project: Cayenne > Issue Type: Improvement > Components: Modeler >Reporter: Arseni Bulatski >Assignee: Arseni Bulatski >Priority: Major > Fix For: 4.2.M1 > > Time Spent: 20m > Remaining Estimate: 0h > > Add lazy-loading to dbImport tab. > First need to load only catalogs and schemas. > Then when user click on catalog or schema, tables should be loaded. > And finally columns should be loaded when user click on table. > This change will speed up loading of database and prepare for other > improvements. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (CAY-2613) "tableTypes" is not defined in dbimport schema
[ https://issues.apache.org/jira/browse/CAY-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16920658#comment-16920658 ] Arseni Bulatski commented on CAY-2613: -- https://github.com/apache/cayenne-website/commit/19322782eab452ad15bab91c8b34dc84e50a348d > "tableTypes" is not defined in dbimport schema > -- > > Key: CAY-2613 > URL: https://issues.apache.org/jira/browse/CAY-2613 > Project: Cayenne > Issue Type: Bug >Affects Versions: 4.1.B3 >Reporter: Andrus Adamchik >Priority: Minor > Fix For: 4.1.B3 > > Attachments: x.png > > > I am using the latest nightly build of CayenneModeler 4.1, and is uses > "tableTypes" tag for table types. This tag is not defined in > https://cayenne.apache.org/schema/10/dbimport.xsd schema, so the IDE > complains. I think the tag was added recently, and we need to update and > republish the schema. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Created] (CAY-2612) Modeler: add lazy-loading to dbImport tab
Arseni Bulatski created CAY-2612: Summary: Modeler: add lazy-loading to dbImport tab Key: CAY-2612 URL: https://issues.apache.org/jira/browse/CAY-2612 Project: Cayenne Issue Type: Improvement Components: Modeler Reporter: Arseni Bulatski Assignee: Arseni Bulatski Fix For: 4.2.M1 Add lazy-loading to dbImport tab. First need to load only catalogs and schemas. Then when user click on catalog or schema, tables should be loaded. And finally columns should be loaded when user click on table. This change will speed up loading of database and prepare for other improvements. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Closed] (CAY-2598) Oracle dbImport bug
[ https://issues.apache.org/jira/browse/CAY-2598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arseni Bulatski closed CAY-2598. Resolution: Fixed > Oracle dbImport bug > --- > > Key: CAY-2598 > URL: https://issues.apache.org/jira/browse/CAY-2598 > Project: Cayenne > Issue Type: Bug > Components: dbimport, Modeler >Affects Versions: 4.2.M1 >Reporter: Arseni Bulatski >Assignee: Arseni Bulatski >Priority: Major > Fix For: 4.2.M1 > > > There are several problems in dbImport from Oracle database. > 1. -Running dbImport from maven plugin is not responding. Connect is > established and then plugin logs nothing.- > 2. -Modeler dbImport also has some problems.- > * -Case when you haven't got catalogs in database but have schemas: modeler > try to load all catalogs and shows that there are nothing to import but > tables in schemas exist. So the problem is that modeler try to load only > catalogs and that's all.- > * -After some changes in code schemas were loaded but when try to load all > tables from all schemas bug with the similar behavior to point 1 appeared.- > DbImport was passed after code modifications to set schema to import. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (CAY-2598) Oracle dbImport bug
[ https://issues.apache.org/jira/browse/CAY-2598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16916786#comment-16916786 ] Arseni Bulatski commented on CAY-2598: -- Fixed. > Oracle dbImport bug > --- > > Key: CAY-2598 > URL: https://issues.apache.org/jira/browse/CAY-2598 > Project: Cayenne > Issue Type: Bug > Components: dbimport, Modeler >Affects Versions: 4.2.M1 >Reporter: Arseni Bulatski >Assignee: Arseni Bulatski >Priority: Major > Fix For: 4.2.M1 > > > There are several problems in dbImport from Oracle database. > 1. -Running dbImport from maven plugin is not responding. Connect is > established and then plugin logs nothing.- > 2. -Modeler dbImport also has some problems.- > * -Case when you haven't got catalogs in database but have schemas: modeler > try to load all catalogs and shows that there are nothing to import but > tables in schemas exist. So the problem is that modeler try to load only > catalogs and that's all.- > * -After some changes in code schemas were loaded but when try to load all > tables from all schemas bug with the similar behavior to point 1 appeared.- > DbImport was passed after code modifications to set schema to import. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (CAY-2598) Oracle dbImport bug
[ https://issues.apache.org/jira/browse/CAY-2598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arseni Bulatski updated CAY-2598: - Description: There are several problems in dbImport from Oracle database. 1. -Running dbImport from maven plugin is not responding. Connect is established and then plugin logs nothing.- 2. -Modeler dbImport also has some problems.- * -Case when you haven't got catalogs in database but have schemas: modeler try to load all catalogs and shows that there are nothing to import but tables in schemas exist. So the problem is that modeler try to load only catalogs and that's all.- * -After some changes in code schemas were loaded but when try to load all tables from all schemas bug with the similar behavior to point 1 appeared.- DbImport was passed after code modifications to set schema to import. was: There are several problems in dbImport from Oracle database. 1. Running dbImport from maven plugin is not responding. Connect is established and then plugin logs nothing. 2. -Modeler dbImport also has some problems.- * -Case when you haven't got catalogs in database but have schemas: modeler try to load all catalogs and shows that there are nothing to import but tables in schemas exist. So the problem is that modeler try to load only catalogs and that's all.- * -After some changes in code schemas were loaded but when try to load all tables from all schemas bug with the similar behavior to point 1 appeared.- DbImport was passed after code modifications to set schema to import. > Oracle dbImport bug > --- > > Key: CAY-2598 > URL: https://issues.apache.org/jira/browse/CAY-2598 > Project: Cayenne > Issue Type: Bug > Components: dbimport, Modeler >Affects Versions: 4.2.M1 >Reporter: Arseni Bulatski >Assignee: Arseni Bulatski >Priority: Major > Fix For: 4.2.M1 > > > There are several problems in dbImport from Oracle database. > 1. -Running dbImport from maven plugin is not responding. Connect is > established and then plugin logs nothing.- > 2. -Modeler dbImport also has some problems.- > * -Case when you haven't got catalogs in database but have schemas: modeler > try to load all catalogs and shows that there are nothing to import but > tables in schemas exist. So the problem is that modeler try to load only > catalogs and that's all.- > * -After some changes in code schemas were loaded but when try to load all > tables from all schemas bug with the similar behavior to point 1 appeared.- > DbImport was passed after code modifications to set schema to import. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Closed] (CAY-2611) Exclude system catalogs and schemas when run dbImport without config
[ https://issues.apache.org/jira/browse/CAY-2611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arseni Bulatski closed CAY-2611. Resolution: Fixed > Exclude system catalogs and schemas when run dbImport without config > > > Key: CAY-2611 > URL: https://issues.apache.org/jira/browse/CAY-2611 > Project: Cayenne > Issue Type: Improvement > Components: dbimport >Reporter: Arseni Bulatski >Assignee: Arseni Bulatski >Priority: Major > Fix For: 4.1.B3, 4.2.M1 > > Time Spent: 20m > Remaining Estimate: 0h > > When user try to run dbImport without any filters, all system tables are > being exporting what can take a lot of time for example for oracle. > Since dbAdapters have collection of system catalogs and schemas (now oracle, > mysql have system collections) we can filter it while loading. > So if user has default config we should filter it ourselves in other cases > not to filter. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (CAY-2611) Exclude system catalogs and schemas when run dbImport without config
[ https://issues.apache.org/jira/browse/CAY-2611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16916783#comment-16916783 ] Arseni Bulatski commented on CAY-2611: -- *4.2* [https://github.com/apache/cayenne/commit/4656d18a109254d86081b8c509bba66ce5b8f7eb] *4.1* https://github.com/apache/cayenne/commit/852cf283e44d794351737b64116a0f300dbfd081 > Exclude system catalogs and schemas when run dbImport without config > > > Key: CAY-2611 > URL: https://issues.apache.org/jira/browse/CAY-2611 > Project: Cayenne > Issue Type: Improvement > Components: dbimport >Reporter: Arseni Bulatski >Assignee: Arseni Bulatski >Priority: Major > Fix For: 4.1.B3, 4.2.M1 > > Time Spent: 20m > Remaining Estimate: 0h > > When user try to run dbImport without any filters, all system tables are > being exporting what can take a lot of time for example for oracle. > Since dbAdapters have collection of system catalogs and schemas (now oracle, > mysql have system collections) we can filter it while loading. > So if user has default config we should filter it ourselves in other cases > not to filter. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (CAY-2611) Exclude system catalogs and schemas when run dbImport without config
[ https://issues.apache.org/jira/browse/CAY-2611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arseni Bulatski updated CAY-2611: - Affects Version/s: (was: 4.1.B2) (was: 4.2.M1) > Exclude system catalogs and schemas when run dbImport without config > > > Key: CAY-2611 > URL: https://issues.apache.org/jira/browse/CAY-2611 > Project: Cayenne > Issue Type: Improvement > Components: dbimport >Reporter: Arseni Bulatski >Assignee: Arseni Bulatski >Priority: Major > Fix For: 4.1.B3, 4.2.M1 > > Time Spent: 10m > Remaining Estimate: 0h > > When user try to run dbImport without any filters, all system tables are > being exporting what can take a lot of time for example for oracle. > Since dbAdapters have collection of system catalogs and schemas (now oracle, > mysql have system collections) we can filter it while loading. > So if user has default config we should filter it ourselves in other cases > not to filter. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (CAY-2598) Oracle dbImport bug
[ https://issues.apache.org/jira/browse/CAY-2598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16916681#comment-16916681 ] Arseni Bulatski commented on CAY-2598: -- When CAY-2611 will be merged, first point of this task should be fixed and task can be closed. > Oracle dbImport bug > --- > > Key: CAY-2598 > URL: https://issues.apache.org/jira/browse/CAY-2598 > Project: Cayenne > Issue Type: Bug > Components: dbimport, Modeler >Affects Versions: 4.2.M1 >Reporter: Arseni Bulatski >Assignee: Arseni Bulatski >Priority: Major > Fix For: 4.2.M1 > > > There are several problems in dbImport from Oracle database. > 1. Running dbImport from maven plugin is not responding. Connect is > established and then plugin logs nothing. > 2. -Modeler dbImport also has some problems.- > * -Case when you haven't got catalogs in database but have schemas: modeler > try to load all catalogs and shows that there are nothing to import but > tables in schemas exist. So the problem is that modeler try to load only > catalogs and that's all.- > * -After some changes in code schemas were loaded but when try to load all > tables from all schemas bug with the similar behavior to point 1 appeared.- > DbImport was passed after code modifications to set schema to import. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Created] (CAY-2611) Exclude system catalogs and schemas when run dbImport without config
Arseni Bulatski created CAY-2611: Summary: Exclude system catalogs and schemas when run dbImport without config Key: CAY-2611 URL: https://issues.apache.org/jira/browse/CAY-2611 Project: Cayenne Issue Type: Improvement Components: dbimport Affects Versions: 4.1.B2, 4.2.M1 Reporter: Arseni Bulatski Assignee: Arseni Bulatski Fix For: 4.1.B3, 4.2.M1 When user try to run dbImport without any filters, all system tables are being exporting what can take a lot of time for example for oracle. Since dbAdapters have collection of system catalogs and schemas (now oracle, mysql have system collections) we can filter it while loading. So if user has default config we should filter it ourselves in other cases not to filter. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (CAY-2598) Oracle dbImport bug
[ https://issues.apache.org/jira/browse/CAY-2598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16915863#comment-16915863 ] Arseni Bulatski commented on CAY-2598: -- DbImport plugin execution is not responding for oracle because it try to load all schemas including system schemas what take a lot of time. It can be fixed if we will filter system schemas before trying to load tables. > Oracle dbImport bug > --- > > Key: CAY-2598 > URL: https://issues.apache.org/jira/browse/CAY-2598 > Project: Cayenne > Issue Type: Bug > Components: dbimport, Modeler >Affects Versions: 4.2.M1 >Reporter: Arseni Bulatski >Assignee: Arseni Bulatski >Priority: Major > Fix For: 4.2.M1 > > > There are several problems in dbImport from Oracle database. > 1. Running dbImport from maven plugin is not responding. Connect is > established and then plugin logs nothing. > 2. -Modeler dbImport also has some problems.- > * -Case when you haven't got catalogs in database but have schemas: modeler > try to load all catalogs and shows that there are nothing to import but > tables in schemas exist. So the problem is that modeler try to load only > catalogs and that's all.- > * -After some changes in code schemas were loaded but when try to load all > tables from all schemas bug with the similar behavior to point 1 appeared.- > DbImport was passed after code modifications to set schema to import. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (CAY-2598) Oracle dbImport bug
[ https://issues.apache.org/jira/browse/CAY-2598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arseni Bulatski updated CAY-2598: - Description: There are several problems in dbImport from Oracle database. 1. Running dbImport from maven plugin is not responding. Connect is established and then plugin logs nothing. 2. -Modeler dbImport also has some problems.- * -Case when you haven't got catalogs in database but have schemas: modeler try to load all catalogs and shows that there are nothing to import but tables in schemas exist. So the problem is that modeler try to load only catalogs and that's all.- * -After some changes in code schemas were loaded but when try to load all tables from all schemas bug with the similar behavior to point 1 appeared.- DbImport was passed after code modifications to set schema to import. was: There are several problems in dbImport from Oracle database. 1. Running dbImport from maven plugin is not responding. Connect is established and then plugin logs nothing. 2. Modeler dbImport also has some problems. * Case when you haven't got catalogs in database but have schemas: modeler try to load all catalogs and shows that there are nothing to import but tables in schemas exist. So the problem is that modeler try to load only catalogs and that's all. * After some changes in code schemas were loaded but when try to load all tables from all schemas bug with the similar behavior to point 1 appeared. DbImport was passed after code modifications to set schema to import. > Oracle dbImport bug > --- > > Key: CAY-2598 > URL: https://issues.apache.org/jira/browse/CAY-2598 > Project: Cayenne > Issue Type: Bug > Components: dbimport, Modeler >Affects Versions: 4.2.M1 >Reporter: Arseni Bulatski >Assignee: Arseni Bulatski >Priority: Major > Fix For: 4.2.M1 > > > There are several problems in dbImport from Oracle database. > 1. Running dbImport from maven plugin is not responding. Connect is > established and then plugin logs nothing. > 2. -Modeler dbImport also has some problems.- > * -Case when you haven't got catalogs in database but have schemas: modeler > try to load all catalogs and shows that there are nothing to import but > tables in schemas exist. So the problem is that modeler try to load only > catalogs and that's all.- > * -After some changes in code schemas were loaded but when try to load all > tables from all schemas bug with the similar behavior to point 1 appeared.- > DbImport was passed after code modifications to set schema to import. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Closed] (CAY-2609) Modeler: can't close dbImport result dialog window
[ https://issues.apache.org/jira/browse/CAY-2609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arseni Bulatski closed CAY-2609. Resolution: Fixed > Modeler: can't close dbImport result dialog window > -- > > Key: CAY-2609 > URL: https://issues.apache.org/jira/browse/CAY-2609 > Project: Cayenne > Issue Type: Bug > Components: Modeler >Affects Versions: 4.1.B2 >Reporter: Arseni Bulatski >Assignee: Arseni Bulatski >Priority: Minor > Fix For: 4.1.B3, 4.2.M1 > > > When user click to start reverse engineering and there are a lot of data to > import, dialog window with progress bar appears. > If user click to the cancel button, dbImport result dialog are shown but then > it can't be closed. > It appears when user click cancel at the beginning of process. > To reproduce: > * Open dbImport tab > * Click run import > * Click cancel in progress dialog window -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Closed] (CAY-2608) CayenneModeler: NPE when reverse engineering with an auto-adapter DataSource
[
https://issues.apache.org/jira/browse/CAY-2608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arseni Bulatski closed CAY-2608.
Resolution: Fixed
> CayenneModeler: NPE when reverse engineering with an auto-adapter DataSource
>
>
> Key: CAY-2608
> URL: https://issues.apache.org/jira/browse/CAY-2608
> Project: Cayenne
> Issue Type: Bug
>Affects Versions: 4.1.B3, 4.2.M1
> Environment: CayenneModeler 4.1.B3-SNAPSHOT, my own Mac assembly
>Reporter: Andrus Adamchik
>Assignee: Arseni Bulatski
>Priority: Minor
> Fix For: 4.1.B3, 4.2.M1
>
>
> 0. In the modeler preferences create a DataSource with "Automatic" adapter
> 1. Start a new project
> 2. Create a new DataMap
> 3. Switch to "DbImport" tab, click "Run Import"
> 4. When prompted, select the DataSource above and click "Continue"
> Result: error dialog with the exception below.
> {noformat}
> CayenneModeler Info
> Version: 4.1.B3-SNAPSHOT
> Build Date: Aug 20 2019 11:02:28
> Exception:
> =
> java.lang.NullPointerException
> at
> java.prefs/java.util.prefs.AbstractPreferences.put(AbstractPreferences.java:249)
> at
> org.apache.cayenne.modeler.action.ReverseEngineeringAction.saveConnectionInfo(ReverseEngineeringAction.java:160)
> at
> org.apache.cayenne.modeler.action.ReverseEngineeringAction.startImport(ReverseEngineeringAction.java:91)
> at
> org.apache.cayenne.modeler.action.ReverseEngineeringAction.performAction(ReverseEngineeringAction.java:137)
> at
> org.apache.cayenne.modeler.util.CayenneAction.actionPerformed(CayenneAction.java:171)
> at
> java.desktop/javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1967)
> at
> java.desktop/javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2308)
> at
> java.desktop/javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:405)
> at
> java.desktop/javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:262)
> at
> java.desktop/javax.swing.plaf.basic.BasicButtonListener.mouseReleased(BasicButtonListener.java:279)
> at
> java.desktop/java.awt.AWTEventMulticaster.mouseReleased(AWTEventMulticaster.java:297)
> at
> java.desktop/java.awt.Component.processMouseEvent(Component.java:6632)
> at
> java.desktop/javax.swing.JComponent.processMouseEvent(JComponent.java:3342)
> at java.desktop/java.awt.Component.processEvent(Component.java:6397)
> at java.desktop/java.awt.Container.processEvent(Container.java:2263)
> at
> java.desktop/java.awt.Component.dispatchEventImpl(Component.java:5008)
> at
> java.desktop/java.awt.Container.dispatchEventImpl(Container.java:2321)
> at java.desktop/java.awt.Component.dispatchEvent(Component.java:4840)
> at
> java.desktop/java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4918)
> at
> java.desktop/java.awt.LightweightDispatcher.processMouseEvent(Container.java:4547)
> at
> java.desktop/java.awt.LightweightDispatcher.dispatchEvent(Container.java:4488)
> at
> java.desktop/java.awt.Container.dispatchEventImpl(Container.java:2307)
> at java.desktop/java.awt.Window.dispatchEventImpl(Window.java:2762)
> at java.desktop/java.awt.Component.dispatchEvent(Component.java:4840)
> at
> java.desktop/java.awt.EventQueue.dispatchEventImpl(EventQueue.java:772)
> at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:721)
> at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:715)
> at
> java.base/java.security.AccessController.doPrivileged(AccessController.java:389)
> at
> java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:85)
> at
> java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:95)
> at java.desktop/java.awt.EventQueue$5.run(EventQueue.java:745)
> at java.desktop/java.awt.EventQueue$5.run(EventQueue.java:743)
> at
> java.base/java.security.AccessController.doPrivileged(AccessController.java:389)
> at
> java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:85)
> at java.desktop/java.awt.EventQueue.dispatchEvent(EventQueue.java:742)
> at
> java.desktop/java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:203)
> at
> java.desktop/java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:124)
> at
> java.desktop/java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:113)
> at
>
[jira] [Closed] (CAY-2600) Modeler DbImport: Can't retrieve schema for databases with no catalog support
[
https://issues.apache.org/jira/browse/CAY-2600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arseni Bulatski closed CAY-2600.
Resolution: Fixed
> Modeler DbImport: Can't retrieve schema for databases with no catalog support
> -
>
> Key: CAY-2600
> URL: https://issues.apache.org/jira/browse/CAY-2600
> Project: Cayenne
> Issue Type: Bug
>Affects Versions: 4.1.B2
>Reporter: Andrus Adamchik
>Assignee: Arseni Bulatski
>Priority: Major
> Fix For: 4.1.B3, 4.2.M1
>
>
> I am trying to db-import model for Hana DB. DB Import itself ("Run Import"
> button) works, if I manually add all the settings. However "Refresh DB
> Schema" button results in an empty schema.
> The cause of it seems to be the implementation of DatabaseSchemaLoader.load
> method. It looks for catalogs, and if none found, returns an empty result.
> Hana does not support catalogs, but supports schemas. And we need to support
> this case.
> I guess in general we need to support all combinations of schema and catalog
> presence across different databases:
> 1. Schema and Catalog (?)
> 2. Catalog only (MySQL)
> 3. Schema only (Hana ... who else?)
> 4. No schema or catalog (any DBs like this?)
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Updated] (CAY-2608) CayenneModeler: NPE when reverse engineering with an auto-adapter DataSource
[
https://issues.apache.org/jira/browse/CAY-2608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arseni Bulatski updated CAY-2608:
-
Affects Version/s: 4.2.M1
> CayenneModeler: NPE when reverse engineering with an auto-adapter DataSource
>
>
> Key: CAY-2608
> URL: https://issues.apache.org/jira/browse/CAY-2608
> Project: Cayenne
> Issue Type: Bug
>Affects Versions: 4.1.B3, 4.2.M1
> Environment: CayenneModeler 4.1.B3-SNAPSHOT, my own Mac assembly
>Reporter: Andrus Adamchik
>Assignee: Arseni Bulatski
>Priority: Minor
> Fix For: 4.1.B3, 4.2.M1
>
>
> 0. In the modeler preferences create a DataSource with "Automatic" adapter
> 1. Start a new project
> 2. Create a new DataMap
> 3. Switch to "DbImport" tab, click "Run Import"
> 4. When prompted, select the DataSource above and click "Continue"
> Result: error dialog with the exception below.
> {noformat}
> CayenneModeler Info
> Version: 4.1.B3-SNAPSHOT
> Build Date: Aug 20 2019 11:02:28
> Exception:
> =
> java.lang.NullPointerException
> at
> java.prefs/java.util.prefs.AbstractPreferences.put(AbstractPreferences.java:249)
> at
> org.apache.cayenne.modeler.action.ReverseEngineeringAction.saveConnectionInfo(ReverseEngineeringAction.java:160)
> at
> org.apache.cayenne.modeler.action.ReverseEngineeringAction.startImport(ReverseEngineeringAction.java:91)
> at
> org.apache.cayenne.modeler.action.ReverseEngineeringAction.performAction(ReverseEngineeringAction.java:137)
> at
> org.apache.cayenne.modeler.util.CayenneAction.actionPerformed(CayenneAction.java:171)
> at
> java.desktop/javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1967)
> at
> java.desktop/javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2308)
> at
> java.desktop/javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:405)
> at
> java.desktop/javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:262)
> at
> java.desktop/javax.swing.plaf.basic.BasicButtonListener.mouseReleased(BasicButtonListener.java:279)
> at
> java.desktop/java.awt.AWTEventMulticaster.mouseReleased(AWTEventMulticaster.java:297)
> at
> java.desktop/java.awt.Component.processMouseEvent(Component.java:6632)
> at
> java.desktop/javax.swing.JComponent.processMouseEvent(JComponent.java:3342)
> at java.desktop/java.awt.Component.processEvent(Component.java:6397)
> at java.desktop/java.awt.Container.processEvent(Container.java:2263)
> at
> java.desktop/java.awt.Component.dispatchEventImpl(Component.java:5008)
> at
> java.desktop/java.awt.Container.dispatchEventImpl(Container.java:2321)
> at java.desktop/java.awt.Component.dispatchEvent(Component.java:4840)
> at
> java.desktop/java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4918)
> at
> java.desktop/java.awt.LightweightDispatcher.processMouseEvent(Container.java:4547)
> at
> java.desktop/java.awt.LightweightDispatcher.dispatchEvent(Container.java:4488)
> at
> java.desktop/java.awt.Container.dispatchEventImpl(Container.java:2307)
> at java.desktop/java.awt.Window.dispatchEventImpl(Window.java:2762)
> at java.desktop/java.awt.Component.dispatchEvent(Component.java:4840)
> at
> java.desktop/java.awt.EventQueue.dispatchEventImpl(EventQueue.java:772)
> at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:721)
> at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:715)
> at
> java.base/java.security.AccessController.doPrivileged(AccessController.java:389)
> at
> java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:85)
> at
> java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:95)
> at java.desktop/java.awt.EventQueue$5.run(EventQueue.java:745)
> at java.desktop/java.awt.EventQueue$5.run(EventQueue.java:743)
> at
> java.base/java.security.AccessController.doPrivileged(AccessController.java:389)
> at
> java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:85)
> at java.desktop/java.awt.EventQueue.dispatchEvent(EventQueue.java:742)
> at
> java.desktop/java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:203)
> at
> java.desktop/java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:124)
> at
> java.desktop/java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:113)
> at
>
[jira] [Updated] (CAY-2608) CayenneModeler: NPE when reverse engineering with an auto-adapter DataSource
[
https://issues.apache.org/jira/browse/CAY-2608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arseni Bulatski updated CAY-2608:
-
Fix Version/s: 4.2.M1
> CayenneModeler: NPE when reverse engineering with an auto-adapter DataSource
>
>
> Key: CAY-2608
> URL: https://issues.apache.org/jira/browse/CAY-2608
> Project: Cayenne
> Issue Type: Bug
>Affects Versions: 4.1.B3
> Environment: CayenneModeler 4.1.B3-SNAPSHOT, my own Mac assembly
>Reporter: Andrus Adamchik
>Assignee: Arseni Bulatski
>Priority: Minor
> Fix For: 4.1.B3, 4.2.M1
>
>
> 0. In the modeler preferences create a DataSource with "Automatic" adapter
> 1. Start a new project
> 2. Create a new DataMap
> 3. Switch to "DbImport" tab, click "Run Import"
> 4. When prompted, select the DataSource above and click "Continue"
> Result: error dialog with the exception below.
> {noformat}
> CayenneModeler Info
> Version: 4.1.B3-SNAPSHOT
> Build Date: Aug 20 2019 11:02:28
> Exception:
> =
> java.lang.NullPointerException
> at
> java.prefs/java.util.prefs.AbstractPreferences.put(AbstractPreferences.java:249)
> at
> org.apache.cayenne.modeler.action.ReverseEngineeringAction.saveConnectionInfo(ReverseEngineeringAction.java:160)
> at
> org.apache.cayenne.modeler.action.ReverseEngineeringAction.startImport(ReverseEngineeringAction.java:91)
> at
> org.apache.cayenne.modeler.action.ReverseEngineeringAction.performAction(ReverseEngineeringAction.java:137)
> at
> org.apache.cayenne.modeler.util.CayenneAction.actionPerformed(CayenneAction.java:171)
> at
> java.desktop/javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1967)
> at
> java.desktop/javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2308)
> at
> java.desktop/javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:405)
> at
> java.desktop/javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:262)
> at
> java.desktop/javax.swing.plaf.basic.BasicButtonListener.mouseReleased(BasicButtonListener.java:279)
> at
> java.desktop/java.awt.AWTEventMulticaster.mouseReleased(AWTEventMulticaster.java:297)
> at
> java.desktop/java.awt.Component.processMouseEvent(Component.java:6632)
> at
> java.desktop/javax.swing.JComponent.processMouseEvent(JComponent.java:3342)
> at java.desktop/java.awt.Component.processEvent(Component.java:6397)
> at java.desktop/java.awt.Container.processEvent(Container.java:2263)
> at
> java.desktop/java.awt.Component.dispatchEventImpl(Component.java:5008)
> at
> java.desktop/java.awt.Container.dispatchEventImpl(Container.java:2321)
> at java.desktop/java.awt.Component.dispatchEvent(Component.java:4840)
> at
> java.desktop/java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4918)
> at
> java.desktop/java.awt.LightweightDispatcher.processMouseEvent(Container.java:4547)
> at
> java.desktop/java.awt.LightweightDispatcher.dispatchEvent(Container.java:4488)
> at
> java.desktop/java.awt.Container.dispatchEventImpl(Container.java:2307)
> at java.desktop/java.awt.Window.dispatchEventImpl(Window.java:2762)
> at java.desktop/java.awt.Component.dispatchEvent(Component.java:4840)
> at
> java.desktop/java.awt.EventQueue.dispatchEventImpl(EventQueue.java:772)
> at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:721)
> at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:715)
> at
> java.base/java.security.AccessController.doPrivileged(AccessController.java:389)
> at
> java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:85)
> at
> java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:95)
> at java.desktop/java.awt.EventQueue$5.run(EventQueue.java:745)
> at java.desktop/java.awt.EventQueue$5.run(EventQueue.java:743)
> at
> java.base/java.security.AccessController.doPrivileged(AccessController.java:389)
> at
> java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:85)
> at java.desktop/java.awt.EventQueue.dispatchEvent(EventQueue.java:742)
> at
> java.desktop/java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:203)
> at
> java.desktop/java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:124)
> at
> java.desktop/java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:113)
> at
>
[jira] [Commented] (CAY-2609) Modeler: can't close dbImport result dialog window
[ https://issues.apache.org/jira/browse/CAY-2609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16915790#comment-16915790 ] Arseni Bulatski commented on CAY-2609: -- *4.1* [https://github.com/apache/cayenne/commit/8cb272f2fca9964bd817b5b7ba6ad7e92322ac74] *4.2* https://github.com/apache/cayenne/commit/fdc03b94e66877c18fc04e71ec9235b533aa8c3c > Modeler: can't close dbImport result dialog window > -- > > Key: CAY-2609 > URL: https://issues.apache.org/jira/browse/CAY-2609 > Project: Cayenne > Issue Type: Bug > Components: Modeler >Affects Versions: 4.1.B2 >Reporter: Arseni Bulatski >Assignee: Arseni Bulatski >Priority: Minor > Fix For: 4.1.B3, 4.2.M1 > > > When user click to start reverse engineering and there are a lot of data to > import, dialog window with progress bar appears. > If user click to the cancel button, dbImport result dialog are shown but then > it can't be closed. > It appears when user click cancel at the beginning of process. > To reproduce: > * Open dbImport tab > * Click run import > * Click cancel in progress dialog window -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (CAY-2608) CayenneModeler: NPE when reverse engineering with an auto-adapter DataSource
[
https://issues.apache.org/jira/browse/CAY-2608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16915626#comment-16915626
]
Arseni Bulatski commented on CAY-2608:
--
*4.2*
[https://github.com/apache/cayenne/commit/efc3834458874e42f60dd347c797f21200ccdd1e]
*4.1*
https://github.com/apache/cayenne/commit/761fceea3edd49ef784d43e9d0e01c6f428d71f5
> CayenneModeler: NPE when reverse engineering with an auto-adapter DataSource
>
>
> Key: CAY-2608
> URL: https://issues.apache.org/jira/browse/CAY-2608
> Project: Cayenne
> Issue Type: Bug
>Affects Versions: 4.1.B3
> Environment: CayenneModeler 4.1.B3-SNAPSHOT, my own Mac assembly
>Reporter: Andrus Adamchik
>Priority: Minor
> Fix For: 4.1.B3
>
>
> 0. In the modeler preferences create a DataSource with "Automatic" adapter
> 1. Start a new project
> 2. Create a new DataMap
> 3. Switch to "DbImport" tab, click "Run Import"
> 4. When prompted, select the DataSource above and click "Continue"
> Result: error dialog with the exception below.
> {noformat}
> CayenneModeler Info
> Version: 4.1.B3-SNAPSHOT
> Build Date: Aug 20 2019 11:02:28
> Exception:
> =
> java.lang.NullPointerException
> at
> java.prefs/java.util.prefs.AbstractPreferences.put(AbstractPreferences.java:249)
> at
> org.apache.cayenne.modeler.action.ReverseEngineeringAction.saveConnectionInfo(ReverseEngineeringAction.java:160)
> at
> org.apache.cayenne.modeler.action.ReverseEngineeringAction.startImport(ReverseEngineeringAction.java:91)
> at
> org.apache.cayenne.modeler.action.ReverseEngineeringAction.performAction(ReverseEngineeringAction.java:137)
> at
> org.apache.cayenne.modeler.util.CayenneAction.actionPerformed(CayenneAction.java:171)
> at
> java.desktop/javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1967)
> at
> java.desktop/javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2308)
> at
> java.desktop/javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:405)
> at
> java.desktop/javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:262)
> at
> java.desktop/javax.swing.plaf.basic.BasicButtonListener.mouseReleased(BasicButtonListener.java:279)
> at
> java.desktop/java.awt.AWTEventMulticaster.mouseReleased(AWTEventMulticaster.java:297)
> at
> java.desktop/java.awt.Component.processMouseEvent(Component.java:6632)
> at
> java.desktop/javax.swing.JComponent.processMouseEvent(JComponent.java:3342)
> at java.desktop/java.awt.Component.processEvent(Component.java:6397)
> at java.desktop/java.awt.Container.processEvent(Container.java:2263)
> at
> java.desktop/java.awt.Component.dispatchEventImpl(Component.java:5008)
> at
> java.desktop/java.awt.Container.dispatchEventImpl(Container.java:2321)
> at java.desktop/java.awt.Component.dispatchEvent(Component.java:4840)
> at
> java.desktop/java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4918)
> at
> java.desktop/java.awt.LightweightDispatcher.processMouseEvent(Container.java:4547)
> at
> java.desktop/java.awt.LightweightDispatcher.dispatchEvent(Container.java:4488)
> at
> java.desktop/java.awt.Container.dispatchEventImpl(Container.java:2307)
> at java.desktop/java.awt.Window.dispatchEventImpl(Window.java:2762)
> at java.desktop/java.awt.Component.dispatchEvent(Component.java:4840)
> at
> java.desktop/java.awt.EventQueue.dispatchEventImpl(EventQueue.java:772)
> at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:721)
> at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:715)
> at
> java.base/java.security.AccessController.doPrivileged(AccessController.java:389)
> at
> java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:85)
> at
> java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:95)
> at java.desktop/java.awt.EventQueue$5.run(EventQueue.java:745)
> at java.desktop/java.awt.EventQueue$5.run(EventQueue.java:743)
> at
> java.base/java.security.AccessController.doPrivileged(AccessController.java:389)
> at
> java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:85)
> at java.desktop/java.awt.EventQueue.dispatchEvent(EventQueue.java:742)
> at
> java.desktop/java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:203)
> at
> java.desktop/java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:124)
> at
>
[jira] [Assigned] (CAY-2608) CayenneModeler: NPE when reverse engineering with an auto-adapter DataSource
[
https://issues.apache.org/jira/browse/CAY-2608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arseni Bulatski reassigned CAY-2608:
Assignee: Arseni Bulatski
> CayenneModeler: NPE when reverse engineering with an auto-adapter DataSource
>
>
> Key: CAY-2608
> URL: https://issues.apache.org/jira/browse/CAY-2608
> Project: Cayenne
> Issue Type: Bug
>Affects Versions: 4.1.B3
> Environment: CayenneModeler 4.1.B3-SNAPSHOT, my own Mac assembly
>Reporter: Andrus Adamchik
>Assignee: Arseni Bulatski
>Priority: Minor
> Fix For: 4.1.B3
>
>
> 0. In the modeler preferences create a DataSource with "Automatic" adapter
> 1. Start a new project
> 2. Create a new DataMap
> 3. Switch to "DbImport" tab, click "Run Import"
> 4. When prompted, select the DataSource above and click "Continue"
> Result: error dialog with the exception below.
> {noformat}
> CayenneModeler Info
> Version: 4.1.B3-SNAPSHOT
> Build Date: Aug 20 2019 11:02:28
> Exception:
> =
> java.lang.NullPointerException
> at
> java.prefs/java.util.prefs.AbstractPreferences.put(AbstractPreferences.java:249)
> at
> org.apache.cayenne.modeler.action.ReverseEngineeringAction.saveConnectionInfo(ReverseEngineeringAction.java:160)
> at
> org.apache.cayenne.modeler.action.ReverseEngineeringAction.startImport(ReverseEngineeringAction.java:91)
> at
> org.apache.cayenne.modeler.action.ReverseEngineeringAction.performAction(ReverseEngineeringAction.java:137)
> at
> org.apache.cayenne.modeler.util.CayenneAction.actionPerformed(CayenneAction.java:171)
> at
> java.desktop/javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1967)
> at
> java.desktop/javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2308)
> at
> java.desktop/javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:405)
> at
> java.desktop/javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:262)
> at
> java.desktop/javax.swing.plaf.basic.BasicButtonListener.mouseReleased(BasicButtonListener.java:279)
> at
> java.desktop/java.awt.AWTEventMulticaster.mouseReleased(AWTEventMulticaster.java:297)
> at
> java.desktop/java.awt.Component.processMouseEvent(Component.java:6632)
> at
> java.desktop/javax.swing.JComponent.processMouseEvent(JComponent.java:3342)
> at java.desktop/java.awt.Component.processEvent(Component.java:6397)
> at java.desktop/java.awt.Container.processEvent(Container.java:2263)
> at
> java.desktop/java.awt.Component.dispatchEventImpl(Component.java:5008)
> at
> java.desktop/java.awt.Container.dispatchEventImpl(Container.java:2321)
> at java.desktop/java.awt.Component.dispatchEvent(Component.java:4840)
> at
> java.desktop/java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4918)
> at
> java.desktop/java.awt.LightweightDispatcher.processMouseEvent(Container.java:4547)
> at
> java.desktop/java.awt.LightweightDispatcher.dispatchEvent(Container.java:4488)
> at
> java.desktop/java.awt.Container.dispatchEventImpl(Container.java:2307)
> at java.desktop/java.awt.Window.dispatchEventImpl(Window.java:2762)
> at java.desktop/java.awt.Component.dispatchEvent(Component.java:4840)
> at
> java.desktop/java.awt.EventQueue.dispatchEventImpl(EventQueue.java:772)
> at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:721)
> at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:715)
> at
> java.base/java.security.AccessController.doPrivileged(AccessController.java:389)
> at
> java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:85)
> at
> java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:95)
> at java.desktop/java.awt.EventQueue$5.run(EventQueue.java:745)
> at java.desktop/java.awt.EventQueue$5.run(EventQueue.java:743)
> at
> java.base/java.security.AccessController.doPrivileged(AccessController.java:389)
> at
> java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:85)
> at java.desktop/java.awt.EventQueue.dispatchEvent(EventQueue.java:742)
> at
> java.desktop/java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:203)
> at
> java.desktop/java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:124)
> at
> java.desktop/java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:113)
> at
>
[jira] [Created] (CAY-2609) Modeler: can't close dbImport result dialog window
Arseni Bulatski created CAY-2609: Summary: Modeler: can't close dbImport result dialog window Key: CAY-2609 URL: https://issues.apache.org/jira/browse/CAY-2609 Project: Cayenne Issue Type: Bug Components: Modeler Affects Versions: 4.1.B2 Reporter: Arseni Bulatski Fix For: 4.1.B3, 4.2.M1 When user click to start reverse engineering and there are a lot of data to import, dialog window with progress bar appears. If user click to the cancel button, dbImport result dialog are shown but then it can't be closed. It appears when user click cancel at the beginning of process. To reproduce: * Open dbImport tab * Click run import * Click cancel in progress dialog window -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (CAY-2600) Modeler DbImport: Can't retrieve schema for databases with no catalog support
[
https://issues.apache.org/jira/browse/CAY-2600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16914270#comment-16914270
]
Arseni Bulatski commented on CAY-2600:
--
*4.1*
[https://github.com/apache/cayenne/commit/8d5a9fe1f0b228cd7668c3599c5aa73ad28fa252]
*4.2*
https://github.com/apache/cayenne/commit/dc088800eab47bd6b8a34144ef051d6f8c155879
> Modeler DbImport: Can't retrieve schema for databases with no catalog support
> -
>
> Key: CAY-2600
> URL: https://issues.apache.org/jira/browse/CAY-2600
> Project: Cayenne
> Issue Type: Bug
>Affects Versions: 4.1.B2
>Reporter: Andrus Adamchik
>Priority: Major
> Fix For: 4.1.B3, 4.2.M1
>
>
> I am trying to db-import model for Hana DB. DB Import itself ("Run Import"
> button) works, if I manually add all the settings. However "Refresh DB
> Schema" button results in an empty schema.
> The cause of it seems to be the implementation of DatabaseSchemaLoader.load
> method. It looks for catalogs, and if none found, returns an empty result.
> Hana does not support catalogs, but supports schemas. And we need to support
> this case.
> I guess in general we need to support all combinations of schema and catalog
> presence across different databases:
> 1. Schema and Catalog (?)
> 2. Catalog only (MySQL)
> 3. Schema only (Hana ... who else?)
> 4. No schema or catalog (any DBs like this?)
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Commented] (CAY-2600) Modeler DbImport: Can't retrieve schema for databases with no catalog support
[
https://issues.apache.org/jira/browse/CAY-2600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16908088#comment-16908088
]
Arseni Bulatski commented on CAY-2600:
--
[~andrus] I tried it on Oracle db what behavior is similar to Hana, I mean
Oracle also has only schemas. And it works. Hope on Hana it will work too.
Also run on Postgres and on MySQL.
> Modeler DbImport: Can't retrieve schema for databases with no catalog support
> -
>
> Key: CAY-2600
> URL: https://issues.apache.org/jira/browse/CAY-2600
> Project: Cayenne
> Issue Type: Bug
>Affects Versions: 4.1.B2
>Reporter: Andrus Adamchik
>Priority: Major
> Fix For: 4.1.B3, 4.2.M1
>
>
> I am trying to db-import model for Hana DB. DB Import itself ("Run Import"
> button) works, if I manually add all the settings. However "Refresh DB
> Schema" button results in an empty schema.
> The cause of it seems to be the implementation of DatabaseSchemaLoader.load
> method. It looks for catalogs, and if none found, returns an empty result.
> Hana does not support catalogs, but supports schemas. And we need to support
> this case.
> I guess in general we need to support all combinations of schema and catalog
> presence across different databases:
> 1. Schema and Catalog (?)
> 2. Catalog only (MySQL)
> 3. Schema only (Hana ... who else?)
> 4. No schema or catalog (any DBs like this?)
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Updated] (CAY-2498) Rename packages to prevent crossing package names
[ https://issues.apache.org/jira/browse/CAY-2498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arseni Bulatski updated CAY-2498: - Description: Need to rename packages to prevent crossing package names when using java modularity. Conflicts were found between: 1) cayenne-project-compatibility and cayenne-server 2) cayenne-rop-server and cayenne-server 3) cayenne-client and cayenne-client-jetty 4) cayenne-server and cayenne-dbcp2 5) cayenne-server and jgroups, jms, xmpp 6) cayenne-protostuff and cayenne-server was: Need to rename packages to prevent crossing package names when using java modularity. Conflicts were found between: 1) cayenne-project-compatibility and cayenne-server 2) cayenne-rap-server and cayenne-server 3) cayenne-client and cayenne-client-jetty 4) cayenne-server and cayenne-dbcp2 5) cayenne-server and jgroups, jms, xmpp 6) cayenne-protostuff and cayenne-server > Rename packages to prevent crossing package names > - > > Key: CAY-2498 > URL: https://issues.apache.org/jira/browse/CAY-2498 > Project: Cayenne > Issue Type: Task > Components: Core Library, ROP >Reporter: Arseni Bulatski >Priority: Major > Fix For: 4.2.M1 > > > Need to rename packages to prevent crossing package names when using java > modularity. > Conflicts were found between: > 1) cayenne-project-compatibility and cayenne-server > 2) cayenne-rop-server and cayenne-server > 3) cayenne-client and cayenne-client-jetty > 4) cayenne-server and cayenne-dbcp2 > 5) cayenne-server and jgroups, jms, xmpp > 6) cayenne-protostuff and cayenne-server -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (CAY-2600) Modeler DbImport: Can't retrieve schema for databases with no catalog support
[
https://issues.apache.org/jira/browse/CAY-2600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16908003#comment-16908003
]
Arseni Bulatski commented on CAY-2600:
--
*4.1*
[https://github.com/apache/cayenne/commit/fc52cf219e9fb01f8e72e7bd9e0467af24c2a3b0]
*4.2*
[https://github.com/apache/cayenne/commit/285d75237d8b0659771c2f219562b57397f19f02]
One case was left. I'm not sure that it really exists.
According to JDBC specifications if user sets null to catalog or schema filter,
database should return all catalogs or schemas.
But if there is some database what doesn't follow this specification and
requires not null catalog and schema at the same time probably some bug will
appear.
But it looks like something extraordinary.
> Modeler DbImport: Can't retrieve schema for databases with no catalog support
> -
>
> Key: CAY-2600
> URL: https://issues.apache.org/jira/browse/CAY-2600
> Project: Cayenne
> Issue Type: Bug
>Affects Versions: 4.1.B2
>Reporter: Andrus Adamchik
>Priority: Major
> Fix For: 4.1.B3, 4.2.M1
>
>
> I am trying to db-import model for Hana DB. DB Import itself ("Run Import"
> button) works, if I manually add all the settings. However "Refresh DB
> Schema" button results in an empty schema.
> The cause of it seems to be the implementation of DatabaseSchemaLoader.load
> method. It looks for catalogs, and if none found, returns an empty result.
> Hana does not support catalogs, but supports schemas. And we need to support
> this case.
> I guess in general we need to support all combinations of schema and catalog
> presence across different databases:
> 1. Schema and Catalog (?)
> 2. Catalog only (MySQL)
> 3. Schema only (Hana ... who else?)
> 4. No schema or catalog (any DBs like this?)
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Closed] (CAY-2602) Remove RTRIM of char columns in Sybase
[ https://issues.apache.org/jira/browse/CAY-2602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arseni Bulatski closed CAY-2602. Resolution: Fixed > Remove RTRIM of char columns in Sybase > -- > > Key: CAY-2602 > URL: https://issues.apache.org/jira/browse/CAY-2602 > Project: Cayenne > Issue Type: Task > Components: Core Library >Affects Versions: 4.2.M1 >Reporter: Arseni Bulatski >Priority: Major > Fix For: 4.2.M1 > > > Previously, in 4.1 RTRIM wasn't added to column and qualifiers in Sybase. > Since 4.2 RTRIM is added to all char columns in Sybase. > Need to move back same behavior to 4.2. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (CAY-2565) Can't use new generated PK properties with dot() operator
[
https://issues.apache.org/jira/browse/CAY-2565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16900958#comment-16900958
]
Arseni Bulatski commented on CAY-2565:
--
For *4.1* added exception when trying to use PK property with obj path
properties.
https://github.com/apache/cayenne/commit/dc0b6507bb9a29d7f5d0939d1806b404f28d1929
> Can't use new generated PK properties with dot() operator
> -
>
> Key: CAY-2565
> URL: https://issues.apache.org/jira/browse/CAY-2565
> Project: Cayenne
> Issue Type: Bug
> Components: Core Library
>Affects Versions: 4.1.B1
>Reporter: Nikita Timofeev
>Assignee: Nikita Timofeev
>Priority: Major
> Fix For: 4.1.B3, 4.2.M1
>
>
> Per CAY-2478 we can generate properties for PK attributes. But they are
> incompatible with {{dot() }} operator as it is unaware about db paths.
> Simple test case: {code}
> Expression exp = Painting.TO_ARTIST.dot(Artist.ARTIST_ID_PK_PROPERTY).eq(1L);
> {code}
> Will generated following expression: {{toArtist.null = 1}}
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Commented] (CAY-2603) NPE reloading project in the model
[ https://issues.apache.org/jira/browse/CAY-2603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16897983#comment-16897983 ] Arseni Bulatski commented on CAY-2603: -- *4.2 [https://github.com/apache/cayenne/commit/c4d0ddc71b397873f7b32e10fe9c179a3c3da664]* *4.1 [https://github.com/apache/cayenne/commit/3b955fdc3eb2072ccd9861768014b3dbe4ee2dc8]* > NPE reloading project in the model > -- > > Key: CAY-2603 > URL: https://issues.apache.org/jira/browse/CAY-2603 > Project: Cayenne > Issue Type: Bug >Affects Versions: 4.1.B3 > Environment: 4.1.B3-SNAPSHOT, Jul 19 2019 build >Reporter: Andrus Adamchik >Priority: Minor > > 1. I have a project open in the Modeler, class generation view. > 2. From the terminal I did "git checkout -f" to undo my local changes. This > removed one of the new entities > 3. The modeler correctly suggested me to reload the project, which I did. > Result: error dialog with the following exception: > --- > CayenneModeler Info > Version: 4.1.B3-SNAPSHOT > Build Date: Jul 19 2019 11:42:53 > Exception: > = > java.lang.NullPointerException > at > org.apache.cayenne.modeler.editor.cgen.CodeGeneratorControllerBase.getSelectedEntities(CodeGeneratorControllerBase.java:263) > at > org.apache.cayenne.modeler.editor.cgen.CodeGeneratorControllerBase.updateEntities(CodeGeneratorControllerBase.java:405) > at > org.apache.cayenne.modeler.editor.cgen.CodeGeneratorControllerBase.updateSelectedEntities(CodeGeneratorControllerBase.java:392) > at > org.apache.cayenne.modeler.editor.cgen.ClassesTabController.classSelectedAction(ClassesTabController.java:117) > at > org.apache.cayenne.modeler.editor.cgen.CodeGeneratorController.generatorSelectedAction(CodeGeneratorController.java:135) > at > org.apache.cayenne.modeler.editor.cgen.CodeGeneratorController.initBindings(CodeGeneratorController.java:123) > at > org.apache.cayenne.modeler.editor.cgen.CodeGeneratorController.(CodeGeneratorController.java:69) > at > org.apache.cayenne.modeler.editor.DataMapTabbedView.initView(DataMapTabbedView.java:66) > at > org.apache.cayenne.modeler.editor.DataMapTabbedView.(DataMapTabbedView.java:50) > at > org.apache.cayenne.modeler.editor.EditorView.initView(EditorView.java:225) > at > org.apache.cayenne.modeler.editor.EditorView.(EditorView.java:165) > at > org.apache.cayenne.modeler.CayenneModelerController.projectOpenedAction(CayenneModelerController.java:215) > at > org.apache.cayenne.modeler.action.OpenProjectAction.openProjectResourse(OpenProjectAction.java:184) > at > org.apache.cayenne.modeler.action.OpenProjectAction.openProject(OpenProjectAction.java:175) > at > org.apache.cayenne.modeler.ProjectFileChangeTracker$1.run(ProjectFileChangeTracker.java:113) > at > java.desktop/java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:313) > at > java.desktop/java.awt.EventQueue.dispatchEventImpl(EventQueue.java:770) > at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:721) > at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:715) > at java.base/java.security.AccessController.doPrivileged(Native Method) > at > java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:85) > at java.desktop/java.awt.EventQueue.dispatchEvent(EventQueue.java:740) > at > java.desktop/java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:203) > at > java.desktop/java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:124) > at > java.desktop/java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:113) > at > java.desktop/java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:109) > at > java.desktop/java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:101) > at > java.desktop/java.awt.EventDispatchThread.run(EventDispatchThread.java:90) -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (CAY-2602) Remove RTRIM of char columns in Sybase
[ https://issues.apache.org/jira/browse/CAY-2602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16891685#comment-16891685 ] Arseni Bulatski commented on CAY-2602: -- https://github.com/apache/cayenne/commit/942ba5786af9a2ed47be5a1881e390c7d7101250 > Remove RTRIM of char columns in Sybase > -- > > Key: CAY-2602 > URL: https://issues.apache.org/jira/browse/CAY-2602 > Project: Cayenne > Issue Type: Task > Components: Core Library >Affects Versions: 4.2.M1 >Reporter: Arseni Bulatski >Priority: Major > Fix For: 4.2.M1 > > > Previously, in 4.1 RTRIM wasn't added to column and qualifiers in Sybase. > Since 4.2 RTRIM is added to all char columns in Sybase. > Need to move back same behavior to 4.2. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Created] (CAY-2602) Remove RTRIM of char columns in Sybase
Arseni Bulatski created CAY-2602: Summary: Remove RTRIM of char columns in Sybase Key: CAY-2602 URL: https://issues.apache.org/jira/browse/CAY-2602 Project: Cayenne Issue Type: Task Components: Core Library Affects Versions: 4.2.M1 Reporter: Arseni Bulatski Fix For: 4.2.M1 Previously, in 4.1 RTRIM wasn't added to column and qualifiers in Sybase. Since 4.2 RTRIM is added to all char columns in Sybase. Need to move back same behavior to 4.2. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (CAY-2601) Modeler DbImport: result dialog issues
[ https://issues.apache.org/jira/browse/CAY-2601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16890909#comment-16890909 ] Arseni Bulatski commented on CAY-2601: -- *4.1* https://github.com/apache/cayenne/commit/2a51a90187e7660fbd462b464d5f9cc172f5465b > Modeler DbImport: result dialog issues > -- > > Key: CAY-2601 > URL: https://issues.apache.org/jira/browse/CAY-2601 > Project: Cayenne > Issue Type: Bug >Affects Versions: 4.1.B2 >Reporter: Andrus Adamchik >Priority: Minor > > Running db import on 4.1.B3-SNAPSHOT modeler. When the changes are detected, > a dialog listing the changes is shown. There are a few minor issues with this > dialog: > 1. It is not centered against the main Modeler window > 2. It is not resizable, so long table/column names are not visible. > 3. The title is "Reverse Engineering Result". In our new terminology it > should be "Db Import Result" -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (CAY-2601) Modeler DbImport: result dialog issues
[ https://issues.apache.org/jira/browse/CAY-2601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16890897#comment-16890897 ] Arseni Bulatski commented on CAY-2601: -- *4.2* https://github.com/apache/cayenne/commit/788b7004032f17c33b1284a656838de5969f30ff > Modeler DbImport: result dialog issues > -- > > Key: CAY-2601 > URL: https://issues.apache.org/jira/browse/CAY-2601 > Project: Cayenne > Issue Type: Bug >Affects Versions: 4.1.B2 >Reporter: Andrus Adamchik >Priority: Minor > > Running db import on 4.1.B3-SNAPSHOT modeler. When the changes are detected, > a dialog listing the changes is shown. There are a few minor issues with this > dialog: > 1. It is not centered against the main Modeler window > 2. It is not resizable, so long table/column names are not visible. > 3. The title is "Reverse Engineering Result". In our new terminology it > should be "Db Import Result" -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (CAY-2593) Add tableTypes field to dbImport config in dataMap
[ https://issues.apache.org/jira/browse/CAY-2593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1684#comment-1684 ] Arseni Bulatski commented on CAY-2593: -- [~andrus] In previous version if no table types were set, we set default types(TABLE, VIEW). I did it in the same way. User can add anything to this field but if he try to save nothing to this field, default values will be set. Do you mean that we should allow null to this field but later set the default types as we did previously? > Add tableTypes field to dbImport config in dataMap > -- > > Key: CAY-2593 > URL: https://issues.apache.org/jira/browse/CAY-2593 > Project: Cayenne > Issue Type: Improvement > Components: dbimport, Modeler >Affects Versions: 4.1.B2, 4.2.M1 >Reporter: Arseni Bulatski >Assignee: Arseni Bulatski >Priority: Major > Fix For: 4.1.B3, 4.2.M1 > > Attachments: image-2019-07-19-07-55-40-804.png, screenshot-1.png > > > * Add table types to dbImport config in dataMap > * Fix saver and loader for table types > * Add field to Modeler -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (CAY-2593) Add tableTypes field to dbImport config in dataMap
[ https://issues.apache.org/jira/browse/CAY-2593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16888698#comment-16888698 ] Arseni Bulatski commented on CAY-2593: -- And fix for *4.2:* https://github.com/apache/cayenne/commit/bdc5e935b9e0b2c76bdd38e0ec92b75f46e20c9a > Add tableTypes field to dbImport config in dataMap > -- > > Key: CAY-2593 > URL: https://issues.apache.org/jira/browse/CAY-2593 > Project: Cayenne > Issue Type: Improvement > Components: dbimport, Modeler >Affects Versions: 4.1.B2, 4.2.M1 >Reporter: Arseni Bulatski >Assignee: Arseni Bulatski >Priority: Major > Fix For: 4.1.B3, 4.2.M1 > > Attachments: screenshot-1.png > > > * Add table types to dbImport config in dataMap > * Fix saver and loader for table types > * Add field to Modeler -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (CAY-2593) Add tableTypes field to dbImport config in dataMap
[ https://issues.apache.org/jira/browse/CAY-2593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16888691#comment-16888691 ] Arseni Bulatski commented on CAY-2593: -- [~andrus] Add table types filter to refresh db schema action. *4.1:* [https://github.com/apache/cayenne/commit/74ab8d146484deff180f1dae2348c237dd935b33] > Add tableTypes field to dbImport config in dataMap > -- > > Key: CAY-2593 > URL: https://issues.apache.org/jira/browse/CAY-2593 > Project: Cayenne > Issue Type: Improvement > Components: dbimport, Modeler >Affects Versions: 4.1.B2, 4.2.M1 >Reporter: Arseni Bulatski >Assignee: Arseni Bulatski >Priority: Major > Fix For: 4.1.B3, 4.2.M1 > > Attachments: screenshot-1.png > > > * Add table types to dbImport config in dataMap > * Fix saver and loader for table types > * Add field to Modeler -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (CAY-2596) DbImport xml config changes after dbImport plugin task execution
[
https://issues.apache.org/jira/browse/CAY-2596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arseni Bulatski updated CAY-2596:
-
Description:
Execution dbImport plugin with config from dataMap changes schema of dbImport
config in dataMap.
Before dbImport:
{code:java}
test-schema
TestTable
{code}
After dbImport:
{code:java}
test-schema
TestTable
{code}
> DbImport xml config changes after dbImport plugin task execution
>
>
> Key: CAY-2596
> URL: https://issues.apache.org/jira/browse/CAY-2596
> Project: Cayenne
> Issue Type: Bug
> Components: dbimport
>Affects Versions: 4.1.B2, 4.2.M1
>Reporter: Arseni Bulatski
>Assignee: Arseni Bulatski
>Priority: Major
> Fix For: 4.1.B3, 4.2.M1
>
>
> Execution dbImport plugin with config from dataMap changes schema of dbImport
> config in dataMap.
> Before dbImport:
> {code:java}
>
> test-schema
> TestTable
> {code}
> After dbImport:
> {code:java}
>
>
> test-schema
> TestTable
>
> {code}
>
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Commented] (CAY-2596) DbImport xml config changes after dbImport plugin task execution
[ https://issues.apache.org/jira/browse/CAY-2596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16888574#comment-16888574 ] Arseni Bulatski commented on CAY-2596: -- [~andrus] Yes, sure. > DbImport xml config changes after dbImport plugin task execution > > > Key: CAY-2596 > URL: https://issues.apache.org/jira/browse/CAY-2596 > Project: Cayenne > Issue Type: Bug > Components: dbimport >Affects Versions: 4.1.B2, 4.2.M1 >Reporter: Arseni Bulatski >Assignee: Arseni Bulatski >Priority: Major > Fix For: 4.1.B3, 4.2.M1 > > -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Closed] (CAY-2593) Add tableTypes field to dbImport config in dataMap
[ https://issues.apache.org/jira/browse/CAY-2593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arseni Bulatski closed CAY-2593. Resolution: Fixed > Add tableTypes field to dbImport config in dataMap > -- > > Key: CAY-2593 > URL: https://issues.apache.org/jira/browse/CAY-2593 > Project: Cayenne > Issue Type: Improvement > Components: dbimport, Modeler >Affects Versions: 4.1.B2, 4.2.M1 >Reporter: Arseni Bulatski >Assignee: Arseni Bulatski >Priority: Major > Fix For: 4.1.B3, 4.2.M1 > > > * Add table types to dbImport config in dataMap > * Fix saver and loader for table types > * Add field to Modeler -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (CAY-2593) Add tableTypes field to dbImport config in dataMap
[ https://issues.apache.org/jira/browse/CAY-2593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16885167#comment-16885167 ] Arseni Bulatski commented on CAY-2593: -- *4.1* https://github.com/apache/cayenne/commit/d3b37f3d3eb4289a3dc933afb6b2ea438f0ccf7a > Add tableTypes field to dbImport config in dataMap > -- > > Key: CAY-2593 > URL: https://issues.apache.org/jira/browse/CAY-2593 > Project: Cayenne > Issue Type: Improvement > Components: dbimport, Modeler >Affects Versions: 4.1.B2, 4.2.M1 >Reporter: Arseni Bulatski >Assignee: Arseni Bulatski >Priority: Major > Fix For: 4.1.B3, 4.2.M1 > > > * Add table types to dbImport config in dataMap > * Fix saver and loader for table types > * Add field to Modeler -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (CAY-2593) Add tableTypes field to dbImport config in dataMap
[ https://issues.apache.org/jira/browse/CAY-2593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16885158#comment-16885158 ] Arseni Bulatski commented on CAY-2593: -- *4.2* [https://github.com/apache/cayenne/commit/0febc0b058c3934aeee1c382906f0996cdfd6a78] > Add tableTypes field to dbImport config in dataMap > -- > > Key: CAY-2593 > URL: https://issues.apache.org/jira/browse/CAY-2593 > Project: Cayenne > Issue Type: Improvement > Components: dbimport, Modeler >Affects Versions: 4.1.B2, 4.2.M1 >Reporter: Arseni Bulatski >Assignee: Arseni Bulatski >Priority: Major > Fix For: 4.1.B3, 4.2.M1 > > > * Add table types to dbImport config in dataMap > * Fix saver and loader for table types > * Add field to Modeler -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Created] (CAY-2598) Oracle dbImport bug
Arseni Bulatski created CAY-2598: Summary: Oracle dbImport bug Key: CAY-2598 URL: https://issues.apache.org/jira/browse/CAY-2598 Project: Cayenne Issue Type: Bug Components: dbimport, Modeler Affects Versions: 4.2.M1 Reporter: Arseni Bulatski Fix For: 4.2.M1 There are several problems in dbImport from Oracle database. 1. Running dbImport from maven plugin is not responding. Connect is established and then plugin logs nothing. 2. Modeler dbImport also has some problems. * Case when you haven't got catalogs in database but have schemas: modeler try to load all catalogs and shows that there are nothing to import but tables in schemas exist. So the problem is that modeler try to load only catalogs and that's all. * After some changes in code schemas were loaded but when try to load all tables from all schemas bug with the similar behavior to point 1 appeared. DbImport was passed after code modifications to set schema to import. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (CAY-2552) ColumnQuery with flattened attributes bug
[ https://issues.apache.org/jira/browse/CAY-2552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arseni Bulatski updated CAY-2552: - Description: Select entity with flattened attributes in column query. Entry point: EntityRowReader Fields size from segmentMetadata isn't equal to columns list size in RowDescriptor. You can see test case in attachment. This bugs appeared when worked on CAY-2529 Custom expression in DbJoin. Order of attributes was changed and bug with wrong size broke tests. was: Select entity with flattened attributes in column query. Entry point: EntityRowReader Fields size from segmentMetadata isn't equal to columns list size in RowDescriptor. You can see test case in attachment. This bugs appeared when workin on CAY > ColumnQuery with flattened attributes bug > - > > Key: CAY-2552 > URL: https://issues.apache.org/jira/browse/CAY-2552 > Project: Cayenne > Issue Type: Bug > Components: Core Library >Affects Versions: 4.2.M1 >Reporter: Arseni Bulatski >Assignee: Nikita Timofeev >Priority: Major > Fix For: 4.2.M1 > > Attachments: ColumnQuery_with_flattened_attribute_bug.patch > > > Select entity with flattened attributes in column query. > Entry point: EntityRowReader > Fields size from segmentMetadata isn't equal to columns list size in > RowDescriptor. > You can see test case in attachment. > > This bugs appeared when worked on CAY-2529 Custom expression in DbJoin. Order > of attributes was changed and bug with wrong size broke tests. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (CAY-2552) ColumnQuery with flattened attributes bug
[ https://issues.apache.org/jira/browse/CAY-2552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arseni Bulatski updated CAY-2552: - Description: Select entity with flattened attributes in column query. Entry point: EntityRowReader Fields size from segmentMetadata isn't equal to columns list size in RowDescriptor. You can see test case in attachment. This bugs appeared when workin on CAY was: Select entity with flattened attributes in column query. Entry point: EntityRowReader Fields size from segmentMetadata isn't equal to columns list size in RowDescriptor. You can see test case in attachment. > ColumnQuery with flattened attributes bug > - > > Key: CAY-2552 > URL: https://issues.apache.org/jira/browse/CAY-2552 > Project: Cayenne > Issue Type: Bug > Components: Core Library >Affects Versions: 4.2.M1 >Reporter: Arseni Bulatski >Assignee: Nikita Timofeev >Priority: Major > Fix For: 4.2.M1 > > Attachments: ColumnQuery_with_flattened_attribute_bug.patch > > > Select entity with flattened attributes in column query. > Entry point: EntityRowReader > Fields size from segmentMetadata isn't equal to columns list size in > RowDescriptor. > You can see test case in attachment. > > This bugs appeared when workin on CAY -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (CAY-2541) Performing query with expression with ObjectId throws NPE in some cases
[
https://issues.apache.org/jira/browse/CAY-2541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arseni Bulatski updated CAY-2541:
-
Fix Version/s: (was: 4.2.M1)
4.1.B3
> Performing query with expression with ObjectId throws NPE in some cases
> ---
>
> Key: CAY-2541
> URL: https://issues.apache.org/jira/browse/CAY-2541
> Project: Cayenne
> Issue Type: Bug
> Components: Core Library
>Affects Versions: 4.0.2, 4.1.B1
>Reporter: Arseni Bulatski
>Assignee: Arseni Bulatski
>Priority: Major
> Fix For: 4.1.B3
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> NPE when using expression with ObjectId.
> Case:
> ObjectId id = new ObjectId("Artist", "ID", 1);
> ASTDbPath astDbPath = new ASTDbPath("ID");
> ASTScalar astScalar = new ASTScalar(id);
> ASTEqual astEqual = new ASTEqual();
> astEqual.setOperand(0, astDbPath);
> astEqual.setOperand(1, astScalar);
> ObjectSelect.query(Artist.class)
> .where(astEqual)
> .selectFirst(context);
>
> StackTrace:
> java.lang.NullPointerException
> at
> org.apache.cayenne.access.translator.select.QualifierTranslator.appendObjectMatch(QualifierTranslator.java:205)
> at
> org.apache.cayenne.access.translator.select.QualifierTranslator.endNode(QualifierTranslator.java:483)
> at org.apache.cayenne.exp.Expression.traverse(Expression.java:609)
> at org.apache.cayenne.exp.Expression.traverse(Expression.java:581)
> at
> org.apache.cayenne.access.translator.select.QualifierTranslator.doAppendPart(QualifierTranslator.java:120)
> at
> org.apache.cayenne.access.translator.select.QualifierTranslator.doAppendPart(QualifierTranslator.java:87)
> at
> org.apache.cayenne.access.translator.select.QueryAssemblerHelper.appendPart(QueryAssemblerHelper.java:76)
> at
> org.apache.cayenne.access.translator.select.DefaultSelectTranslator.doTranslate(DefaultSelectTranslator.java:152)
> at
> org.apache.cayenne.access.translator.select.QueryAssembler.ensureTranslated(QueryAssembler.java:130)
> at
> org.apache.cayenne.access.translator.select.QueryAssembler.getSql(QueryAssembler.java:121)
> at
> org.apache.cayenne.access.jdbc.SelectAction.performAction(SelectAction.java:91)
> at
> org.apache.cayenne.access.DataNodeQueryAction.runQuery(DataNodeQueryAction.java:97)
> at org.apache.cayenne.access.DataNode.performQueries(DataNode.java:293)
> at
> org.apache.cayenne.access.DataDomainQueryAction.runQuery(DataDomainQueryAction.java:471)
> at
> org.apache.cayenne.access.DataDomainQueryAction.access$000(DataDomainQueryAction.java:72)
> at
> org.apache.cayenne.access.DataDomainQueryAction$2.perform(DataDomainQueryAction.java:446)
> at
> org.apache.cayenne.tx.DefaultTransactionManager.performInTransaction(DefaultTransactionManager.java:87)
> at
> org.apache.cayenne.tx.DefaultTransactionManager.performInTransaction(DefaultTransactionManager.java:51)
> at
> org.apache.cayenne.tx.DefaultTransactionManager.performInTransaction(DefaultTransactionManager.java:40)
> at
> org.apache.cayenne.access.DataDomainQueryAction.runQueryInTransaction(DataDomainQueryAction.java:443)
> at
> org.apache.cayenne.access.DataDomainQueryAction.execute(DataDomainQueryAction.java:122)
> at org.apache.cayenne.access.DataDomain.onQueryNoFilters(DataDomain.java:564)
> at
> org.apache.cayenne.access.DataDomain$DataDomainQueryFilterChain.onQuery(DataDomain.java:748)
> at org.apache.cayenne.tx.TransactionFilter.onQuery(TransactionFilter.java:49)
> at
> org.apache.cayenne.access.DataDomain$DataDomainQueryFilterChain.onQuery(DataDomain.java:748)
> at org.apache.cayenne.access.DataDomain.onQuery(DataDomain.java:556)
> at
> org.apache.cayenne.util.ObjectContextQueryAction.runQuery(ObjectContextQueryAction.java:406)
> at
> org.apache.cayenne.util.ObjectContextQueryAction.executePostCache(ObjectContextQueryAction.java:107)
> at
> org.apache.cayenne.util.ObjectContextQueryAction.execute(ObjectContextQueryAction.java:94)
> at org.apache.cayenne.access.DataContext.onQuery(DataContext.java:965)
> at org.apache.cayenne.access.DataContext.performQuery(DataContext.java:954)
> at org.apache.cayenne.BaseContext.select(BaseContext.java:307)
> at org.apache.cayenne.BaseContext.selectFirst(BaseContext.java:331)
> at org.apache.cayenne.query.ObjectSelect.selectFirst(ObjectSelect.java:660)
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Commented] (CAY-2019) Optimistic locking always fails on CRYPTO columns
[ https://issues.apache.org/jira/browse/CAY-2019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16883652#comment-16883652 ] Arseni Bulatski commented on CAY-2019: -- If the task is complete can anybody of participants close this task? Or this task is still in process. > Optimistic locking always fails on CRYPTO columns > - > > Key: CAY-2019 > URL: https://issues.apache.org/jira/browse/CAY-2019 > Project: Cayenne > Issue Type: Bug > Components: Core Library >Affects Versions: 4.0.M2 >Reporter: John Huss >Assignee: John Huss >Priority: Minor > Fix For: 4.2.M1 > > Time Spent: 1h > Remaining Estimate: 0h > > If you have optimistic locking turned on for columns that are configured to > be encrypted (named CRYPTO_*) then updates to those rows will always fail > because it uses the unencrypted value to check the optimistic locking, ie. > WHERE encryptedColumn = -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (CAY-2593) Add tableTypes field to dbImport config in dataMap
[ https://issues.apache.org/jira/browse/CAY-2593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arseni Bulatski updated CAY-2593: - Description: * Add table types to dbImport config in dataMap * Fix saver and loader for table types * Add field to Modeler > Add tableTypes field to dbImport config in dataMap > -- > > Key: CAY-2593 > URL: https://issues.apache.org/jira/browse/CAY-2593 > Project: Cayenne > Issue Type: Improvement > Components: dbimport, Modeler >Affects Versions: 4.1.B2, 4.2.M1 >Reporter: Arseni Bulatski >Assignee: Arseni Bulatski >Priority: Major > Fix For: 4.1.B3, 4.2.M1 > > > * Add table types to dbImport config in dataMap > * Fix saver and loader for table types > * Add field to Modeler -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (CAY-2593) Add tableTypes field to dbImport config in dataMap
[ https://issues.apache.org/jira/browse/CAY-2593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arseni Bulatski updated CAY-2593: - Component/s: dbimport > Add tableTypes field to dbImport config in dataMap > -- > > Key: CAY-2593 > URL: https://issues.apache.org/jira/browse/CAY-2593 > Project: Cayenne > Issue Type: Improvement > Components: dbimport, Modeler >Affects Versions: 4.1.B2, 4.2.M1 >Reporter: Arseni Bulatski >Assignee: Arseni Bulatski >Priority: Major > Fix For: 4.1.B3, 4.2.M1 > > -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (CAY-2593) Add tableTypes field to dbImport config in dataMap
[ https://issues.apache.org/jira/browse/CAY-2593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arseni Bulatski updated CAY-2593: - Summary: Add tableTypes field to dbImport config in dataMap (was: Modeler: add field to filter table types to dbImport) > Add tableTypes field to dbImport config in dataMap > -- > > Key: CAY-2593 > URL: https://issues.apache.org/jira/browse/CAY-2593 > Project: Cayenne > Issue Type: Improvement > Components: Modeler >Affects Versions: 4.1.B2, 4.2.M1 >Reporter: Arseni Bulatski >Assignee: Arseni Bulatski >Priority: Major > Fix For: 4.1.B3, 4.2.M1 > > -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Closed] (CAY-2596) DbImport xml config changes after dbImport plugin task execution
[ https://issues.apache.org/jira/browse/CAY-2596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arseni Bulatski closed CAY-2596. Resolution: Fixed > DbImport xml config changes after dbImport plugin task execution > > > Key: CAY-2596 > URL: https://issues.apache.org/jira/browse/CAY-2596 > Project: Cayenne > Issue Type: Bug > Components: dbimport >Affects Versions: 4.1.B2, 4.2.M1 >Reporter: Arseni Bulatski >Assignee: Arseni Bulatski >Priority: Major > Fix For: 4.1.B3, 4.2.M1 > > -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (CAY-2596) DbImport xml config changes after dbImport plugin task execution
[ https://issues.apache.org/jira/browse/CAY-2596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16882975#comment-16882975 ] Arseni Bulatski commented on CAY-2596: -- *4.1* https://github.com/apache/cayenne/commit/85ed6850e483b377e51fa4ec5b38606ee51ace1c > DbImport xml config changes after dbImport plugin task execution > > > Key: CAY-2596 > URL: https://issues.apache.org/jira/browse/CAY-2596 > Project: Cayenne > Issue Type: Bug > Components: dbimport >Affects Versions: 4.1.B2, 4.2.M1 >Reporter: Arseni Bulatski >Assignee: Arseni Bulatski >Priority: Major > Fix For: 4.1.B3, 4.2.M1 > > -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (CAY-2596) DbImport xml config changes after dbImport plugin task execution
[ https://issues.apache.org/jira/browse/CAY-2596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16882956#comment-16882956 ] Arseni Bulatski commented on CAY-2596: -- *4.2* https://github.com/apache/cayenne/commit/ea1ed5da1f9b55d9bd25af0e43bc226097b70441 > DbImport xml config changes after dbImport plugin task execution > > > Key: CAY-2596 > URL: https://issues.apache.org/jira/browse/CAY-2596 > Project: Cayenne > Issue Type: Bug > Components: dbimport >Affects Versions: 4.1.B2, 4.2.M1 >Reporter: Arseni Bulatski >Assignee: Arseni Bulatski >Priority: Major > Fix For: 4.1.B3, 4.2.M1 > > -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (CAY-2596) DbImport xml config changes after dbImport plugin task execution
[ https://issues.apache.org/jira/browse/CAY-2596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arseni Bulatski updated CAY-2596: - Summary: DbImport xml config changes after dbImport plugin task execution (was: Use dbImport config from dataMap in plugin's dbImport task) > DbImport xml config changes after dbImport plugin task execution > > > Key: CAY-2596 > URL: https://issues.apache.org/jira/browse/CAY-2596 > Project: Cayenne > Issue Type: Bug > Components: dbimport >Affects Versions: 4.1.B2, 4.2.M1 >Reporter: Arseni Bulatski >Assignee: Arseni Bulatski >Priority: Major > Fix For: 4.1.B3, 4.2.M1 > > > DbImport description changed after run dbImport task from plugin. > -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (CAY-2596) DbImport xml config changes after dbImport plugin task execution
[ https://issues.apache.org/jira/browse/CAY-2596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arseni Bulatski updated CAY-2596: - Description: (was: DbImport description changed after run dbImport task from plugin. ) > DbImport xml config changes after dbImport plugin task execution > > > Key: CAY-2596 > URL: https://issues.apache.org/jira/browse/CAY-2596 > Project: Cayenne > Issue Type: Bug > Components: dbimport >Affects Versions: 4.1.B2, 4.2.M1 >Reporter: Arseni Bulatski >Assignee: Arseni Bulatski >Priority: Major > Fix For: 4.1.B3, 4.2.M1 > > -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (CAY-2596) Use dbImport config from dataMap in plugin's dbImport task
[ https://issues.apache.org/jira/browse/CAY-2596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arseni Bulatski updated CAY-2596: - Fix Version/s: 4.1.B3 > Use dbImport config from dataMap in plugin's dbImport task > -- > > Key: CAY-2596 > URL: https://issues.apache.org/jira/browse/CAY-2596 > Project: Cayenne > Issue Type: Bug > Components: dbimport >Affects Versions: 4.1.B2, 4.2.M1 >Reporter: Arseni Bulatski >Assignee: Arseni Bulatski >Priority: Major > Fix For: 4.1.B3, 4.2.M1 > > > * Need to load dataMap in plugin's task. > * If no dbImport config in pom, use config from dataMap. If there are no > configs, use default. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (CAY-2596) Use dbImport config from dataMap in plugin's dbImport task
[ https://issues.apache.org/jira/browse/CAY-2596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arseni Bulatski updated CAY-2596: - Affects Version/s: 4.1.B2 > Use dbImport config from dataMap in plugin's dbImport task > -- > > Key: CAY-2596 > URL: https://issues.apache.org/jira/browse/CAY-2596 > Project: Cayenne > Issue Type: Bug > Components: dbimport >Affects Versions: 4.1.B2, 4.2.M1 >Reporter: Arseni Bulatski >Assignee: Arseni Bulatski >Priority: Major > Fix For: 4.2.M1 > > > * Need to load dataMap in plugin's task. > * If no dbImport config in pom, use config from dataMap. If there are no > configs, use default. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (CAY-2596) Use dbImport config from dataMap in plugin's dbImport task
[ https://issues.apache.org/jira/browse/CAY-2596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arseni Bulatski updated CAY-2596: - Description: DbImport description changed after run dbImport task from plugin. was: * Need to load dataMap in plugin's task. * If no dbImport config in pom, use config from dataMap. If there are no configs, use default. > Use dbImport config from dataMap in plugin's dbImport task > -- > > Key: CAY-2596 > URL: https://issues.apache.org/jira/browse/CAY-2596 > Project: Cayenne > Issue Type: Bug > Components: dbimport >Affects Versions: 4.1.B2, 4.2.M1 >Reporter: Arseni Bulatski >Assignee: Arseni Bulatski >Priority: Major > Fix For: 4.1.B3, 4.2.M1 > > > DbImport description changed after run dbImport task from plugin. > -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (CAY-2596) Use dbImport config from dataMap in plugin's dbImport task
[ https://issues.apache.org/jira/browse/CAY-2596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arseni Bulatski updated CAY-2596: - Issue Type: Bug (was: Improvement) > Use dbImport config from dataMap in plugin's dbImport task > -- > > Key: CAY-2596 > URL: https://issues.apache.org/jira/browse/CAY-2596 > Project: Cayenne > Issue Type: Bug > Components: dbimport >Affects Versions: 4.2.M1 >Reporter: Arseni Bulatski >Assignee: Arseni Bulatski >Priority: Major > Fix For: 4.2.M1 > > > * Need to load dataMap in plugin's task. > * If no dbImport config in pom, use config from dataMap. If there are no > configs, use default. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Created] (CAY-2596) Use dbImport config from dataMap in plugin's dbImport task
Arseni Bulatski created CAY-2596: Summary: Use dbImport config from dataMap in plugin's dbImport task Key: CAY-2596 URL: https://issues.apache.org/jira/browse/CAY-2596 Project: Cayenne Issue Type: Improvement Components: dbimport Affects Versions: 4.2.M1 Reporter: Arseni Bulatski Assignee: Arseni Bulatski Fix For: 4.2.M1 * Need to load dataMap in plugin's task. * If no dbImport config in pom, use config from dataMap. If there are no configs, use default. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (CAY-2592) Modeler: make all datamaps selected in global cgen tab
[ https://issues.apache.org/jira/browse/CAY-2592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arseni Bulatski closed CAY-2592. Resolution: Fixed > Modeler: make all datamaps selected in global cgen tab > -- > > Key: CAY-2592 > URL: https://issues.apache.org/jira/browse/CAY-2592 > Project: Cayenne > Issue Type: Task > Components: Modeler >Affects Versions: 4.1.B2, 4.2.M1 >Reporter: Arseni Bulatski >Assignee: Arseni Bulatski >Priority: Major > Fix For: 4.1.B3, 4.2.M1 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAY-2592) Modeler: make all datamaps selected in global cgen tab
[ https://issues.apache.org/jira/browse/CAY-2592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16880225#comment-16880225 ] Arseni Bulatski commented on CAY-2592: -- *4.1* https://github.com/apache/cayenne/commit/08b62e04e8030637544be089e8240f616c5f6e0d > Modeler: make all datamaps selected in global cgen tab > -- > > Key: CAY-2592 > URL: https://issues.apache.org/jira/browse/CAY-2592 > Project: Cayenne > Issue Type: Task > Components: Modeler >Affects Versions: 4.1.B2, 4.2.M1 >Reporter: Arseni Bulatski >Assignee: Arseni Bulatski >Priority: Major > Fix For: 4.1.B3, 4.2.M1 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAY-2592) Modeler: make all datamaps selected in global cgen tab
[ https://issues.apache.org/jira/browse/CAY-2592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16880221#comment-16880221 ] Arseni Bulatski commented on CAY-2592: -- *4.2* https://github.com/apache/cayenne/commit/5346def3d1f2b362ea42e81973fcd25fa0f13c28 > Modeler: make all datamaps selected in global cgen tab > -- > > Key: CAY-2592 > URL: https://issues.apache.org/jira/browse/CAY-2592 > Project: Cayenne > Issue Type: Task > Components: Modeler >Affects Versions: 4.1.B2, 4.2.M1 >Reporter: Arseni Bulatski >Assignee: Arseni Bulatski >Priority: Major > Fix For: 4.1.B3, 4.2.M1 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (CAY-2592) Modeler: make all datamaps selected in global cgen tab
[ https://issues.apache.org/jira/browse/CAY-2592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arseni Bulatski updated CAY-2592: - Issue Type: Task (was: Bug) > Modeler: make all datamaps selected in global cgen tab > -- > > Key: CAY-2592 > URL: https://issues.apache.org/jira/browse/CAY-2592 > Project: Cayenne > Issue Type: Task > Components: Modeler >Affects Versions: 4.1.B2, 4.2.M1 >Reporter: Arseni Bulatski >Assignee: Arseni Bulatski >Priority: Major > Fix For: 4.1.B3, 4.2.M1 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (CAY-2591) Modeler: project becomes dirty after click on dbImport or cgen tab
[ https://issues.apache.org/jira/browse/CAY-2591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arseni Bulatski closed CAY-2591. Resolution: Fixed > Modeler: project becomes dirty after click on dbImport or cgen tab > -- > > Key: CAY-2591 > URL: https://issues.apache.org/jira/browse/CAY-2591 > Project: Cayenne > Issue Type: Bug > Components: Modeler >Affects Versions: 4.1.B2, 4.2.M1 >Reporter: Arseni Bulatski >Assignee: Arseni Bulatski >Priority: Major > Fix For: 4.1.B3, 4.2.M1 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAY-2591) Modeler: project becomes dirty after click on dbImport or cgen tab
[ https://issues.apache.org/jira/browse/CAY-2591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16880124#comment-16880124 ] Arseni Bulatski commented on CAY-2591: -- *4.1* https://github.com/apache/cayenne/commit/587a53ea6cfa260e55dca47c6114ecdcb777d08b > Modeler: project becomes dirty after click on dbImport or cgen tab > -- > > Key: CAY-2591 > URL: https://issues.apache.org/jira/browse/CAY-2591 > Project: Cayenne > Issue Type: Bug > Components: Modeler >Affects Versions: 4.1.B2, 4.2.M1 >Reporter: Arseni Bulatski >Assignee: Arseni Bulatski >Priority: Major > Fix For: 4.1.B3, 4.2.M1 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAY-2591) Modeler: project becomes dirty after click on dbImport or cgen tab
[ https://issues.apache.org/jira/browse/CAY-2591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16880122#comment-16880122 ] Arseni Bulatski commented on CAY-2591: -- *4.2* https://github.com/apache/cayenne/commit/df3f1dbb7471e465edfde404fb5af8c8d6a4ff4b > Modeler: project becomes dirty after click on dbImport or cgen tab > -- > > Key: CAY-2591 > URL: https://issues.apache.org/jira/browse/CAY-2591 > Project: Cayenne > Issue Type: Bug > Components: Modeler >Affects Versions: 4.1.B2, 4.2.M1 >Reporter: Arseni Bulatski >Assignee: Arseni Bulatski >Priority: Major > Fix For: 4.1.B3, 4.2.M1 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAY-2586) Char can't be materialized to EnumType in some cases
[ https://issues.apache.org/jira/browse/CAY-2586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16880089#comment-16880089 ] Arseni Bulatski commented on CAY-2586: -- On *4.2* it works fine because of new implementation of SelectTranslator. [https://github.com/apache/cayenne/commit/46ad6bc9e5cb0c66d994dc01ad0f59f67fc788c9] Added test to this case. > Char can't be materialized to EnumType in some cases > > > Key: CAY-2586 > URL: https://issues.apache.org/jira/browse/CAY-2586 > Project: Cayenne > Issue Type: Bug > Components: Core Library >Affects Versions: 4.0.1, 4.1.B2 >Reporter: Arseni Bulatski >Priority: Major > Fix For: 4.0.2, 4.1.B3 > > > Test case: > DbEntity has char attribute with max size. > ObjEntity has enum attribute mapped to char column. > Bug appears when trying to select this entity because no RTRIM was added to > this select. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CAY-2593) Modeler: add field to filter table types to dbImport
Arseni Bulatski created CAY-2593: Summary: Modeler: add field to filter table types to dbImport Key: CAY-2593 URL: https://issues.apache.org/jira/browse/CAY-2593 Project: Cayenne Issue Type: Improvement Components: Modeler Affects Versions: 4.1.B2, 4.2.M1 Reporter: Arseni Bulatski Assignee: Arseni Bulatski Fix For: 4.1.B3, 4.2.M1 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CAY-2592) Modeler: make all datamaps selected in global cgen tab
Arseni Bulatski created CAY-2592: Summary: Modeler: make all datamaps selected in global cgen tab Key: CAY-2592 URL: https://issues.apache.org/jira/browse/CAY-2592 Project: Cayenne Issue Type: Bug Components: Modeler Affects Versions: 4.1.B2, 4.2.M1 Reporter: Arseni Bulatski Assignee: Arseni Bulatski Fix For: 4.1.B3, 4.2.M1 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CAY-2591) Modeler: project becomes dirty after click on dbImport or cgen tab
Arseni Bulatski created CAY-2591: Summary: Modeler: project becomes dirty after click on dbImport or cgen tab Key: CAY-2591 URL: https://issues.apache.org/jira/browse/CAY-2591 Project: Cayenne Issue Type: Bug Components: Modeler Affects Versions: 4.1.B2, 4.2.M1 Reporter: Arseni Bulatski Assignee: Arseni Bulatski Fix For: 4.1.B3, 4.2.M1 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAY-2590) Add method to set query timeout to queries
[ https://issues.apache.org/jira/browse/CAY-2590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16878718#comment-16878718 ] Arseni Bulatski commented on CAY-2590: -- https://github.com/apache/cayenne/commit/731794d5644a681d77e931947b400d997e836987 > Add method to set query timeout to queries > -- > > Key: CAY-2590 > URL: https://issues.apache.org/jira/browse/CAY-2590 > Project: Cayenne > Issue Type: Improvement > Components: Core Library >Reporter: Arseni Bulatski >Assignee: Arseni Bulatski >Priority: Major > Fix For: 4.2.M1 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (CAY-2590) Add method to set query timeout to queries
[ https://issues.apache.org/jira/browse/CAY-2590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arseni Bulatski closed CAY-2590. Resolution: Fixed > Add method to set query timeout to queries > -- > > Key: CAY-2590 > URL: https://issues.apache.org/jira/browse/CAY-2590 > Project: Cayenne > Issue Type: Improvement > Components: Core Library >Reporter: Arseni Bulatski >Assignee: Arseni Bulatski >Priority: Major > Fix For: 4.2.M1 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (CAY-2523) Deprecate SelectQuery
[
https://issues.apache.org/jira/browse/CAY-2523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arseni Bulatski closed CAY-2523.
Resolution: Fixed
> Deprecate SelectQuery
> -
>
> Key: CAY-2523
> URL: https://issues.apache.org/jira/browse/CAY-2523
> Project: Cayenne
> Issue Type: Task
> Components: Core Library
>Reporter: Nikita Timofeev
>Assignee: Nikita Timofeev
>Priority: Major
> Fix For: 4.2.M1
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> After implementing CAY-2522 we can deprecate {{SelectQuery}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (CAY-2523) Deprecate SelectQuery
[
https://issues.apache.org/jira/browse/CAY-2523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16878655#comment-16878655
]
Arseni Bulatski commented on CAY-2523:
--
https://github.com/apache/cayenne/commit/1719ba07db3bd7cacb72963b5c362a543b256f73
> Deprecate SelectQuery
> -
>
> Key: CAY-2523
> URL: https://issues.apache.org/jira/browse/CAY-2523
> Project: Cayenne
> Issue Type: Task
> Components: Core Library
>Reporter: Nikita Timofeev
>Assignee: Nikita Timofeev
>Priority: Major
> Fix For: 4.2.M1
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> After implementing CAY-2522 we can deprecate {{SelectQuery}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (CAY-2539) Import procedures with the help of MergerToken
[ https://issues.apache.org/jira/browse/CAY-2539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16878446#comment-16878446 ] Arseni Bulatski commented on CAY-2539: -- https://github.com/apache/cayenne/commit/e576e343b0c494db1f9d20b0bed4a3f1fd4b8ac8 > Import procedures with the help of MergerToken > -- > > Key: CAY-2539 > URL: https://issues.apache.org/jira/browse/CAY-2539 > Project: Cayenne > Issue Type: Task > Components: dbimport >Affects Versions: 4.2.M1 >Reporter: Arseni Bulatski >Assignee: Arseni Bulatski >Priority: Major > Fix For: 4.2.M1 > > Time Spent: 20m > Remaining Estimate: 0h > > Refactor dbImport. > Import procedures with the help of MergerToken. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (CAY-2539) Import procedures with the help of MergerToken
[ https://issues.apache.org/jira/browse/CAY-2539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arseni Bulatski closed CAY-2539. Resolution: Fixed > Import procedures with the help of MergerToken > -- > > Key: CAY-2539 > URL: https://issues.apache.org/jira/browse/CAY-2539 > Project: Cayenne > Issue Type: Task > Components: dbimport >Affects Versions: 4.2.M1 >Reporter: Arseni Bulatski >Assignee: Arseni Bulatski >Priority: Major > Fix For: 4.2.M1 > > Time Spent: 20m > Remaining Estimate: 0h > > Refactor dbImport. > Import procedures with the help of MergerToken. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (CAY-2590) Add method to set query timeout to queries
[ https://issues.apache.org/jira/browse/CAY-2590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arseni Bulatski updated CAY-2590: - Fix Version/s: 4.2.M1 > Add method to set query timeout to queries > -- > > Key: CAY-2590 > URL: https://issues.apache.org/jira/browse/CAY-2590 > Project: Cayenne > Issue Type: Improvement > Components: Core Library >Affects Versions: 4.2.M1 >Reporter: Arseni Bulatski >Assignee: Arseni Bulatski >Priority: Major > Fix For: 4.2.M1 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (CAY-2590) Add method to set query timeout to queries
[ https://issues.apache.org/jira/browse/CAY-2590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arseni Bulatski updated CAY-2590: - Affects Version/s: (was: 4.2.M1) > Add method to set query timeout to queries > -- > > Key: CAY-2590 > URL: https://issues.apache.org/jira/browse/CAY-2590 > Project: Cayenne > Issue Type: Improvement > Components: Core Library >Reporter: Arseni Bulatski >Assignee: Arseni Bulatski >Priority: Major > Fix For: 4.2.M1 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CAY-2590) Add method to set query timeout to queries
Arseni Bulatski created CAY-2590: Summary: Add method to set query timeout to queries Key: CAY-2590 URL: https://issues.apache.org/jira/browse/CAY-2590 Project: Cayenne Issue Type: Improvement Components: Core Library Affects Versions: 4.2.M1 Reporter: Arseni Bulatski Assignee: Arseni Bulatski -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAY-2585) Rename scalarQuery and params methods in SQLSelect
[ https://issues.apache.org/jira/browse/CAY-2585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16874909#comment-16874909 ] Arseni Bulatski commented on CAY-2585: -- https://github.com/apache/cayenne/commit/8d5f37cf1b73bcb7800dcf81b278b8a77a286201 > Rename scalarQuery and params methods in SQLSelect > -- > > Key: CAY-2585 > URL: https://issues.apache.org/jira/browse/CAY-2585 > Project: Cayenne > Issue Type: Task > Components: Core Library >Reporter: Arseni Bulatski >Assignee: Arseni Bulatski >Priority: Major > Fix For: 4.2.M1 > > Time Spent: 20m > Remaining Estimate: 0h > > Need to deprecate _scalarQuery_ methods with array returned type and add new > methods called _arrayQuery._ > Also deprecate _params_ method and add _param_ method instead. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (CAY-2585) Rename scalarQuery and params methods in SQLSelect
[ https://issues.apache.org/jira/browse/CAY-2585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arseni Bulatski closed CAY-2585. Resolution: Fixed > Rename scalarQuery and params methods in SQLSelect > -- > > Key: CAY-2585 > URL: https://issues.apache.org/jira/browse/CAY-2585 > Project: Cayenne > Issue Type: Task > Components: Core Library >Reporter: Arseni Bulatski >Assignee: Arseni Bulatski >Priority: Major > Fix For: 4.2.M1 > > Time Spent: 20m > Remaining Estimate: 0h > > Need to deprecate _scalarQuery_ methods with array returned type and add new > methods called _arrayQuery._ > Also deprecate _params_ method and add _param_ method instead. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (CAY-2579) Review and possibly relax usage of readonly flag of ObjRelationship
[ https://issues.apache.org/jira/browse/CAY-2579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arseni Bulatski closed CAY-2579. Resolution: Fixed > Review and possibly relax usage of readonly flag of ObjRelationship > --- > > Key: CAY-2579 > URL: https://issues.apache.org/jira/browse/CAY-2579 > Project: Cayenne > Issue Type: Improvement >Reporter: Nikita Timofeev >Assignee: Arseni Bulatski >Priority: Major > Fix For: 4.2.M1 > > > We should review readonly flag after CAY-2571 is done. It is likely that we > can handle some additional cases now. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAY-2579) Review and possibly relax usage of readonly flag of ObjRelationship
[ https://issues.apache.org/jira/browse/CAY-2579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16874880#comment-16874880 ] Arseni Bulatski commented on CAY-2579: -- https://github.com/apache/cayenne/commit/bccd53853cb5903b2c50c7f7aabb547ca40757aa > Review and possibly relax usage of readonly flag of ObjRelationship > --- > > Key: CAY-2579 > URL: https://issues.apache.org/jira/browse/CAY-2579 > Project: Cayenne > Issue Type: Improvement >Reporter: Nikita Timofeev >Priority: Major > Fix For: 4.2.M1 > > > We should review readonly flag after CAY-2571 is done. It is likely that we > can handle some additional cases now. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (CAY-2579) Review and possibly relax usage of readonly flag of ObjRelationship
[ https://issues.apache.org/jira/browse/CAY-2579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arseni Bulatski reassigned CAY-2579: Assignee: Arseni Bulatski > Review and possibly relax usage of readonly flag of ObjRelationship > --- > > Key: CAY-2579 > URL: https://issues.apache.org/jira/browse/CAY-2579 > Project: Cayenne > Issue Type: Improvement >Reporter: Nikita Timofeev >Assignee: Arseni Bulatski >Priority: Major > Fix For: 4.2.M1 > > > We should review readonly flag after CAY-2571 is done. It is likely that we > can handle some additional cases now. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAY-2584) Crypto: can't use ColumnSelect with encrypted columns
[
https://issues.apache.org/jira/browse/CAY-2584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16874011#comment-16874011
]
Arseni Bulatski commented on CAY-2584:
--
*4.2*:
https://github.com/apache/cayenne/commit/7257d0af94c69d669351805f52d287f20dae23dd
> Crypto: can't use ColumnSelect with encrypted columns
> -
>
> Key: CAY-2584
> URL: https://issues.apache.org/jira/browse/CAY-2584
> Project: Cayenne
> Issue Type: Bug
>Affects Versions: 4.0.1, 4.1.B2
>Reporter: Nikita Timofeev
>Assignee: Nikita Timofeev
>Priority: Critical
> Fix For: 4.0.2, 4.1.B3, 4.2.M1
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> {{CryptoRowReaderFactoryDecorator}} is not aware about different row readers
> so it can't read {{ColumnQuery}} result.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (CAY-2584) Crypto: can't use ColumnSelect with encrypted columns
[
https://issues.apache.org/jira/browse/CAY-2584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arseni Bulatski closed CAY-2584.
Resolution: Fixed
> Crypto: can't use ColumnSelect with encrypted columns
> -
>
> Key: CAY-2584
> URL: https://issues.apache.org/jira/browse/CAY-2584
> Project: Cayenne
> Issue Type: Bug
>Affects Versions: 4.0.1, 4.1.B2
>Reporter: Nikita Timofeev
>Assignee: Nikita Timofeev
>Priority: Critical
> Fix For: 4.0.2, 4.1.B3, 4.2.M1
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> {{CryptoRowReaderFactoryDecorator}} is not aware about different row readers
> so it can't read {{ColumnQuery}} result.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (CAY-2402) cdbimport: escape db names that is not valid Java identifiers
[
https://issues.apache.org/jira/browse/CAY-2402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arseni Bulatski closed CAY-2402.
Resolution: Not A Problem
To prevent incorrect generation need to use custom naming strategy in dbImport.
Cgen expects that's data is valid.
If invalid attributes and entities were imported wrong classes are generated.
This is expected behavior.
So the solution is custom ObjectNameGenerator contribution.
> cdbimport: escape db names that is not valid Java identifiers
> -
>
> Key: CAY-2402
> URL: https://issues.apache.org/jira/browse/CAY-2402
> Project: Cayenne
> Issue Type: Bug
> Components: dbimport, Non-GUI Tools
>Affects Versions: 4.0.B2, 4.1.M1
>Reporter: Nikita Timofeev
>Assignee: Arseni Bulatski
>Priority: Minor
> Labels: pull-request-available
> Fix For: 4.2.M1
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Database names starting with numbers are converted as is in Object attribute
> names.
> I.e. name like {{"123name"}} will end as {{}}.
> It can be fixed by prefixing with {{"_"}} such names.
> Also should review other special characters that can be in db names.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (CAY-2402) cdbimport: escape db names that is not valid Java identifiers
[
https://issues.apache.org/jira/browse/CAY-2402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16873348#comment-16873348
]
Arseni Bulatski commented on CAY-2402:
--
To prevent incorrect generation need to use custom naming strategy in dbImport.
Cgen expects that's data is valid.
So the solution is contribution custom ObjectNameGenerator.
> cdbimport: escape db names that is not valid Java identifiers
> -
>
> Key: CAY-2402
> URL: https://issues.apache.org/jira/browse/CAY-2402
> Project: Cayenne
> Issue Type: Bug
> Components: dbimport, Non-GUI Tools
>Affects Versions: 4.0.B2, 4.1.M1
>Reporter: Nikita Timofeev
>Assignee: Arseni Bulatski
>Priority: Minor
> Labels: pull-request-available
> Fix For: 4.2.M1
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Database names starting with numbers are converted as is in Object attribute
> names.
> I.e. name like {{"123name"}} will end as {{}}.
> It can be fixed by prefixing with {{"_"}} such names.
> Also should review other special characters that can be in db names.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (CAY-2588) IdRowReader: ArrayIndexOutOfBoundsException
[
https://issues.apache.org/jira/browse/CAY-2588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1687#comment-1687
]
Arseni Bulatski commented on CAY-2588:
--
Fix:
https://github.com/apache/cayenne/commit/4422aa56a64bbb7a0f4e88d339186b6187a88e89
> IdRowReader: ArrayIndexOutOfBoundsException
> ---
>
> Key: CAY-2588
> URL: https://issues.apache.org/jira/browse/CAY-2588
> Project: Cayenne
> Issue Type: Bug
> Components: Core Library
>Affects Versions: 4.2.M1
>Reporter: Arseni Bulatski
>Assignee: Arseni Bulatski
>Priority: Major
> Fix For: 4.2.M1
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> When trying to execute such query as
> {code:java}
> ObjectSelect.columnQuery(Artist.class,
> PropertyFactory.createSelf(Artist.class),
> PropertyFactory
> .createBase(ExpressionFactory
> .dbPathExp("paintingArray.toArtist.ARTIST_ID"),
> Integer.class))
> .pageSize(1)
> .select(context);
> {code}
> get ArrayIndexOutOfBoundsException.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (CAY-2588) IdRowReader: ArrayIndexOutOfBoundsException
[
https://issues.apache.org/jira/browse/CAY-2588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arseni Bulatski closed CAY-2588.
Resolution: Fixed
> IdRowReader: ArrayIndexOutOfBoundsException
> ---
>
> Key: CAY-2588
> URL: https://issues.apache.org/jira/browse/CAY-2588
> Project: Cayenne
> Issue Type: Bug
> Components: Core Library
>Affects Versions: 4.2.M1
>Reporter: Arseni Bulatski
>Assignee: Arseni Bulatski
>Priority: Major
> Fix For: 4.2.M1
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> When trying to execute such query as
> {code:java}
> ObjectSelect.columnQuery(Artist.class,
> PropertyFactory.createSelf(Artist.class),
> PropertyFactory
> .createBase(ExpressionFactory
> .dbPathExp("paintingArray.toArtist.ARTIST_ID"),
> Integer.class))
> .pageSize(1)
> .select(context);
> {code}
> get ArrayIndexOutOfBoundsException.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (CAY-2460) Newly set value is not saved if cursor is in the edit field
[ https://issues.apache.org/jira/browse/CAY-2460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arseni Bulatski closed CAY-2460. Resolution: Won't Fix Update of fields happens when we remove focus from editable field. If focus stays in field this attribute won't be updated and as a result won't be saved. > Newly set value is not saved if cursor is in the edit field > --- > > Key: CAY-2460 > URL: https://issues.apache.org/jira/browse/CAY-2460 > Project: Cayenne > Issue Type: Bug > Components: Modeler > Environment: OS X >Reporter: Yana >Priority: Trivial > Fix For: 4.2.M1 > > > *Steps:* > It's all throughout the app, for example: > 1. Click to create new DB Entity attribute > 2. Set type first, then edit name (leave cursor in name field) > 3. Click Save > Verify results (e.g in datamap xml) > *Actual result:* name has a default value: untitledAttr > *Expected result:* If the cursor is moved from edited field, changes are > saved successfully. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (CAY-2586) Char can't be materialized to EnumType in some cases
[ https://issues.apache.org/jira/browse/CAY-2586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arseni Bulatski closed CAY-2586. Resolution: Fixed > Char can't be materialized to EnumType in some cases > > > Key: CAY-2586 > URL: https://issues.apache.org/jira/browse/CAY-2586 > Project: Cayenne > Issue Type: Bug > Components: Core Library >Affects Versions: 4.0.1, 4.1.B2 >Reporter: Arseni Bulatski >Priority: Major > Fix For: 4.0.2, 4.1.B3 > > > Test case: > DbEntity has char attribute with max size. > ObjEntity has enum attribute mapped to char column. > Bug appears when trying to select this entity because no RTRIM was added to > this select. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAY-2586) Char can't be materialized to EnumType in some cases
[ https://issues.apache.org/jira/browse/CAY-2586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16873290#comment-16873290 ] Arseni Bulatski commented on CAY-2586: -- *4.0* [https://github.com/apache/cayenne/commit/24d82ad4071b77fcb377927e0fcb013af05ea81e] *4.1* https://github.com/apache/cayenne/commit/f7411f25e70568c5439c86d9a97f30124e2ec955 > Char can't be materialized to EnumType in some cases > > > Key: CAY-2586 > URL: https://issues.apache.org/jira/browse/CAY-2586 > Project: Cayenne > Issue Type: Bug > Components: Core Library >Affects Versions: 4.0.1, 4.1.B2 >Reporter: Arseni Bulatski >Priority: Major > Fix For: 4.0.2, 4.1.B3 > > > Test case: > DbEntity has char attribute with max size. > ObjEntity has enum attribute mapped to char column. > Bug appears when trying to select this entity because no RTRIM was added to > this select. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (CAY-2586) Char can't be materialized to EnumType in some cases
[ https://issues.apache.org/jira/browse/CAY-2586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arseni Bulatski updated CAY-2586: - Description: Test case: DbEntity has char attribute with max size. ObjEntity has enum attribute mapped to char column. Bug appears when trying to select this entity because no RTRIM was added to this select. was: Test case: DbEntity has char attribute with max size. ObjEntity has enum attribute mapped to char column. Bug appears when trying to select this entity because no RTRIM added to this select. > Char can't be materialized to EnumType in some cases > > > Key: CAY-2586 > URL: https://issues.apache.org/jira/browse/CAY-2586 > Project: Cayenne > Issue Type: Bug > Components: Core Library >Affects Versions: 4.0.1, 4.1.B2 >Reporter: Arseni Bulatski >Priority: Major > Fix For: 4.0.2, 4.1.B3 > > > Test case: > DbEntity has char attribute with max size. > ObjEntity has enum attribute mapped to char column. > Bug appears when trying to select this entity because no RTRIM was added to > this select. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CAY-2588) IdRowReader: ArrayIndexOutOfBoundsException
Arseni Bulatski created CAY-2588:
Summary: IdRowReader: ArrayIndexOutOfBoundsException
Key: CAY-2588
URL: https://issues.apache.org/jira/browse/CAY-2588
Project: Cayenne
Issue Type: Bug
Components: Core Library
Affects Versions: 4.2.M1
Reporter: Arseni Bulatski
Assignee: Arseni Bulatski
Fix For: 4.2.M1
When trying to execute such query as
{code:java}
ObjectSelect.columnQuery(Artist.class,
PropertyFactory.createSelf(Artist.class),
PropertyFactory
.createBase(ExpressionFactory
.dbPathExp("paintingArray.toArtist.ARTIST_ID"),
Integer.class))
.pageSize(1)
.select(context);
{code}
get ArrayIndexOutOfBoundsException.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (CAY-2586) Char can't be materialized to EnumType in some cases
Arseni Bulatski created CAY-2586: Summary: Char can't be materialized to EnumType in some cases Key: CAY-2586 URL: https://issues.apache.org/jira/browse/CAY-2586 Project: Cayenne Issue Type: Bug Components: Core Library Affects Versions: 4.1.B2, 4.0.1 Reporter: Arseni Bulatski Fix For: 4.0.2, 4.1.B3 Test case: DbEntity has char attribute with max size. ObjEntity has enum attribute mapped to char column. Bug appears when trying to select this entity because no RTRIM added to this select. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (CAY-2541) Performing query with expression with ObjectId throws NPE in some cases
[
https://issues.apache.org/jira/browse/CAY-2541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arseni Bulatski reassigned CAY-2541:
Assignee: Arseni Bulatski
> Performing query with expression with ObjectId throws NPE in some cases
> ---
>
> Key: CAY-2541
> URL: https://issues.apache.org/jira/browse/CAY-2541
> Project: Cayenne
> Issue Type: Bug
> Components: Core Library
>Affects Versions: 4.0.2, 4.1.B1
>Reporter: Arseni Bulatski
>Assignee: Arseni Bulatski
>Priority: Major
> Fix For: 4.2.M1
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> NPE when using expression with ObjectId.
> Case:
> ObjectId id = new ObjectId("Artist", "ID", 1);
> ASTDbPath astDbPath = new ASTDbPath("ID");
> ASTScalar astScalar = new ASTScalar(id);
> ASTEqual astEqual = new ASTEqual();
> astEqual.setOperand(0, astDbPath);
> astEqual.setOperand(1, astScalar);
> ObjectSelect.query(Artist.class)
> .where(astEqual)
> .selectFirst(context);
>
> StackTrace:
> java.lang.NullPointerException
> at
> org.apache.cayenne.access.translator.select.QualifierTranslator.appendObjectMatch(QualifierTranslator.java:205)
> at
> org.apache.cayenne.access.translator.select.QualifierTranslator.endNode(QualifierTranslator.java:483)
> at org.apache.cayenne.exp.Expression.traverse(Expression.java:609)
> at org.apache.cayenne.exp.Expression.traverse(Expression.java:581)
> at
> org.apache.cayenne.access.translator.select.QualifierTranslator.doAppendPart(QualifierTranslator.java:120)
> at
> org.apache.cayenne.access.translator.select.QualifierTranslator.doAppendPart(QualifierTranslator.java:87)
> at
> org.apache.cayenne.access.translator.select.QueryAssemblerHelper.appendPart(QueryAssemblerHelper.java:76)
> at
> org.apache.cayenne.access.translator.select.DefaultSelectTranslator.doTranslate(DefaultSelectTranslator.java:152)
> at
> org.apache.cayenne.access.translator.select.QueryAssembler.ensureTranslated(QueryAssembler.java:130)
> at
> org.apache.cayenne.access.translator.select.QueryAssembler.getSql(QueryAssembler.java:121)
> at
> org.apache.cayenne.access.jdbc.SelectAction.performAction(SelectAction.java:91)
> at
> org.apache.cayenne.access.DataNodeQueryAction.runQuery(DataNodeQueryAction.java:97)
> at org.apache.cayenne.access.DataNode.performQueries(DataNode.java:293)
> at
> org.apache.cayenne.access.DataDomainQueryAction.runQuery(DataDomainQueryAction.java:471)
> at
> org.apache.cayenne.access.DataDomainQueryAction.access$000(DataDomainQueryAction.java:72)
> at
> org.apache.cayenne.access.DataDomainQueryAction$2.perform(DataDomainQueryAction.java:446)
> at
> org.apache.cayenne.tx.DefaultTransactionManager.performInTransaction(DefaultTransactionManager.java:87)
> at
> org.apache.cayenne.tx.DefaultTransactionManager.performInTransaction(DefaultTransactionManager.java:51)
> at
> org.apache.cayenne.tx.DefaultTransactionManager.performInTransaction(DefaultTransactionManager.java:40)
> at
> org.apache.cayenne.access.DataDomainQueryAction.runQueryInTransaction(DataDomainQueryAction.java:443)
> at
> org.apache.cayenne.access.DataDomainQueryAction.execute(DataDomainQueryAction.java:122)
> at org.apache.cayenne.access.DataDomain.onQueryNoFilters(DataDomain.java:564)
> at
> org.apache.cayenne.access.DataDomain$DataDomainQueryFilterChain.onQuery(DataDomain.java:748)
> at org.apache.cayenne.tx.TransactionFilter.onQuery(TransactionFilter.java:49)
> at
> org.apache.cayenne.access.DataDomain$DataDomainQueryFilterChain.onQuery(DataDomain.java:748)
> at org.apache.cayenne.access.DataDomain.onQuery(DataDomain.java:556)
> at
> org.apache.cayenne.util.ObjectContextQueryAction.runQuery(ObjectContextQueryAction.java:406)
> at
> org.apache.cayenne.util.ObjectContextQueryAction.executePostCache(ObjectContextQueryAction.java:107)
> at
> org.apache.cayenne.util.ObjectContextQueryAction.execute(ObjectContextQueryAction.java:94)
> at org.apache.cayenne.access.DataContext.onQuery(DataContext.java:965)
> at org.apache.cayenne.access.DataContext.performQuery(DataContext.java:954)
> at org.apache.cayenne.BaseContext.select(BaseContext.java:307)
> at org.apache.cayenne.BaseContext.selectFirst(BaseContext.java:331)
> at org.apache.cayenne.query.ObjectSelect.selectFirst(ObjectSelect.java:660)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
