You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cayenne.apache.org by "Arseni Bulatski (Jira)" <ji...@apache.org> on 2019/08/26 14:48:00 UTC

[jira] [Commented] (CAY-2598) Oracle dbImport bug

    [ https://issues.apache.org/jira/browse/CAY-2598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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)