I think we save this documents in the repository, too. Not only in the mailing list or on private servers. Unfortunally not all of us have a private server....
Would this be O.K.? Regards, Henner > -----Urspr�ngliche Nachricht----- > Von: Luca Fossato [mailto:[EMAIL PROTECTED]] > Gesendet: Samstag, 25. Januar 2003 18:41 > An: Henner Kollmann; 'shawn' > Cc: jdbf > Betreff: dbforms internals - Was: Re: AW: > [Jdbforms-developers] whereClause orderBy navigation problem > > > Hi boys ! > > I see the mailing lists re-starts to rumble ;^) > Unfortunately, I started to work for a customer's project and > I suppose > I will not have much time to hack dbforms. Too bad ! > > Anyway, I think it could be useful to collect the > informations derived > from our experiments in an "official" document. Developers > could follow > the debug and its "logical steps", add new informations about their > ideas, discovered bugs, document software flow, etc. > It could links UML diagrams, etc. > > I started a similar document time ago (see > http://www.pow2.com/download/DbForms-internals_20030107.zip - doc/A > journey with DbForms.doc) > > For example, we know that the sql where clause used with resultset > navigation is generated by > - doFreeFormSelect if the user specifies whereClause attribute; > - doConstrainedSelect if the user specifies the filter > attribute; etc. etc. > > As Henner said: > > > Sorry, see my previous mail - free form select and > navigation will not > word together. > It's not a problem > of getSelectQuery - The problem is that in dbformtag > are > two different ways to build the query: > > a] uses > getFreeFormSelect > b] uses getSelectQuery. > > If you use > navigation in a form created with whereClause a] will be > > used. If you hit a navigation button then b] will be used - > with the > result you mentioned. > > Maybe we can bring > the two forms together - I think it could go.... > > > Regards, > Henner > > or... > > >So if you use free-form select with the whereClause nothing > will work - >only the free form select. No filter, no > sorting, no navigation. Even >orderBy is ignored because you > should write it in the whereClause. >then, we could have an > idea about navigation events flow watching the > > >uml/navigationEvent-seq.gif diagram, etc. > > another information: Philiph [thanks to Shawn] said: > > > What I do remember is that I was not responsible for > writing > navigation and furthermore I never liked using it! > I preferred using > JSPtags Pager Tag for any type of navigation. > > probably, whereClause was added to replace filter attribute > when dbforms > could be used bypassing navigation system... > > > -- > > The goal, as we already know, is the understanding of the dbforms > architecture, its flow and its bugs. Having a similar > document, IMHO, we > could decide (for example) to try to debug the wicked > navigation code OR > to fork the project and rewrite the navigation system. > > Please, let me know. > > Regards, > Luca > ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _______________________________________________ DbForms Mailing List http://www.wap-force.net/dbforms
