Hi,
Will someone be kind enough to blow my idea to bits?
Or tell me that it does make sense:~)
I have several read-only tables such as:
A. "States", "Countries", "ZipCodes", etc.
B. "genres", "moods", etc.
... and so on.
They are all Read-only for the most part. While modification of a)
is more rare than that of b), it's conceivable.
I have entity beans represented by a table in the database that have
foreign keys pointing to tables
in A., like "User"
in B., like "Song"
A form will need to provide the values from the Read-only tables as
drop-down lists.
The information in tables in A. and B., is frequently accessed,
shared by several "clients", and may(although very rare) need to be
modified.
So, I'm thinking I can have a ROTables Entity Bean(for want of a
better name:~), that's a singleton(created with a predetermined
primary-key(say, int pk=0, and not allow any other primary key), and that
supports methods like:
getStates
getCountries
getZipCodes
getGenres
getMoods
etc.
Are there any problems in this design? Is there a Better way to do this?
Thanks for your input.
Regards,
Murali Krishna Devarakonda
===========================================================================
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".
