"Uwe Grauer" <[email protected]> schrieb: > Sibylle Koczian wrote: > > > > - set...Clause methods > > The setWhereClause() method takes a correctly constructed WHERE clause > > _without_ the word "WHERE", but the clause used in a setJoinClause() > > call _must_ start with "JOIN", right? And here table aliases for the > > joined tables can be set and used in other calls building the SQL. Still > > correct? How about the other set...Clause methods, do they or don't they > > have to start with the appropriate SQL keyword? > > > > Are there any examples for bizobjs with changing queries according to > > user input? > > I have no real answers to your questions just because i didn't come into > the situation to test all this. > When i have complicated search forms i build my query myself as this > seemed to be much easier than using the sqlbuilder. > Quite true (even if you have to manage linking between tables yourself, as I just learned). But if parts of your SQL have to change, then you might end up creating your own ad hoc SQL builder. That seems to me the use case for those setXxxClause() methods.
> Maybe a selectable stored procedure would help too. > One thing you have to make sure is that you do not use the same bizobjs > for queries and for edits. Why not? Especially, why such a rule for all cases, simple or complex? I suppose the NonUpdateFields list works with UserSQL as well as with SQL constructed by the SQL builder, so additional fields in the bizobj used for searching should be no problem? > That means you have to use browser forms and > edit forms. Bizobjs on my browser form often use joins to add > searchfields from additional tables, but i try to have only one grid > for browsing. Once the searchform found something, the user calls > additional forms for editing. > But that way calling the edit form must pass information about the selected record from the search form (the PK for choice). If you put search page and edit page on a dPageFrame and let them use the same bizobj, the edit page automatically shows the selected record (and the right child records, if any). Except if the search doesn't find any records: in that case separate forms and separate bizobjs might really be easier to handle. Regards Sibylle -- Dr. Sibylle Koczian _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users Searchable Archives: http://leafe.com/archives/search/dabo-users This message: http://leafe.com/archives/byMID/[email protected]
