Re: EOModeler
Re: EOModeler
- Subject: Re: EOModeler
- From: Ricardo Strausz <email@hidden>
- Date: Mon, 12 Jan 2004 14:03:51 -0600
On Jan 11, 2004, at 20:55, james cicenia wrote:
Also, Is it possible to model a GROUP BY fetch specification in
EOModeler.
EOModeler is not an ER tool although it can fake it sometimes. The
fact that you're
asking this question indicates that you're still not seeing the
objects you're trying
to model. What collection of your objects would benefit by being
grouped?
The groupings would be for graphing. For instance the count of all
open project requests
by department.
I'd put this on saparate logic... i.e., an independent object which is
capable of graphing on many situations. However, good design may alow
you to do this with EObjects. Say you want to graph invoices by client.
There should be a Client->>Invoice relation; then each client will know
its invoices and it will Foult them in a Invoices array. With a simple
public int howmanyInvoices(){
return invoices().count();
}
you know howmany of them are.
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.