Hi Ritz,
First, the Entity Engine in OFBiz is really neat. You will want to avoid unstructured (and
possibly mile-long) strings of SQL commands if possible. Also good to avoid RDBMS-specific native
languages.
Chris is right that dynamic view entities are exactly like view entities. Both run through the
same Entity Engine. Caching by OFBiz is also good, though much slower than RDBMS-native caches;
idea is to achieve some good degree of RDBMS-independence. Entity Engine's caching is also easily
programmable; you can't flexibly tweak a RDBMS cache as easily.
When creating dynamic view entities, try to port them over to view entities whenever possible.
Better to have an easy full list of the views in use, in clean and declarative XML form. Not so
good to have your views (or worse, entities) defined in Java code.
Jonathon
Chris Howe wrote:
I can't say I've used the dynamic view entity myself. However, my
impression would be that it would likely have the same benefits that a
normal view-entity has over sql statements.
1) Returns a GenericEntity with named lower camel cased field names in
the object instead of an array of unnamed fields.
2) Cache-able by ofbiz instead of the database.
--- Ritz123 <[EMAIL PROTECTED]> wrote:
Hi,
I am hoping someone can tell me what are the benefits to creating
dynamic
(runtime) view entities over executing the SQL statements directly
using
delegator.
Thanks
--
View this message in context:
http://www.nabble.com/Benefits-of-dynmic-view-entity-tp16765600p16765600.html
Sent from the OFBiz - User mailing list archive at Nabble.com.
