[jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3607) Use schema for model generation, but don't include in @Table
[
https://jira.jboss.org/jira/browse/JBSEAM-3607?page=com.atlassian.jira.pl...
]
Valerie Griffin commented on JBSEAM-3607:
-----------------------------------------
When I provide the schema in the setup, it becomes part of the @Table line in the files
as:
@Table(name = "STD_GROUP_PERMS", schema = "VALERIE")
If I don't provide the schema, it pulls in tables from all schemas it can get to.
What I want is to limit the schema used for table searches to VALERIE (in this case) but
for the @Table line to appear as:
@Table(name = "STD_GROUP_PERMS")
The user name and URL used to connect specify the schema which is used as the default for
associated connections.
I do recognize that a lot of what seam-gen does is appropriately connected to capabilities
provided by Hibernate.
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