[
https://issues.apache.org/jira/browse/CAY-1977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14235408#comment-14235408
]
ASF GitHub Bot commented on CAY-1977:
-------------------------------------
GitHub user thinline72 opened a pull request:
https://github.com/apache/cayenne/pull/43
CAY-1977 | Add catalog selector
1. Add catalog selector to the "Reengineer Database Schema: Select Options"
dialog.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/thinline72/cayenne CAY-1977
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/cayenne/pull/43.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #43
----
commit 20c3e9449b732e2af834227d5456358cbbcdea3a
Author: Savva Kolbachev <s.kolbac...@gmail.com>
Date: 2014-12-05T11:49:23Z
CAY-1977 | Add catalog selector to the "Reengineer Database Schema: Select
Options" dialog
----
> 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)
