+1
- Original Message -
> From: "Strong Liu"
> To: "Steve Ebersole"
> Cc: "Hibernate hibernate-dev"
> Sent: Thursday, August 9, 2012 9:15:32 PM
> Subject: Re: [hibernate-dev] SchemaManagementTool / Exportable
>
>
> +1
>
> On Aug 10, 2012, at 12:38 AM, Steve Ebersole
> wrote:
>
> >
AFAIK, joined inheritance and one-to-one are not implemented.
- Original Message -
> From: "Hardy Ferentschik"
> To: "Steve Ebersole"
> Cc: "Gail Badner" , "Hibernate hibernate-dev"
>
> Sent: Thursday, August 9, 2012 12:04:37 PM
> Subject: Re: [hibernate-dev] Test success may not mean
seeing this failure on our CI a lot, anyone know how to workaround it?
org.hibernate.test.annotations.xml.ejb3.OrmVersion1SupportedTest.testOrm1Support
Failing for the past 1 build (Since #14 )
Took 30 min.
edit description
Error Message
java.lang.Exception: test timed out after 180 millis
+1
On Aug 10, 2012, at 12:38 AM, Steve Ebersole wrote:
> The basics of org.hibernate.service.schema.spi.SchemaManagementTool are
> essentially done. There is a lot of clean up I want to do after
> Configuration is gutted or removed, changing how SchemaExport, etc work
> internally.
>
> But
On 9 Jan 2012, at 8:32 PM, Steve Ebersole wrote:
> OK, I added adding FK between joined inheritance tables but
> org.hibernate.test.annotations.genericsinheritance.GenericsInheritanceTest
> still fails. AFAICT the problem there is that joined inheritance is
> considered the default if no inhe
OK, I added adding FK between joined inheritance tables but
org.hibernate.test.annotations.genericsinheritance.GenericsInheritanceTest
still fails. AFAICT the problem there is that joined inheritance is
considered the default if no inheritance type is specified (at least
based on the old DDL o
Lots of people are doing this with 4.0 and Integrator. In fact some of
those discussions helping people led directly to this new SPI. That and
wanting to allow pluggable schema management tools since we well
advertise ours as "not meant for production"
But, all that said, thats not really rele
+1 for the externalization. We actually have a custom schema-export tool
for hibernate 4.1 that plugs in with how we configure data sources in
spring much better than the provided tool.
-Eric
On 08/09/2012 11:38 AM, Steve Ebersole wrote:
> The basics of org.hibernate.service.schema.spi.SchemaMa
The basics of org.hibernate.service.schema.spi.SchemaManagementTool are
essentially done. There is a lot of clean up I want to do after
Configuration is gutted or removed, changing how SchemaExport, etc work
internally.
But one thing I wanted to discuss was to change up how Exportable works.
I hooked in using the new schema management tool code to handle schema
create/drop processing. These particular FKs are still not being
created. So I looked at the tests a little closer. The issue there is
that code building the bindings are not always creating Database
objects. Specifically
Yes this is exactly what I meant.
By renaming, what I mean is that a user could very well rename the jar
file themselves and things would generally continue to work because
java is based on classloading and the names of jars are irrelevant to
classloading (other than feeding class path).
I als
11 matches
Mail list logo
