roken,
> or you are starting on a new project, then Maven is worth a look. The
> Hibernate project has a very effective build, and the site docs are all very
> well put together. Of course, it would be nice maybe to see
> JCoverage/Clover, StatCVS, PMD, Simian, FindBugs, Junit etc reports ad
Quoting Christian Bauer <[EMAIL PROTECTED]>:
> I'll do it. We don't need any Maven praising here...
Folks,
Whats wrong with Maven?
Seriously, I'm not trying to start a flame war or promote dissention from
within, but what are your gripes? I'm trying to get a valued opinion before
possibly inco
> have a prefix that indicates it should flow through into the resulting
> xml
I think you meant resulting sql, right? ;)
Les
---
This SF. Net email is sponsored by: GoToMyPC
GoToMyPC is the fast, easy and secure way to access your computer fr
> I would rather you go the other way, i.e. unprefixed functions should be
> portable ANSI-derived aliases which are mapped by the dialects to the
> necessary names. For driver-specific functions you could potentially
> have a prefix that indicates it should flow through into the resulting
> xml, e
> How about we get a list of ANSI-standard SQL functions and portably
> support those and those only (I don't think there are many of them).
This makes a lot of sense. However, what if something so commonly used (like a
current_timestamp() function) is not part of the ANSI standard (assuming ANSI
> I am not familiar with the 'current date' construct in this example:
> "from Calendar cal where cal.holidays.maxElement > current date"
>
> Is 'current' a function? If so, is 'date' the argument? Is this ORACLE
> specific?
"current date" would need to be a Hibernate defined token.
Oracl
> No, this is a different strategy, it's called "table per class
> hierarchy", not "table per concrete subclass".
Wonderful. Thanks so much for the clarification. I've been using Hibernate for
quite a while now, but everything I use is a to support the
underlying relational model. I've had ver
> Thats why you have to use the strategy instead of the
> . You have a discriminator value already, but keep in
> mind that this strategy has some problems, like impossibility of NOT
> NULL constraints.
Just to understand you...
Lets say my application wants to persist instances of 3 permission
Folks,
I haven't received a reply to my forum post, so I was wondering if anyone here
on the developer mailing list might be able to help out
My post:
http://forum.hibernate.org/viewtopic.php?t=925582
Basically, I'm trying to save instances of different subclasses to the same table...
the
> Okay.. I guess that kind of thing is that someone looking at
> code will sometimes say "String concatenation Bad!", which I
> think is really a bit of a myth in modern JVM's..
It is a myth.
Both Sun and IBM's JDK/JVM do pre-compiler optimization for String
concatentation (and a whole lot mo
10 matches
Mail list logo
