The major concert about whereClause is (for me) correlated with my major concern about the new navigation system, in which, (as I understand) you fetch all records systematically, this may cause problems using very large tables. For this reason only I like the idea of a filter that could be implemented leaving the way to get back to page navigation using a where clause (in the next days I will try to analyze more deeply the problem of the navigation).
Anyway, I saw the development trend is to improve the project trying also to *simplify / refactoring* the code where possible. Making UML diagrams I saw the new event handler is (am I right ?) simpler than the previous one.
Events code is simpler and uses standard patterns (DAO).
And I hope that there will ONLY one navigation system (the new one), not two.
So I think another step could be to use standard SQL to specify "all type of filters". Having only whereClause and orderBy attributes could be the best thing to obtain. Having another (redundant) attribute is not a good idea, IMHO.
cheers, 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
