Not really,
You were mixing 2 different strategies, 1 for hbm and one for
annotations which was by side effect possible, but very bad.
I've merged the 2. ImprovedNS always had the semantic (2).
Pablo Nussembaum wrote:
I don't understand why 2 is unrelated, this version broke the backward
compatibility.
Until now if I use the xml configuration or annotations, hibernate
generates the same db schema with this change this not true any more.
Pablo Nussembaum
Emmanuel Bernard wrote:
2) is unrelated. You were not able to work with custom NS in
annotations before, you should consider writing an extension of
EJB3NamingStrategy instead.
Pablo Nussembaum wrote:
I'm complaining :-P
today I was trying to update from hibernate-3.1-rc2 y
annotation-3.1-b6.
I found 2 problems (I'm the ImprovedNamingStrategy):
1. The one your describing
2. Some JoinTables change the generated name.
Example:
@Entity
@org.hibernate.annotations.Entity(mutable=false)
@Table(name = "menu_item")
public class MenuItem extends BusinessObject {
private MenuItem parent;
private List<MenuItem> children;
... others methods ...
@OneToMany(cascade = {CascadeType.ALL}
@IndexColumn(name = "menu_position", base=1) public
List<MenuItem> getChildren() {
return children;
}
}
with revision rc2 the join table's name was "menu_item_menu_item"
and with the 3.1-release is "menu_item_children".
I prefer the old behavior.
--
Pablo Nussembaum
Gavin King wrote:
Well, let's see if anyone complains...
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Emmanuel Bernard
Sent: Tuesday, December 20, 2005 7:06 AM
To: Hibernate development
Subject: [Hibernate] ImprovedNamingStrategy
When working on the new naming strategy, I've broken the use of
ImprovedNamingStrategy.
now
<component name="editStatus" class="com.csg.pmnet.model.EditStatus">
<property name="editPid" column='edit_pid'/> leads to
/edit_status_edit_pid/ instead of /edit_pid.
/Should I fix that for the sake of backward compatibility, or is it
OK?/
/
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log
files for problems? Stop! Download the new AJAX search engine that
makes searching your log files as easy as surfing the web. DOWNLOAD
SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
hibernate-devel mailing list
hibernate-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hibernate-devel
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through
log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD
SPLUNK!
http://ads.osdn.com/?ad_idv37&alloc_id865&op=click
_______________________________________________
hibernate-devel mailing list
hibernate-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hibernate-devel
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
hibernate-devel mailing list
hibernate-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hibernate-devel
