Ramsey knows what I am trying to do.
But that leads to other quandaries:
We have an ERUser framework, and I have my project framework.
I would like to separate User/Auth from my account, profile, business, etc.
So which is proper? Does a person subclass a user or does a user subclass a person. In my case practicalities seem to dictate that I subclass user. But then the issue of actual database storage comes into play. I want my user table separate for my person table.
So I still think I should punt and just break one side and and bridge where needed in code.
On Dec 5, 2012, at 8:07 PM, Ramsey Gurley < email@hidden> wrote: Subclass :-)
James Cicenia <email@hidden> wrote:
Suboptimal. :-(
FM1.User ==> FM2.Person
Now I have to give up the reflexive relationship or the two one relationship.
How does one then ever fully bridge two models from two frameworks?
James
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
|