Re: [hibernate-dev] HHH-9548 - stored procedures and null parameter values

I agree that it looks quite strange, especially considering the existing API. I believe that, if JPA falls short on specifying something, we should rather cover that in the Hibernate-specific API. Vlad On Tue, Feb 9, 2016 at 1:06 AM, Steve Ebersole wrote: > I have heard no

Re: [hibernate-dev] Entity-joins (HHH-16 and HHH-7321)

Hi. It's fine to assume that implicit joins and entity-joins don't mix and document this behavior. When using explicit joins: select f.id, c.name, f.postDate, u.username from FinancialRecord f inner join f.customer c left join User u on f.lastUpdateBy = u.username We get

[hibernate-dev] Batch version data support in Dialect

Hi, While browsing the PRs on GitHub, I stumbled on this issue: https://hibernate.atlassian.net/browse/HHH-10290 In the current implementation, the hibernate.jdbc.batch_versioned_data property is set to true and we override it at Dialect-level as follows: public Oracle12cDialect() {

Re: [hibernate-dev] HHH-10478 : OperationContext

This is going to have to wait post-5.1 as I mentioned earlier if this was not ready prior to last week. I have just too much on my plate to look at this over 2 days. On Mon, Feb 8, 2016 at 12:29 AM Gail Badner wrote: > The POC [1] assumes that we only need a single

Re: [hibernate-dev] Entity-joins (HHH-16 and HHH-7321)

On 8 February 2016 at 17:44, Steve Ebersole wrote: > I am working mainly on HHH-16 which requests adding support for > entity-joins (aka "ad hoc" joins). > > So long-story-short, there is a simple solution with some limitations and > then a more correct solution that

[hibernate-dev] Entity-joins (HHH-16 and HHH-7321)

I am working mainly on HHH-16 which requests adding support for entity-joins (aka "ad hoc" joins). So long-story-short, there is a simple solution with some limitations and then a more correct solution that unfortunately requires a lot of rework in the HQL parser. The crux of the problem is

Re: [hibernate-dev] HHH-9548 - stored procedures and null parameter values

I have heard no feedback, especially in regards to my last comment on the Jira. So at this point I plan on simply not supporting that atm from the JPA APIs. Longer term I think the correct solution is to expose the underlying Hibernate parameter object and users can directly set it. Handling