Using the String value could be a good idea also for double,
not very clean but safe.
2009/3/5 Emmanuel Bernard :
> I mean we could but we would need to rely on the string representation
>
> @interface Max {
> String value()
> }
>
> @Max("12.5")
> double someNumber;
>
>
> On Mar 4, 2009, at 19:1
On Wed, Mar 4, 2009 at 4:20 PM, Emmanuel Bernard wrote:
> I mean we could but we would need to rely on the string representation
>
> @interface Max {
> String value()
> }
>
> @Max("12.5")
> double someNumber;
There's very few domains where you want to be validating user input
and storing it as
On Thu, 05 Mar 2009 10:30:49 +0100, Elias Ross
wrote:
@Max("12.5")
BigDecimal someNumber;
Since the BigDecimal and BigInteger have String constructors that are
well defined, a String representation seems fine.
The string representation is probably less intuative though, especially
for i
http://opensource.atlassian.com/projects/hibernate/browse/HHH-3225
Steve, any chance you could look at this one, it seems to hit HSearch
users on a regular basis.
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/ma
Sorry for the delay Sanne and thanks for the constant work. Feel free
to bug me I will say no if I can't.
On Feb 25, 2009, at 06:19, Sanne Grinovero wrote:
Hi,
I am happy with the "new features" in the roadmap, but still a bit
worried about some
open issues:
HSEARCH-314 is quite annoying and
On Feb 25, 2009, at 06:19, Sanne Grinovero wrote:
HSEARCH-314 is quite annoying and I've run out of ideas to propose;
any direction from someone?
It would be nice if the solution could be reused also by other
listeners (a topic for JPA2 spec?)
See my other email on the Core issue. It's not e
Is this somehow different than the "attempt to load stuff into the PC
during flush" scenarios I see in any of these related issues?
-
Steve Ebersole
Project Lead
http://hibernate.org
st...@hibernate.org
Principal Software Engineer
JBoss, a division of Red Hat
http://jboss.com
http://redhat.com
