Hi all,
I have read many post about the Entity bean (useful ?-useless?). I'd like
to speak about a concrete situatuation:
I have a table which has a long list of commercial operations. The Boss
asked
me to have the chance to "filter" these operations by date, by company_id,
by category
of operation and so on.
I started using BMP logic, but I soon discovered it's really an ugly logic.
Since I don't know how many "AND" I have to insert in the select nor I know
if the user wants at all filtering of records I found myself at a dead
point.
As you can see it's technically impossible to know before running where I
have to issue
the "WHERE" clause......
yes I could issue it just after the SELECT
sql = "SELECT * FROM TABEL WHERE"
But what if the user doesn't want at all the filter ?? I solved the
situation appendind
-in this second situation- a condition that's always fulfilled....but still
it's just a hack,
not a real programmer solution......
Then I thought...this could be made with Entity Bean CMP, issuing a
FindByCompanyAndDate,
and setting only the fields I want actually to use as a filter......
What do you say ? can this be a "classic" example of when Entity bean are a
"MUST" ?
I await your kind replies.....
Good weekend to everybody
Francesco Marchioni
===========================================================================
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".
