Scott Gray wrote: > I'd be careful with the limit/offset, support tends to vary among > vendors, e.g. http://blogs.sun.com/kah/entry/derby_10_5_preview_fetch
You are mistaken. This does *not* send raw sql to the database. It parses the sql into a DynamicViewEntity, which ofbiz then reconverts back to whatever sql dialect is required by the underlying database. Offset/limit can be completely handled in java. Besides, I currently don't have them fully implemented. And EntityFindOptions has a maxRows option. > I like the concept, but to be honest I have to deal with raw sql so > rarely these days that given the choice I probably wouldn't use it. Which is easier; editting a <view-entity> xml definition, or creating a sql string? Consider the case when you have option parts of a query you have to deal with. In addition, I'll be adding helper methods to parse *just* entity conditions. It's mostly there, I just haven't made the methods public.
