Any particular reason this is in matrix?
On Tue 21 Feb 2012 05:23:11 PM CST, Gail Badner wrote:
> Stacktrace at: http://pastebin.com/Pr2EgwEx
> ___
> hibernate-dev mailing list
> hibernate-dev@lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hi
Stacktrace at: http://pastebin.com/Pr2EgwEx
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
As you know the old code is extremely hard to follow. IIUC there
really is not much of a difference, aside from loader being able to be
callable, whereas subselect cannot. IIUC they both infer a table name
(if not specified explicitly) and generate insert/update/delete
statements. AFAICT th
We discussed this a little in the meeting.
There is another, contradictory "requirement" that the sources
(org.hibernate.metamodel.spi.sources) be able to report back all
logical names. Initially we had decided to try and have sources return
null to indicate that the naming strategy should b
[09:17] Meeting ended Tue Feb 21 15:17:30 2012 UTC. Information
about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)
[09:17] Minutes:
http://transcripts.jboss.org/meeting/irc.freenode.org/hibernate-dev/2012/hibernate-dev.2012-02-21-14.00.html
[09:17] Minutes (text):
http://transcripts
What's the fundamental difference between a loader based entity and a subselect
based entity assuming the entity is read-only. It seems that subselect lets you
define which table it relies on and thus when the entity should be refreshed.
Maybe ti would be worth converging here?
On 20 févr. 2012
