« Return to Thread: [scala] JPA question
Re: [scala] JPA question
by John Nilsson
::
Rate this Message:
Hi,
I think the showSql property has been deprecated in favor of log4j loggers.
If you set the log4j level to TRACE for org.hibernate you'll get
everything Hibernate has to say about what it is doing. Can't remember
which one it is, but I know one of the loggers will give you the
values used in queries at the TRACE level.
BR,
John
On Tue, Jun 16, 2009 at 2:18 AM, Balthazar
Crowley<balthazar.crowley@...> wrote:
> Derek,
> The show_sql property was on, it turns out, but the sql statement doesn't
> display the values for the inserts. What's weirder is that JoinColumn +
> OneToOne annotations are causing the generated DDL to specify the type as
> tinyblob instead of the type of the id field. So, it really is attempting to
> serialize the element contained instead of the foreign key.
> Regards,
> Balthazar
>
> On Sun, Jun 14, 2009 at 6:23 AM, Derek Chen-Becker <java@...>
> wrote:
>>
>> Balthazar Crowley wrote:
>> > Derek,
>> >
>> > Thanks for the tip about the hibernate.show_sql property. The column
>> > it's complaining about is not the Id column, but the column that should
>> > be inferred as a relation. It's a field that represents a OneToOne
>> > composition relation. It looks like -- instead of just using the Id of
>> > the thing contained it's using the serialization of the object.
>>
>> Right, well, what I meant was that for the other side of the one-to-one
>> the @Id is a String uuid, which is what really should be stored as the
>> foreign key. If you're truly getting a serialized version of the object
>> then that really seems like a Hibernate bug.
>>
>> Derek
>
>
>
> --
> Balthazar Crowley
> Resident Magician
> DSLver.com
>
I think the showSql property has been deprecated in favor of log4j loggers.
If you set the log4j level to TRACE for org.hibernate you'll get
everything Hibernate has to say about what it is doing. Can't remember
which one it is, but I know one of the loggers will give you the
values used in queries at the TRACE level.
BR,
John
On Tue, Jun 16, 2009 at 2:18 AM, Balthazar
Crowley<balthazar.crowley@...> wrote:
> Derek,
> The show_sql property was on, it turns out, but the sql statement doesn't
> display the values for the inserts. What's weirder is that JoinColumn +
> OneToOne annotations are causing the generated DDL to specify the type as
> tinyblob instead of the type of the id field. So, it really is attempting to
> serialize the element contained instead of the foreign key.
> Regards,
> Balthazar
>
> On Sun, Jun 14, 2009 at 6:23 AM, Derek Chen-Becker <java@...>
> wrote:
>>
>> Balthazar Crowley wrote:
>> > Derek,
>> >
>> > Thanks for the tip about the hibernate.show_sql property. The column
>> > it's complaining about is not the Id column, but the column that should
>> > be inferred as a relation. It's a field that represents a OneToOne
>> > composition relation. It looks like -- instead of just using the Id of
>> > the thing contained it's using the serialization of the object.
>>
>> Right, well, what I meant was that for the other side of the one-to-one
>> the @Id is a String uuid, which is what really should be stored as the
>> foreign key. If you're truly getting a serialized version of the object
>> then that really seems like a Hibernate bug.
>>
>> Derek
>
>
>
> --
> Balthazar Crowley
> Resident Magician
> DSLver.com
>
« Return to Thread: [scala] JPA question
| Free embeddable forum powered by Nabble | Forum Help |
