cayenne-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (CAY-1977) Cleanup Modeler reverse engineering functionality
Date Fri, 05 Dec 2014 13:47:12 GMT


ASF GitHub Bot commented on CAY-1977:

GitHub user thinline72 opened a pull request:

    CAY-1977 | Remove "DbEntity Already Exists" dialog

    Now our strategy is to always override DbEntities and ObjEntities.
    Also fixed issue with error dialog.

You can merge this pull request into a Git repository by running:

    $ git pull CAY-1977_1

Alternatively you can review and apply these changes as the patch at:

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #44
commit 0b2acf6ba375930ebb6c184b3a874e8b6fae9d2b
Author: Savva Kolbachev <>
Date:   2014-12-05T13:39:58Z

    CAY-1977 | Remove "DbEntity Already Exists" dialog


> Cleanup Modeler reverse engineering functionality
> -------------------------------------------------
>                 Key: CAY-1977
>                 URL:
>             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

View raw message