I imagine the DB name + version will be provided by the user somehow.
We could also have Hibernate build a DatabaseMetadata implementation returning
the data provided by the user.
That would avoid changing the contract. The main drawback is that
DatabaseMetadata has many more methods
we would not
Let's split the problem in two
## Infinispan
In the ORM case we do filter null results. The logic is in
`QueryLoader.executeLoader` and more precisely
`ObjectLoaderHelper.returnAlreadyLoadedObjectsInCorrectOrder`.
So it looks like a mistake of the Infinipsan Query module to not reproduce this
b
Correct. The current proposal has them passed in as settings.
Yes, we could "mock" DatabaseMetadata, but there is a lot there
including access to the Connection from which the DatabaseMetadata was
supposedly retrieved.
On Thu 30 Aug 2012 02:31:56 AM CDT, Emmanuel Bernard wrote:
> I imagine the
Just a heads up to check the changes on master in how
JtaPlatformInitiator works now.
On Thu 09 Aug 2012 09:10:18 AM CDT, Steve Ebersole wrote:
> 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 general
I assume no responses means everyone is ok with this change. Hopefully I
will start on those changes next week; for certain I would like to get it
done before the meeting
On Aug 23, 2012 8:28 AM, "Steve Ebersole" wrote:
> The initial design I had for building a SessionFactory using the new
> met
