Page History

...

Previous discussions related to this topic can be found here:

1. 2008-12-08 - http://n4.nabble.com/Save-Search-in-database-td196166.html#a196167^{Image Removed}
2. 2009-10-26 - http://n4.nabble.com/Searches-done-by-default-td213375.html#a221317^{Image Removed}

User Interaction

...

Two new entities will be required:
PersistedForm - Main entity

• persistedFormId - Sequenced primary key
• formTargetUrl - Stores the target request (would be the target from the find form), this would be used to find persisted searches for populating the drop-down box and also as the target for persisted search submission
• name - The user provided name for the saved search
• persistanceType - This will mostly be a place holder for now, refer to potential uses below
• userLoginId - The user for whom the search has been persisted, allowed to be null in the case of global saved searches i.e. available to anyone who would normally be able to view the formTargetUrl
• createdByUserLoginId - means to keep track of who created a global saved search
• createdDate - Timestamp for when the search was persisted
• hitCount - Keeps track of number of times the persisted search has been used, could allow for floating the most commonly used searches to the top of the drop-down (not sure about this, just a thought)

PersistedFormParam - Child entity containing the request parameters for the request

• persistedFormId - Primary and also Foreign Key to PersistedRequest
• parameterName - The name of the parameter and also part of the Primary Key
• parameterValue - The value of the named parameter

I'm not sure about the names but given the #Other potential uses of the entities, I've tried come up with something as generic as possible, the data could also be considered to represent a persisted request rather than a form. Other suggestions are welcome

...