[jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3607) Use schema for model generation, but don't include in @Table

[Dan Allen (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBSEAM-3607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12434998#action_12434998 ] 

Dan Allen commented on JBSEAM-3607:
-----------------------------------

Why can't you just provide the default schema or catalog when it asks you for them in the setup questionnaire. This accomplishes the same task. I'm not sure that Hibernate Tools has the ability to detect the default schema (but I could be wrong). Either way, that wouldn't be a Seam issue, that would be a Hibernate Tools issue.

> Use schema for model generation, but don't include in @Table
> ------------------------------------------------------------
>
>                 Key: JBSEAM-3607
>                 URL: https://jira.jboss.org/jira/browse/JBSEAM-3607
>             Project: Seam
>          Issue Type: Feature Request
>          Components: Tools
>    Affects Versions: 2.1.0.CR1
>         Environment: Database with schemas, DB2 in particular
>            Reporter: Valerie Griffin
>
> I'm building code using "my" development database. I need to tell Hibernate that the schema is "VALERIE" so it will ionly generate code for tables in that schema, but that's not going to be the test or release schema. Therefore, I don't want the schema to be part of the @Table lines. Perhaps there could be a question like "Is this the default schema for the connection?" where a "Yes" answer would not include the schema in the @Table lines while a "No" answer would include it.
> Catalog probably could use a similar feature.

-- 
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