Shorten the text a little bit....
> If someone uses the where clause, everything else, e.g. filters will
be overwritten, navigation will also be not possible. Same here?
WhereClause may
> contain group-by and order-by clauses. What happens then?
The freeForm where clause overrides everything. This is hardcoded in
DbFormsTag. I like this. You are free to formulate what ever you like.
So it will be the same here.
>
> Summary:
>
> - consider to allow expression attribute for search tag
In the syntax it is allowed yet, will try to implement.
> - consider to allow free form strings for from clause and for a
> whereClause plugin (not replacement as it is using current
> whereClause for dbform tag!). So it would be possible to use
> join views, subqueries and a lot more.
That is no problem. But how should the whereClause be added to the rest
of the query? And, or? Better define
whereClause=" customer.id = order.cust_id AND "
And let the where part from the form follow up.
> - it is not important to try to make as many views as possible
> updatable. Just a simple view containing a whole base table
> should be updatable. Syntax
>
> <view name="xyz_view" from="table"/>
>
> can't be made better!
This is the only thing wich works and is tested in the moment!
> - I would agree (see Luca's and your last post) to choose another
> name for the tag that does not make developers think of
> database views.
Do you have one?
Regards,
Henner
-------------------------------------------------------
This SF.net email is sponsored by: ApacheCon, November 18-21 in
Las Vegas (supported by COMDEX), the only Apache event to be
fully supported by the ASF. http://www.apachecon.com
_______________________________________________
DbForms Mailing List
http://www.wap-force.net/dbforms
