[jbosstools-issues] [JBoss JIRA] Updated: (JBIDE-5703) Hibernate Reverse Engineering Editor should show multiple catalogs/schemas from a MySQL database

[Max Rydahl Andersen (JIRA)]

     [ https://jira.jboss.org/jira/browse/JBIDE-5703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Max Rydahl Andersen updated JBIDE-5703:
---------------------------------------

    Fix Version/s: 3.2.next


Do you have some sample schema(s) to test this on ? screenshots ? 

My understanding is that the jdbc url in mysql control what you got access to.

> Hibernate Reverse Engineering Editor should show multiple catalogs/schemas from a MySQL database
> ------------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-5703
>                 URL: https://jira.jboss.org/jira/browse/JBIDE-5703
>             Project: Tools (JBoss Tools)
>          Issue Type: Feature Request
>          Components: Hibernate
>    Affects Versions: 3.1.0.CR1
>            Reporter: Pieter Hartog
>            Priority: Minor
>             Fix For: 3.2.next
>
>
> MySQL is funny with catalogs and schemas. It doesn't support schemas like most other databases do. It's just called 'databases'.
> When you try to create a reveng.xml file using the Hibernate Reverse Engineering Editor, you can't get multiple databases / schemas to show up.
>  It looks like the wizard looks at the hibernate.connection.url property in the hibernate-console.properties file. However, when I leave out the name of the database (e.g.   jdbc:mysql://localhost:3306) without the database, the wizard does not return any tables.
> When you leave out the default database (i.e. schema) name in the connection.url, you should see all databases/ schemas for that one connection.
> When a user selects multiple schemas, the resulting reveng.xml file should have one <schema-selection ...> element for each schema the user wants to map tables from. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira