[
https://jira.jboss.org/jira/browse/JBIDE-3842?page=com.atlassian.jira.plu...
]
Vitali Yemialyanchyk commented on JBIDE-3842:
---------------------------------------------
3) here I'm hesitate - we need to discuss this:
is @GeneratedValue @Id annotations enough to create db column which doesn't accept
null value?
4) my argument here - 255 is to long value.
the user case:
a) to create DB structure I create several java classes
b) then I use "Generate Hibernate/JPA annotations" to anotate all these
classes;
c) then I want to create DB tables from annotated classes
if I get all columns length 255 it is BIG ENOUGH to store almost all user input,
but it is TOO BIG for all data (login, first name, last name, password, etc)
so the default case can't satisfy this, so I should add
@Column(length = N) for login (first name, last name, password, etc) column by the hands -
we can generate this to avoid such manual updates.
Additional annotations support for "Generate Hibernate/JPA
annotations"
-----------------------------------------------------------------------
Key: JBIDE-3842
URL:
https://jira.jboss.org/jira/browse/JBIDE-3842
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: Hibernate
Affects Versions: 3.0.0.CR2
Reporter: Vitali Yemialyanchyk
Assignee: Vitali Yemialyanchyk
Priority: Minor
Fix For: LATER
currently I see the sence add @MappedSuperclass annotation for base class instead of or
together with @Entity annotation;
in case when the class has offsprings - there is a big sence to have @MappedSuperclass
annotation by default.
Some other ideas?
--
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