I'm not sure it's a bug but that is definitely is worth a few thoughts.
The way we implement embeddable names using the dot strategy is via a
custom naming strategy. But when you use an explicit column name, we
simply discard that and pass the real column name.
We probably can improve the naming strategy to do what you are proposing
Tug but what if I want to change the embeddable prefix to something
else? There would be no way to do it.
I'm not sure of the right course of action. Can you open a JIRA to
capture this problem.
Emmanuel
On Sun 2012-10-07 13:59, Tugdual Grall wrote:
Hi,
I am developing a new Datastore for Couchbase and have a issue/question
with the Embeddable support. Since I am new to OGM I prefer to ask the
question to the expert before login an issue. (and did not find this issue
in JIRA)
For my example I am using the model described in the Embeddable test:
https://github.com/hibernate/hibernate-ogm/tree/master/hibernate-ogm-core...
During the process of creating a new Account, with an Address OGM is
calling the updateTuple, and when the Embeddable tupe has a custom column
name.
In the Address entity I see the following code:
...
@Column(name = "postal_code")
public String getZipCode() { return zipCode; }
....
The updateTuple() method received the following columnName:
postal_code
Where it should be something like:
homeAddress.postal_code
This is what happens when the column is not renamed: homeAddress.zipCode
Could you please confirm that it is a bug? (or what I am doing wrong)
PS: I have started to dive into the code to find the source of the issue...
will continue as soon as I have the green light to enter a JIRA.
Tug the newbie
_______________________________________________
hibernate-dev mailing list
hibernate-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev