I would use a role pattern.
User - Role
You should even be able to make a rule qualifier like
user.roles.name contains Vendor
Ramsey
On Aug 13, 2013, at 11:19 AM, Theodore Petrosky wrote:
I have been playing with D2W and I may have boxed myself into a corner.
A User is of a type. a User
Use vertical inheritance and then use entity.name='Vendor'?
Sent from my iPad
On Aug 13, 2013, at 8:19 AM, Theodore Petrosky tedp...@yahoo.com wrote:
I have been playing with D2W and I may have boxed myself into a corner.
A User is of a type. a User can be a Vendor or a Client or a Worker.
I like this method of inheritance however, why did you choose vertical
inheritance? I did one vertical and one single table. I put a qualifier
userType='Vendor' on the table.
I think the only thing 'wrong' with inheritance is that I can not create a User
that is both a employee and a vendor.
What about ERTag? A user could be tagged as both ‘vendor’ and ‘employee.'
T
On Aug 13, 2013, at 1:31 PM, Theodore Petrosky tedp...@yahoo.com wrote:
I like this method of inheritance however, why did you choose vertical
inheritance? I did one vertical and one single table. I put a qualifier
Sorry brain fart (dealing with bronchitis) - I meant single table inheritance.
But if an object can be both then I would go with Ramsey's method.
Aloha,
Mr. Johnny Miller
Web Development Manager
Kahalawai Media Company
Lahaina, HI 96761
tel: (808) 661-7962 | mobile: (808) 283-0791
website |
almost but maybe barking (or coughing) up the wrong tree.
without cloning all the fetch specification methods from _User into User.java
is there an easy way to set IsDeep to false?
On Aug 13, 2013, at 4:42 PM, Johnny Miller jlmil...@kahalawai.com wrote:
Sorry brain fart (dealing with
Tweak your eotemplate? And have isDeep set by a protected method that you can
override if you don't want the default behavior?
Just thinking out loud there?
Sent from my iPad
On Aug 13, 2013, at 11:49 AM, Theodore Petrosky tedp...@yahoo.com wrote:
almost but maybe barking (or coughing) up
