At 12:00 26.06.01 -0500, you wrote:
>Julia Stobbe wrote:
> > >
> > >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... ??
>
>Jerome Verleyen
same effect in a nicer way (just using the Criteria API):
Criteria crit = new Criteria();
crit.add (TurbineUserPeer.USER_ID, 0 . Criteria.GREATER_EQUAL);
User[] users = TurbineSecurity.getUsers(crit);
but this is just a hack around the problem.
any ideas ?
julia
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
