Hey John, this looks very good.
> c.or(d);
Maybe make more method overloading that allows you to just define something
like this:
Criteria.Criterion c = crit.getNewCriterion("SCARAB_MODULE",
"MODULE_NAME", "name", Criteria.EQUAL);
c.or ("SCARAB_MODULE", "MODULE_DESCRIPTION", "%serious%", Criteria.LIKE);
That would have the same effect as doing this:
Criteria.Criterion c = crit.getNewCriterion("SCARAB_MODULE",
"MODULE_NAME", "name", Criteria.EQUAL);
Criteria.Criterion d = crit.getNewCriterion("SCARAB_MODULE",
"MODULE_DESCRIPTION", "%serious%", Criteria.LIKE);
c.or(d);
It just seems cleaner to me than having to always first get a reference to
the Criterion object when you may not really need it.
> FROM SCARAB_R_MODULE_USER, SCARAB_MODULE, SCARAB_MODULE f, SCARAB_ISSUE
Shouldn't SCARAB_MODULE only need to be defined once?
Also, if you add an alias for a table name, then it should probably be used
throughout the rest of the SQL statement instead of the main table name. Am
I wrong in that thinking?
-jon
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
