Sanjay Nambiar wrote:
>
> The business logic does not require a query by primary key and hence the
> customer has not mentioned a primary key for the table.
> All queries are for multiple rows.....
>
I would say this is a strong indicator that entities aren't the way to go. Stick
with the session bean. Why do you want entity beans?
> Hope u got the problem...I am not in a
> position to change database design.I am using session bean and would like to
> know a workaround for multiple updates and deletes
>
Don't change the design to fit entity beans if its a good design (ie entity
beans would be the wrong selection of representation). What problems are you
having with multiple updates and deletes?
regards
/Kalle
--
>From the Soviet Weekly: "There will be a Moscow Exhibition of Arts by 15,000
Soviet Republic painters and sculptors. These were executed over the past two
years."
Karl-Fredrik Blixt
Computer Science student at LiTH, Sweden
Homepage: http://travel.to/kp
Telephone: +46-(0)13-17 99 29
Cellular: +46-(0)739-87 11 03
ICQ: 4744258
===========================================================================
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".
