DatabaseMetaData question
by Steve Ebersole
Anyone know if there is a (standard JDBC) way to know if the names
returned in the various result sets from DatabaseMetaData are quoted names?
For example, DatabaseMetaData.getTables(...) returns a ResultSet that
includes, amongst other stuff, catalog name, schema name and table name.
But I need to know if those names are quoted.
Do I just have to leverage the DatabaseMetaData values like:
storesMixedCaseQuotedIdentifiers
storesLowerCaseQuotedIdentifiers
storesUpperCaseQuotedIdentifiers
storesUpperCaseIdentifiers
storesLowerCaseIdentifiers
and use them to decipher the incoming text based on case? Is that
really the only/best option? Or am I missing something?
--
steve(a)hibernate.org
http://hibernate.org
12 years, 9 months
Re: [hibernate-dev] Problem with Infinispan 5.1.5 with Hibernate version 3.6.10.
by Steve Ebersole
And yet again...
On Fri 27 Jul 2012 11:01:07 AM CDT, Steve Ebersole wrote:
> No, we only maintain a "latest to latest" integration. Maintaining
> every possible combo would be way too big of a challenge for a small
> open source team.
>
> But, all the needed code does exist in Git. You'd want to start with
> the hibernate-infinispan module from the 3.6 branch and selectively
> apply patches from 4.0/4.1 branch to integrate Infinispan 5.1. This
> might mean cherry-picking or just plain merging.
>
>
> On Fri 27 Jul 2012 10:35:16 AM CDT, thomas fuller wrote:
>> Hi Steven,
>>
>> Thanks for your reply.
>>
>> Re: "The Infinispan implementation of the Hibernate RegionFactory SPI
>> is actually done in the org.hibernate:hibernate-infinispan module, not
>> in Infinispan itself unless something drastic has changed there."
>>
>> I agree with this, I think my message was poorly worded perhaps.
>>
>> Let me ask this question:
>>
>> Is there a hibernate-infinispan module that will work with Infinispan
>> 5+ (5.1.5 specifically) and Hibernate 3.6 (3.6.10, specifically)?
>>
>> If this exists, would you happen to know which version I should be
>> using?
>>
>> Thanks,
>>
>> Tom
>>
>> On Fri, Jul 27, 2012 at 4:02 PM, Steve Ebersole
>> <steven.ebersole(a)gmail.com <mailto:steven.ebersole@gmail.com>> wrote:
>>
>> The Infinispan implementation of the Hibernate RegionFactory SPI
>> is actually done in the org.hibernate:hibernate-__infinispan
>> module, not in Infinispan itself unless something drastic has
>> changed there.
>>
>> You would seem to have something else wrong in your setup.
>>
>>
>>
>> On Fri 27 Jul 2012 05:05:05 AM CDT, thomas fuller wrote:
>>
>> Hi Folks,
>>
>> I am using Infinispan 5.1.5 on Grails 2.1.0, which ships with
>> Hibernate
>> 3.6.10.
>>
>> The problem I am having is that the exception below indicates
>> that an
>> attempt is being made to load
>> org/hibernate/cache/spi/__RegionFactory, which
>> is included in Hibernate 4.0.0, whereas Grails 2.1.0 ships
>> with Hibernate
>> version 3.6.10 which includes the class
>> org.hibernate.cache.__RegionFactory.
>>
>> Is there a way to configure Infinispan such that it can work
>> with Hibernate
>> version 3.6.10?
>>
>> If the answer is "no", I suspect the reason would be that the
>> custom
>> InfinispanRegionFactory has not been written. Can you let me
>> know if you
>> are aware of anyone currently writing this, because if nobody
>> is, I'll
>> write it myself.
>>
>> Thanks for your help,
>>
>> Tom
>>
>> org.springframework.beans.__factory.BeanCreationException:
>> Error creating
>> bean with name 'transactionManager': Cannot resolve reference
>> to bean
>> 'sessionFactory' while setting bean property 'sessionFactory';
>> nested
>> exception is
>> org.springframework.beans.__factory.BeanCreationException: Error
>> creating bean with name 'sessionFactory': Invocation of init
>> method failed;
>> nested exception is java.lang.__NoClassDefFoundError:
>> org/hibernate/cache/spi/__RegionFactory
>> at
>>
>> java.util.concurrent.__FutureTask$Sync.innerRun(__FutureTask.java:303)
>> at
>> java.util.concurrent.__FutureTask.run(FutureTask.__java:138)
>> at
>>
>> java.util.concurrent.__ThreadPoolExecutor$Worker.__runTask(ThreadPoolExecutor.__java:886)
>>
>> at
>>
>> java.util.concurrent.__ThreadPoolExecutor$Worker.run(__ThreadPoolExecutor.java:908)
>>
>> at java.lang.Thread.run(Thread.__java:662)
>> _________________________________________________
>> hibernate-dev mailing list
>> hibernate-dev(a)lists.jboss.org
>> <mailto:hibernate-dev@lists.jboss.org>
>> https://lists.jboss.org/__mailman/listinfo/hibernate-dev
>> <https://lists.jboss.org/mailman/listinfo/hibernate-dev>
>>
>>
--
steve(a)hibernate.org
http://hibernate.org
12 years, 9 months
Re: [hibernate-dev] Problem with Infinispan 5.1.5 with Hibernate version 3.6.10.
by thomas fuller
Hi Stephen,
That's what I thought.
I may end up needing to write this. If I do, is this something that could
be contributed to the Hibernate-Infinispan module? I ask because, while the
audience for this may be somewhat limited, it could prove to be helpful
nonetheless.
Thanks for your help,
Tom
On Fri, Jul 27, 2012 at 5:01 PM, Steve Ebersole
<steven.ebersole(a)gmail.com>wrote:
> No, we only maintain a "latest to latest" integration. Maintaining every
> possible combo would be way too big of a challenge for a small open source
> team.
>
> But, all the needed code does exist in Git. You'd want to start with the
> hibernate-infinispan module from the 3.6 branch and selectively apply
> patches from 4.0/4.1 branch to integrate Infinispan 5.1. This might mean
> cherry-picking or just plain merging.
>
>
>
> On Fri 27 Jul 2012 10:35:16 AM CDT, thomas fuller wrote:
>
>> Hi Steven,
>>
>> Thanks for your reply.
>>
>> Re: "The Infinispan implementation of the Hibernate RegionFactory SPI
>> is actually done in the org.hibernate:hibernate-**infinispan module, not
>> in Infinispan itself unless something drastic has changed there."
>>
>> I agree with this, I think my message was poorly worded perhaps.
>>
>> Let me ask this question:
>>
>> Is there a hibernate-infinispan module that will work with Infinispan
>> 5+ (5.1.5 specifically) and Hibernate 3.6 (3.6.10, specifically)?
>>
>> If this exists, would you happen to know which version I should be using?
>>
>> Thanks,
>>
>> Tom
>>
>> On Fri, Jul 27, 2012 at 4:02 PM, Steve Ebersole
>> <steven.ebersole(a)gmail.com <mailto:steven.ebersole@gmail.**com<steven.ebersole(a)gmail.com>>>
>> wrote:
>>
>> The Infinispan implementation of the Hibernate RegionFactory SPI
>> is actually done in the org.hibernate:hibernate-__**infinispan
>>
>> module, not in Infinispan itself unless something drastic has
>> changed there.
>>
>> You would seem to have something else wrong in your setup.
>>
>>
>>
>> On Fri 27 Jul 2012 05:05:05 AM CDT, thomas fuller wrote:
>>
>> Hi Folks,
>>
>> I am using Infinispan 5.1.5 on Grails 2.1.0, which ships with
>> Hibernate
>> 3.6.10.
>>
>> The problem I am having is that the exception below indicates
>> that an
>> attempt is being made to load
>> org/hibernate/cache/spi/__**RegionFactory, which
>>
>> is included in Hibernate 4.0.0, whereas Grails 2.1.0 ships
>> with Hibernate
>> version 3.6.10 which includes the class
>> org.hibernate.cache.__**RegionFactory.
>>
>>
>> Is there a way to configure Infinispan such that it can work
>> with Hibernate
>> version 3.6.10?
>>
>> If the answer is "no", I suspect the reason would be that the
>> custom
>> InfinispanRegionFactory has not been written. Can you let me
>> know if you
>> are aware of anyone currently writing this, because if nobody
>> is, I'll
>> write it myself.
>>
>> Thanks for your help,
>>
>> Tom
>>
>> org.springframework.beans.__**factory.BeanCreationException:
>>
>> Error creating
>> bean with name 'transactionManager': Cannot resolve reference
>> to bean
>> 'sessionFactory' while setting bean property 'sessionFactory';
>> nested
>> exception is
>> org.springframework.beans.__**factory.BeanCreationException:
>> Error
>>
>> creating bean with name 'sessionFactory': Invocation of init
>> method failed;
>> nested exception is java.lang.__**NoClassDefFoundError:
>> org/hibernate/cache/spi/__**RegionFactory
>> at
>> java.util.concurrent.__**FutureTask$Sync.innerRun(__**
>> FutureTask.java:303)
>> at
>> java.util.concurrent.__**FutureTask.run(FutureTask.__**java:138)
>> at
>> java.util.concurrent.__**ThreadPoolExecutor$Worker.__**
>> runTask(ThreadPoolExecutor.__**java:886)
>> at
>> java.util.concurrent.__**ThreadPoolExecutor$Worker.run(**
>> __ThreadPoolExecutor.java:908)
>> at java.lang.Thread.run(Thread.__**java:662)
>> ______________________________**___________________
>> hibernate-dev mailing list
>> hibernate-dev(a)lists.jboss.org
>> <mailto:hibernate-dev@lists.**jboss.org<hibernate-dev(a)lists.jboss.org>
>> >
>> https://lists.jboss.org/__**mailman/listinfo/hibernate-dev<https://lists.jboss.org/__mailman/listinfo/hibernate-dev>
>> <https://lists.jboss.org/**mailman/listinfo/hibernate-dev<https://lists.jboss.org/mailman/listinfo/hibernate-dev>
>> **>
>>
>>
>>
12 years, 9 months
Fwd: Re: schema export question
by Steve Ebersole
---------- Forwarded message ----------
From: "Steve Ebersole" <steven.ebersole(a)gmail.com>
Date: Jul 27, 2012 7:25 AM
Subject: Re: [hibernate-dev] schema export question
To: "Hardy Ferentschik" <hardy(a)hibernate.org>
This is all changing as we had discussed the other day. If for now you
want to change Exporter to be public for what you need, go for it. However
as for setter keep in mind there are actually multiple export ers in play.
We can discuss the state of the changes so far locally on my machine if you
want. But I don't understand why you need to supply new exporter. Why
aren't you just changing the "relational model" (adding check constraints,
etc) for the exports to pick up?
And no, that should be using System.out. Its output it sent to stdout
specifically for purposes of command line piping/redirection.
On Jul 27, 2012 5:35 AM, "Hardy Ferentschik" <hardy(a)hibernate.org> wrote:
> Hi,
>
> I am trying to write some tests related to schema constraints application
> in conjunction with Bean Validation.
> In this context I came across org.hibernate.tool.hbm2ddl.Exporter which is
> atm a package visible interface.
> I was wondering whether it would make sense to make is a public interface
> and add a setter to SchemaExport in
> order to provide a custom exporter. This way I could get hold of the
> created sql and use it in my tests.
>
> On a side note, org.hibernate.tool.hbm2ddl.ScriptExporter uses System.out.
> Should it not use the logger instead?
>
> Thoughts?
>
> --Hardy
> _______________________________________________
> hibernate-dev mailing list
> hibernate-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hibernate-dev
>
12 years, 9 months
Re: [hibernate-dev] Problem with Infinispan 5.1.5 with Hibernate version 3.6.10.
by Steve Ebersole
I really dislike Thunderbird sometimes...
Sorry recently its been seemingly randomly deciding to send my emails
from different "profiles". Which is very annoying when it decides to
send it as accounts that do not have access to post to lists I am
responding to! Ugh.
Anyway, here is the response from my "proper" account...
On 07/27/2012 10:02 AM, Steve Ebersole wrote:
> The Infinispan implementation of the Hibernate RegionFactory SPI is
> actually done in the org.hibernate:hibernate-infinispan module, not in
> Infinispan itself unless something drastic has changed there.
>
> You would seem to have something else wrong in your setup.
>
>
> On Fri 27 Jul 2012 05:05:05 AM CDT, thomas fuller wrote:
>> Hi Folks,
>>
>> I am using Infinispan 5.1.5 on Grails 2.1.0, which ships with Hibernate
>> 3.6.10.
>>
>> The problem I am having is that the exception below indicates that an
>> attempt is being made to load org/hibernate/cache/spi/RegionFactory,
>> which
>> is included in Hibernate 4.0.0, whereas Grails 2.1.0 ships with Hibernate
>> version 3.6.10 which includes the class
>> org.hibernate.cache.RegionFactory.
>>
>> Is there a way to configure Infinispan such that it can work with
>> Hibernate
>> version 3.6.10?
>>
>> If the answer is "no", I suspect the reason would be that the custom
>> InfinispanRegionFactory has not been written. Can you let me know if you
>> are aware of anyone currently writing this, because if nobody is, I'll
>> write it myself.
>>
>> Thanks for your help,
>>
>> Tom
>>
>> org.springframework.beans.factory.BeanCreationException: Error creating
>> bean with name 'transactionManager': Cannot resolve reference to bean
>> 'sessionFactory' while setting bean property 'sessionFactory'; nested
>> exception is org.springframework.beans.factory.BeanCreationException:
>> Error
>> creating bean with name 'sessionFactory': Invocation of init method
>> failed;
>> nested exception is java.lang.NoClassDefFoundError:
>> org/hibernate/cache/spi/RegionFactory
>> at
>> java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
>> at java.util.concurrent.FutureTask.run(FutureTask.java:138)
>> at
>> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
>>
>> at
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
>>
>> at java.lang.Thread.run(Thread.java:662)
>> _______________________________________________
>> hibernate-dev mailing list
>> hibernate-dev(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/hibernate-dev
--
steve(a)hibernate.org
http://hibernate.org
12 years, 9 months
Re: [hibernate-dev] Problem with Infinispan 5.1.5 with Hibernate version 3.6.10.
by thomas fuller
Hi Steven,
Thanks for your reply.
Re: "The Infinispan implementation of the Hibernate RegionFactory SPI is
actually done in the org.hibernate:hibernate-infinispan module, not in
Infinispan itself unless something drastic has changed there."
I agree with this, I think my message was poorly worded perhaps.
Let me ask this question:
Is there a hibernate-infinispan module that will work with Infinispan 5+
(5.1.5 specifically) and Hibernate 3.6 (3.6.10, specifically)?
If this exists, would you happen to know which version I should be using?
Thanks,
Tom
On Fri, Jul 27, 2012 at 4:02 PM, Steve Ebersole
<steven.ebersole(a)gmail.com>wrote:
> The Infinispan implementation of the Hibernate RegionFactory SPI is
> actually done in the org.hibernate:hibernate-**infinispan module, not in
> Infinispan itself unless something drastic has changed there.
>
> You would seem to have something else wrong in your setup.
>
>
>
> On Fri 27 Jul 2012 05:05:05 AM CDT, thomas fuller wrote:
>
>> Hi Folks,
>>
>> I am using Infinispan 5.1.5 on Grails 2.1.0, which ships with Hibernate
>> 3.6.10.
>>
>> The problem I am having is that the exception below indicates that an
>> attempt is being made to load org/hibernate/cache/spi/**RegionFactory,
>> which
>> is included in Hibernate 4.0.0, whereas Grails 2.1.0 ships with Hibernate
>> version 3.6.10 which includes the class org.hibernate.cache.**
>> RegionFactory.
>>
>> Is there a way to configure Infinispan such that it can work with
>> Hibernate
>> version 3.6.10?
>>
>> If the answer is "no", I suspect the reason would be that the custom
>> InfinispanRegionFactory has not been written. Can you let me know if you
>> are aware of anyone currently writing this, because if nobody is, I'll
>> write it myself.
>>
>> Thanks for your help,
>>
>> Tom
>>
>> org.springframework.beans.**factory.BeanCreationException: Error creating
>> bean with name 'transactionManager': Cannot resolve reference to bean
>> 'sessionFactory' while setting bean property 'sessionFactory'; nested
>> exception is org.springframework.beans.**factory.BeanCreationException:
>> Error
>> creating bean with name 'sessionFactory': Invocation of init method
>> failed;
>> nested exception is java.lang.**NoClassDefFoundError:
>> org/hibernate/cache/spi/**RegionFactory
>> at java.util.concurrent.**FutureTask$Sync.innerRun(**
>> FutureTask.java:303)
>> at java.util.concurrent.**FutureTask.run(FutureTask.**java:138)
>> at
>> java.util.concurrent.**ThreadPoolExecutor$Worker.**
>> runTask(ThreadPoolExecutor.**java:886)
>> at
>> java.util.concurrent.**ThreadPoolExecutor$Worker.run(**
>> ThreadPoolExecutor.java:908)
>> at java.lang.Thread.run(Thread.**java:662)
>> ______________________________**_________________
>> hibernate-dev mailing list
>> hibernate-dev(a)lists.jboss.org
>> https://lists.jboss.org/**mailman/listinfo/hibernate-dev<https://lists.jboss.org/mailman/listinfo/hibernate-dev>
>>
>
12 years, 9 months
schema export question
by Hardy Ferentschik
Hi,
I am trying to write some tests related to schema constraints application in conjunction with Bean Validation.
In this context I came across org.hibernate.tool.hbm2ddl.Exporter which is atm a package visible interface.
I was wondering whether it would make sense to make is a public interface and add a setter to SchemaExport in
order to provide a custom exporter. This way I could get hold of the created sql and use it in my tests.
On a side note, org.hibernate.tool.hbm2ddl.ScriptExporter uses System.out. Should it not use the logger instead?
Thoughts?
--Hardy
12 years, 9 months
Problem with Infinispan 5.1.5 with Hibernate version 3.6.10.
by thomas fuller
Hi Folks,
I am using Infinispan 5.1.5 on Grails 2.1.0, which ships with Hibernate
3.6.10.
The problem I am having is that the exception below indicates that an
attempt is being made to load org/hibernate/cache/spi/RegionFactory, which
is included in Hibernate 4.0.0, whereas Grails 2.1.0 ships with Hibernate
version 3.6.10 which includes the class org.hibernate.cache.RegionFactory.
Is there a way to configure Infinispan such that it can work with Hibernate
version 3.6.10?
If the answer is "no", I suspect the reason would be that the custom
InfinispanRegionFactory has not been written. Can you let me know if you
are aware of anyone currently writing this, because if nobody is, I'll
write it myself.
Thanks for your help,
Tom
org.springframework.beans.factory.BeanCreationException: Error creating
bean with name 'transactionManager': Cannot resolve reference to bean
'sessionFactory' while setting bean property 'sessionFactory'; nested
exception is org.springframework.beans.factory.BeanCreationException: Error
creating bean with name 'sessionFactory': Invocation of init method failed;
nested exception is java.lang.NoClassDefFoundError:
org/hibernate/cache/spi/RegionFactory
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
12 years, 9 months
Cache issue
by Christian Beikov
Hello!
I think I found a bug in hibernate, but I am not sure if it really is a
bug or expected behavior.
I made a Jira Task: https://hibernate.onjira.com/browse/HHH-7465
Any thoughts?
--
Mit freundlichen Grüßen,
------------------------------------------------------------------------
*Christian Beikov*
12 years, 9 months
Test failures when entity name is mapped
by Gail Badner
I'm seeing 2 test failures using the new metamodel for tests that were passing in commit 787ab27d459a385411d3bf6ae0adfb9682898aa1.
The tests are:
org.hibernate.test.entityname.EntityNameFromSubClassTest
org.hibernate.test.iterate.IterateTest
Both of these tests are mapped using hbm.xml with the entity name specified. For EntityNameFromSubClassTest, the mapping is:
<class name="Vehicle" abstract="true" entity-name="VEHICLE" ...>
The exception is:
Caused by: org.hibernate.MappingException: Unknown entity: org.hibernate.test.entityname.Vehicle
Anyone know of a change in the last couple of days that would cause this?
Thanks,
Gail
12 years, 9 months
