Yeah you could setup a Report EOModel that has a different entity
definition on the same table, too. The view approach potentially
makes it a little easier to define fancier queries that you can just
treat like a regular (non-editable) EO.
ms
On Jul 8, 2009, at 4:37 PM, Mr. Frank Cobia wrote:
Sorry. I meant never use them in the report or the command line
application. They are used by my web apps.
Frank
On Jul 8, 2009, at 4:34 PM, Mike Schrag wrote:
Is there any advantage to creating a view and pointing my new
entity to that view as opposed to just pointing the entity
directly to the table and leaving out the fields I am not
interested in? It seems like the view would just add overhead, but
you may know some advantage to using it that I am not aware of.
Oh, if you NEVER use the fields, then by all means, just remove
them from your entity definition (assuming they're not "NOT NULL"
fields).
ms
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/frank.cobia%40f2technology.com
This email sent to [email protected]
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/mschrag%40mdimension.com
This email sent to [email protected]
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [email protected]
