I don't think it can be SpatialValue as the annotations:
- marks the property describing the spatial coordinates
- describes how the data will be indexed wrt spatial indexing (strategy + fine
tuning)
- describes the usual boost, etc properties
It's the sister of @Field but @SpatialField is wrong
On Jun 4, 2012, at 4:51 PM, Emmanuel Bernard wrote:
> I don't think it can be SpatialValue as the annotations:
>
> - marks the property describing the spatial coordinates
> - describes how the data will be indexed wrt spatial indexing (strategy +
> fine tuning)
> - describes the usual boost, et
Steve,
Thanks for the feedback.
Is this a correct summary:
* Introduce the "{alias}" placeholder, as in Restrictions.sqlRestriction.
* Introduce another optional @Filter element, "entity", which
developers could use instead of the proposed "table" element.
Thanks,
Rob.
On Fri, Jun 1, 2012 at 1
Hi,
I have a mysql master/slave setup which works fine with jdbc datasource.
All inserts goes to the master and all queries goes to the slaves.
I try to access mysql master/slaves using hibernate/spring configuration.
I use org.springframework.orm.hibernate3.HibernateTransactionManager
transacti
1) I think adding support for {alias} is a more general issue. Its
applicable to many other pieces of mapping metadata (@Formula, etc).
More I was responding to David's comment there. I totally think it
makes sense to support this in all of those cases. I guess the vote
point there is wheth
Hi,
Would it be possible to apply the pull request
https://github.com/hibernate/hibernate-orm/pull/335 mentioned previously?
Thanks Chris
-Original Message-
From: Chris Pheby
Sent: 10 May 2012 10:29
To: 'Steve Ebersole'
Cc: hibernate-dev@lists.jboss.org
Subject: RE: [hibernate-dev] Pro
On 4 juin 2012, at 17:03, Hardy Ferentschik wrote:
>
> On Jun 4, 2012, at 4:51 PM, Emmanuel Bernard wrote:
>
>> I don't think it can be SpatialValue as the annotations:
>>
>> - marks the property describing the spatial coordinates
>> - describes how the data will be indexed wrt spatial indexin
Not sure. Need to think about that one some more.
The problem there is that Components have their mapping information
resolved differently from all other types. Its a long standing problem
in Hibernate that causes all kinds of issues.
On Mon 04 Jun 2012 11:17:44 AM CDT, Chris Pheby wrote:
> H
On Fri 01 Jun 2012 07:21:32 AM CDT, Strong Liu wrote:
> when using connection pool or datasource, there is not a way to set
> the connection level settings for each query, is it?
Sure you can. Psuedo-code:
dialect.setLockTimeout( theConnection );
try {
executeTheStatement();
}
finally {
