I propose to add a way to disable DataSourceFactory caching in navigation events. This is to solve the following issue: I a have build up a page showing a table in which there's a mechanism to change the orderby clause (simply the page is reloaded with the dbform's orderBy attribute changed). To maintain position I have to call navFirst event, but if caching is active the result is that the query isn't executed and the rows aren't reordered. So I think about two way to solve this:
1) add a new attribute to DbFormTag (something like "forceReload")
2) make the caching system more elaborate, maybe inserting in the DataSourceList key the real SQL query instead of the page name.


Any comment?

--
Sergio Moretti



-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01
_______________________________________________
DbForms Mailing List

http://www.wap-force.net/dbforms

Reply via email to