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, at 19:09, Steve Ebersole wrote: > for the "completeness" argument, the corollary to those others is actually > loader, which is the ability to name a query to use for loading an > entity/collection. > > > On Mon 20 Feb 2012 12:57:36 PM CST, Emmanuel Bernard wrote: >> I find the second reason important. In some organizations, the idea of >> developers owning a schema especially on legacy database is harder than >> climbing the Himalaya bare foot. >> Having access to the subselect views helps. >> >> I also like it for completeness since we can override insert / update / >> delete statements. >> >> On 20 févr. 2012, at 18:52, Steve Ebersole wrote: >> >>> subselects are a feature that was originally put in place to support >>> databases without view support and/or application developers which did >>> not have access to create views on their target database. >>> >>> I am contemplating whether we want to continue to support this. >>> >>> At this time I all real databases out there support views. Anyone know >>> of any that do not? >>> >>> I am not inclined to leave the feature in place just for the second >>> reason. They could always define the view in a schema in which they do >>> have access to create views. >>> >>> Thoughts? >>> >>> -- >>> st...@hibernate.org >>> http://hibernate.org >>> _______________________________________________ >>> hibernate-dev mailing list >>> hibernate-dev@lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/hibernate-dev >> > > -- > st...@hibernate.org > http://hibernate.org _______________________________________________ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
