Hi Rob, All,
Thanks for the responses.
I probably did not give enough information. There are multiple users hitting
the same table. The status field will have a status initially saying that
for eg: I am still to be looked at, and after a user has manipulated the
record, he/she will update the status to be "finished looking at".
Thus, from the client, the first user should get the first available record
of "still to be done" status, the second user should get the next available
one and so on. This is the case, as the users are all operating
concurrently.
In particular I would want to lock the row, so that 2 users don't get the
same record with the "still to be done" status.
Thus, getting all the rows on to the client as some have suggested may be
out of the question.
Some more answers are below.
>
> So you may have a ejbFindByStatus() which returned and Ordered Collection,
> which you could grab the one you want.
>
If I do this how can I handle the case that 2 or more users are doing the
same.
> Alternatively execute the query in a SSB, and return the key and use the
> ejbFindByPrimaryKey() method.
>
Same as above.
> -) Is the client just updating just a status field and no other fields in
> the row? Is the client updating an "Entity" of the System or just
> setting a general flag?
No, they are updating more fields in the record.
> -) How many rows are in the table? May impact performance of your
> ejbFind....() depending on the container/or mapping tool you're using.
approx 3000
Regards,
Aravind
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
