You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cayenne.apache.org by "Savva Kolbachev (JIRA)" <ji...@apache.org> on 2016/01/20 14:36:40 UTC

[jira] [Closed] (CAY-1977) Cleanup Modeler reverse engineering functionality

     [ https://issues.apache.org/jira/browse/CAY-1977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Savva Kolbachev closed CAY-1977.
--------------------------------
    Resolution: Fixed

> Cleanup Modeler reverse engineering functionality
> -------------------------------------------------
>
>                 Key: CAY-1977
>                 URL: https://issues.apache.org/jira/browse/CAY-1977
>             Project: Cayenne
>          Issue Type: Bug
>    Affects Versions: 4.0.M2
>            Reporter: Andrus Adamchik
>            Assignee: Andrus Adamchik
>         Attachments: error-post-reveng.png
>
>
> With the new DB import functionality added in the backend, we'll need to align Modeler UI related to reverse engineering (Tools > Reengineer Database Schema).
> 1. Add catalog selector to the "Reengineer Database Schema: Select Options" dialog. Just like with schema selector, it should be hidden if no catalogs are found for a given db
> 2. New style of table / procedure name matching (instead of "%" use regex.. this is what the backend understands)
> 3. Reverse engineering progress dialog is not updated when the process is looking for columns, primary and foreign keys.
> 4. "DbEntity Already Exists" dialog should be removed as well as  the code handling overrides in the Modeler, as we no longer care about override/no override selection - our strategy is to always merge.
> 5. An odd error dialog appears at the end of repeat reverse engineering. Doesn't seem to affect the process, still there's probably an exception somewhere (see screenshot).
> This list is not extensive and we'll likely have follow up Jiras.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)