 |
BorlandTalk.com
Borland discussion newsgroups
|
| View previous topic :: View next topic |
| Author |
Message |
Tom Corcoran
Guest
|
 Posted: Mon Jan 19, 2004 11:59 pm Post subject: Mixing database persistence & registry |
 |
|
We use a persistence framework based on TOwnedCollection to control the
database access. Each user that logons on the system can choose a certain
CollectionItem for filtering. I need to store the last filtered item. It
would be no problem to add a collection object to store this but it is
essentially a machine specific setting (since the user will for all
intensive purposes always use the same machine) and would seem to have no
place in the database.
I am considering storing this last filtered CollectionItem (oid) in the
registry. All the published properties in the collection are persisted (to
the database). What is the feeling about adding a public property (which
talks to a separate registry class) to store this last filtered
CollectionItem ?
Any discussion, comments welcome.
Thanks a lot, Tom.
|
|
| Back to top |
|
 |
Jim Cooper
Guest
|
| Posted: Tue Jan 20, 2004 1:10 am Post subject: Re: Mixing database persistence & registry |
|
|
| Quote: | We use a persistence framework
|
I've got a feeling I might recognise it :-)
Define a BO to store the required info, and then define a new mapper
class that talks to the registry, and register that to persist the BO.
Cheers,
Jim Cooper
_______________________________________________
Jim Cooper [email]jim (AT) falafelsoft (DOT) com[/email]
Falafel Software http://www.falafelsoft.co.uk
_______________________________________________
|
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
FAQ
Search
Memberlist
Usergroups
Register
Profile
Log in to check your private messages
Log in
