Is the call also expensive if there are no SQL warnings (i.e. null is
returned, so no further walking is required)?
It'd be my hope that drivers should be able to fetch the first warning
- if any - upon statement execution without further round-trips. So
getWarnings() would be cheap if no warnings
If that’s effectively widespread, I think indeed we should guard this feature
with an explicit property.
It’s not necessarily easy to anticipate such consequences when designing things.
In insight, something more explicit looks better.
> On 28 Jan 2016, at 06:25, Vlad Mihalcea wrote:
>
> Hi,
>
Hi,
Shouldn't we use the database metadata to know what SQL column type we are
mapping to?
I don't think we should do heuristic determination of types:
Type result = metadata.getTypeResolver().heuristicType( typeName,
typeParameters
);
When Hibernate starts, we could inspect the underlying tabl
I created this JIRA issue for this:
https://hibernate.atlassian.net/browse/HHH-10483
Vlad
On Wed, Jan 27, 2016 at 7:02 PM, Vlad Mihalcea
wrote:
> Then we can add this task as a feature request and see when we have some
> time to add support for it.
>
> Vlad
>
> On Wed, Jan 27, 2016 at 6:54 PM,
Hi,
The guys at Plumbr wrote an article about how MySQL JDBC warnings are
handled by Hibernate:
https://plumbr.eu/blog/io/how-we-accidentally-doubled-our-jdbc-traffic-with-hibernate
I remember seeing this issue on StackOverflow too and I was curious if you
want to tweak it a little bit.
I also a
Hi,
As mentioned in our last discussion, I explored adding Travis support to
Search.
The diff is here:
https://github.com/gsmet/hibernate-search/commit/cbd2c1fff05532974823da572795d53cb8b9d26a
(yes it's short but it was a long road :))
I had to raise a bit the JGroups timeout for one test and ha
Andrea and I discussed on IRC and since we were the only 2 involved and
both agreed, that constitutes a quorum! :)
So I am going to override Oracle12cDialect#contributeTypes (implicit Type
determination) such that:
- recognize byte[] as MaterializedBlobType (Types#BLOB) rather than
BinaryTy
Then we can add this task as a feature request and see when we have some
time to add support for it.
Vlad
On Wed, Jan 27, 2016 at 6:54 PM, Steve Ebersole wrote:
> Just pesky things like resources ;)
>
> On Wed, Jan 27, 2016 at 12:43 AM Vlad Mihalcea
> wrote:
>
>> This must be done like insert
Just pesky things like resources ;)
On Wed, Jan 27, 2016 at 12:43 AM Vlad Mihalcea
wrote:
> This must be done like insert but in reverse order. With inserts, we need
> to add parents first and children after, because of the foreign key
> constraints.
> For delete, we need to group children first
Hi,
It's my pleasure to announce the release of Hibernate Validator
5.2.3.Final. This fixes several bugs, most notably it allows to use HV
on Java 9. Check out the announcement for the details [1].
Cheers,
--Gunnar
[1]
http://in.relation.to/2016/01/27/friends-with-java-9-hibernate-validator-52
10 matches
Mail list logo
