Re: when is derived column resolved
Re: when is derived column resolved
- Subject: Re: when is derived column resolved
- From: Chuck Hill <email@hidden>
- Date: Wed, 13 Jan 2016 00:55:46 +0000
- Thread-topic: when is derived column resolved
I can’t come up with a better case. I don’t recall ever using them. As Paul said, it would have to be a read only column. This might have made more sense years ago when offloading processing to the database made sense. If it ever really did.
For more data inconsistency fun, you can flatten attributes too!
Chuck
Hi Ted,
On 13 Jan 2016, at 10:39 am, Theodore Petrosky < email@hidden> 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?
|
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden