I think it is closely related (if not the same) to this one:
https://hibernate.atlassian.net/browse/HHH-9788
2015-05-15 5:20 GMT+03:00 Steve Ebersole :
> Actually that cannot be it. JPA does not define schema update capability.
> On May 14, 2015 4:27 PM, "Steve Ebersole" wrote:
>
>> So you're
Actually that cannot be it. JPA does not define schema update capability.
On May 14, 2015 4:27 PM, "Steve Ebersole" wrote:
> So you're original test was using JPA? See this illustrates why it's best
> to isolate tests down to SSCCE.
>
> I will try again with JPA specifically.
> On May 14, 2015
So you're original test was using JPA? See this illustrates why it's best
to isolate tests down to SSCCE.
I will try again with JPA specifically.
On May 14, 2015 11:30 AM, "Petar Tahchiev" wrote:
> Hi Steve,
>
> your test indeed works fine - I logged here
> https://jira.spring.io/browse/SPR-116
Hi Steve,
your test indeed works fine - I logged here
https://jira.spring.io/browse/SPR-11694 so that the spring guys will have a
look, but I don't think spring is doing any magic on the foreign keys.
Juergen Hoeller from spring proposed it might be a bug in Hibernate's
EntityManager implementatio
No word on the new test case I take it?
WRT the HHH72 logged warnings, like i said the warning is inocuous.
But I did correct it: https://hibernate.atlassian.net/browse/HHH-9797
On Wed, May 13, 2015 at 3:52 PM, Steve Ebersole wrote:
> Nope. Well, specifically yes your test fails as is. Bu
Nope. Well, specifically yes your test fails as is. But since you did not
simplify your environment, I took that opportunity and simplified it. So I
sent you a PR that adds a new test using your model and successfully
running an schema update. The only difference is that my test does not
have a
Any luck on reproducing this?
2015-05-05 16:17 GMT+03:00 Steve Ebersole :
> Petar, I have just been focusing on other things the past 3 days or so.
> Chill :)
>
> I will look at this this week. If you happen to have a chance to debug it
> any further by then, that would rock. FWIW, I do not thi
Petar, I have just been focusing on other things the past 3 days or so.
Chill :)
I will look at this this week. If you happen to have a chance to debug it
any further by then, that would rock. FWIW, I do not think it is in any
way related to the duplicate secondary table warnings. Those are
com
Any of you have seen this issue? Shall I open a ticket?
2015-05-04 0:03 GMT+03:00 Petar Tahchiev :
> Hi guys,
>
> I finally managed to reproduce it - here's a small application that will
> generate the provided exception:
>
> https://github.com/paranoiabla/hibernate-hsql-issue
>
> Please notice t
Hi guys,
I finally managed to reproduce it - here's a small application that will
generate the provided exception:
https://github.com/paranoiabla/hibernate-hsql-issue
Please notice that it works fine with Hibernate 4.3.x I think it has to do
something with the CommerceCustomerModel - If I remov
Hi guys,
I just tried hibernate 5.0 beta2 and here's my observations. First of all
the foreign key problems I had before seems to be resolved, however I see
the following error when executing tests with HSQL:
Caused by: org.springframework.beans.factory.BeanCreationException: Error
creating bean
11 matches
Mail list logo
