Julia Stobbe wrote:
>
> taking up this old thread again, sorry about the delay ...
>
> > > another problem regarding transactions will be coming up: when testing
> > > whether transactions are needed, criteria.containsObjectColumn(dbname)
> > > only returns true when criteria is not empty...not always a valid
> > > assumption, i think.
> >
> >I don't usually need transactions, so forgive me if this is obvious,
> >but can you provide a use case for this and/or a patch which
> >illustrates a fix for this insidious situation?
> >Daniel
> example:
> working with turbine-release (turbine-src-2.1) code, i try to get all users :
>
> Criteria crit = new Criteria();
> User [] users = TurbineSecurity.getUsers(crit);
>
Hi,
I just try this ( in fact in the FluxTool.jar file ) :
Criteria crit = new Criteria();
Criteria.Criterion crit =
criteria.getNewCriterion("TURBINE_USER.USER_ID",new
Integer(0),Criteria.GREATER_EQUAL);
crit.setTable("TURBINE_USER");
User [] users = TurbineSecurity.getUsers(crit);-
And so, this bypass the problem of the Criteria that contains any
Criterion.. But i think that is awfull. It should be a nice methos to do
this... ??
>julia
Jerome Verleyen
- La connerie � ce point-l�, moi, j'dis qu'�a devient g�nant.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
