Hi Ted,

On 13 Jan 2016, at 10:39 am, Theodore Petrosky <[email protected]> wrote:

>>> 1. should I go back to creating a method on Entity Person fullName that 
>>> returns a string concatenating first and last names?
>> 
>> Probably, yes.
> 
> OK, that’s a plan, when do you feel it’s appropriate to use a derived column?

I am reasonably sure we use them nowhere. I think you would want to limit their 
use to read-only attributes (or you will immediately hit the freshness issue 
you’ve already discovered), and quite probably to transformations that are 
better done in the database than in Java. (Pulling an example out of the air: 
maybe some kind of geospatial result that you can get from PostGIS. But even 
then, if you can write to the columns the result depends on, you’ve got a 
problem again.) Does anyone have a solid use case for derived attributes that 
they actually use in the real world?


-- 
Paul Hoadley
http://logicsquad.net/



 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      ([email protected])
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com

This email sent to [email protected]

Reply via email to