Some of the issues I've found with JPA 2.1 and the overall new stored procedure
APIs:
1. StoredProcedureQuery#hasMoreResults() returns true if the next result is an
update count, it should return false, according to API documentation. On MySQL,
if a SP returns a single or multiple ResultSets,
On 01.08.2013, at 19:01, Steve Ebersole steven.ebers...@gmail.com wrote:
2. If there is only one ResultSet returned by the SP, I should be able to
call StoredProcedureQuery#getResultList() without first calling
hasMoreResults(). This maps to JDBC CallableStatement#excuteQuery().
Like I
Testing the latest scanner changes. Still trying to configure an explicit
persistence unit, where only the listed annotated classes (and listed
package-info) are included, everything else should be ignored.
The PackageInfoArchiveEntryHandler will always add package names to
DeploymentResources
Trying to upgrade to 4.3-SNAPSHOT, the
EntityManagerFactoryBuilderImpl.indexResource() is failing for my
persistence.xml configuration in Java SE with
Persistence.createEntityManagerFactory():
persistence-unit name=SimplePU
jta-data-sourcemyDS/jta-data-source
On 18.03.2013, at 17:09, Steve Ebersole st...@hibernate.org wrote:
Out of curiosity, where is this documented as being supported?
http://docs.jboss.org/hibernate/entitymanager/3.6/reference/en/html/configuration.html
The class element specifies a fully qualified class name that you will map.
I've noticed some cases where a native Hibernate exception is not wrapped in a
javax.persistence.OptimisticLockException.
EntityVerifyVersionProcess.java throws an org.hibernate.OptimisticLockException
that is passed on directly to JPA users.
EntityIncrementVersionProcess.java passes through
On Feb 7, 2012, at 16:05 , Scott Marlow wrote:
The use case for duplicate EntityManagerFactory, would be the application
that is depending on the persistence unit name that may or may not be
unique across multiple application deployments.
Or many integration test environments. Test setups
See Button.java in the tests. The @NotNull on the embeddables property is
checked at runtime but doesn't affect DDL, there's no NOT NULL constraint
generated. Is that by design - component nullability etc. - or missing?
___
hibernate-dev mailing list
Debugging a BLOB issue on H2 (different issue than this) led me to try Derby,
which fails even earlier.
This is the same test as org.hibernate.ejb.test.lob.BlobTest, if someone could
run this on Derby, you should see the exception. I've copied the test 1:1 into
my environment and had the same
On Nov 23, 2011, at 11:34 , Sanne Grinovero wrote:
log.debugf vs log.debug
log.tracef vs log.trace
This also seems to be the difference between these messages with JUL:
[main] TRACE - 11:27:51,428 - org.hibernate.loader.Loader:
While you guys are at it, I think you should add the Maven or rather
non-Eclipse tools for Hibernate to your TODO list. All of that needs cleanup
and unification.
On Oct 6, 2011, at 19:05 , Strong Liu wrote:
I'm in the middle of moving hibernate tools to use hibernate4
but there are too many
On Jul 2, 2007, at 4:58 PM, Brian Stansberry wrote:
FYI, there are a bunch of EJB3 clustered entity test failures in AS
trunk due to a bad interaction between Hibernate 3.2.4.SP1 and
JBoss Cache 2.0.0. Basically, this is a temporary mismatch between
Hibernate and JBC. There's work in
On Jul 3, 2007, at 11:57 PM, Brian Stansberry wrote:
I added a version of the above to http://wiki.jboss.org/wiki/
Wiki.jsp?page=JBossCacheHibernateAlignment. As mentioned there, a
bunch of us will be meeting the week of July 23 to deal with these
issues. We'll update the wiki after those
On Feb 19, 2007, at 3:32 PM, Michael Barker wrote:
However I have noticed that everytime distinct is specifed in the
ejb-ql query it also gets specified in the sql query. I am
curious as the reasoning behind this.
You are wondering why a DISTINCT you put into your query is actually
On Feb 16, 2007, at 6:29 PM, Horan, Jeff wrote:
Then it works. So it is not following Java accessor standards of
mixed case method names.
FAQ. Go to the forum next time.
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
On Nov 24, 2006, at 7:43 PM, Arthur Orange wrote:
Ok the page http://www.hibernate.org/hib_docs/tools/reference/en/
html/setup.html
lists such scant docs on how to install hibernate tools that its
worthless really.
I went to tools.hibernate.org and that didn't work either.
Read up
On Nov 8, 2006, at 4:49 PM, Emmanuel Bernard wrote:
Can we get rid of those files, people get confused and they are
outdated.
Not if the Ant clowns still bundle the plugin JARs in their
distribution in the default classpath.
___
hibernate-dev
On Oct 31, 2006, at 6:35 PM, Vikas Phonsa wrote:
I'm a newbie to hibernate 3 (haven't worked with older versions)
and am trying to understand the difference between the get() and
the load() methods of the Hibernate Session Object.
http://forum.hibernate.org/
Guys, be nice to people who don't read the mailing list page. Alexis
is watching.
Begin forwarded message:
From: Alexis Pigeon [EMAIL PROTECTED]
Date: October 31, 2006 7:01:01 PM GMT+01:00
To: Christian Bauer [EMAIL PROTECTED]
Subject: Re: [hibernate-dev] Session get() and load()
Hi
The Hibernate developer team released Hibernate 3.2.0 GA today, this
release is now ready for production use. Please read the migration
guidelines if you are upgrading from an earlier version.
In addition to Hibernate Core, final releases of the Java Persistence
provider are now available
On Sep 28, 2006, at 8:51 PM, Emmanuel Bernard wrote:
@Filter (pointing to the target table)
@FilterJoinTable (pointing to the association table)
I like 2. better, it is more consistent esp when you realize that
@OneToMany can use a join table just by changing an annotation.
2. would require
On Sep 27, 2006, at 6:43 PM, Emmanuel Bernard wrote:
This is consistent with the way saveOrUpdate works
And it's perfectly reasonable behavior. If I modify a field value,
then merge, then take the instance returned by merge, I expect that
the value is still there in the merged result.
22 matches
Mail list logo
