7 Nov
2011
7 Nov
'11
11:14 p.m.
On Nov 7, 2011, at 10:37 PM, Tudor Girba wrote:
Yes
Hi,
On 7 Nov 2011, at 14:05, Usman Bhatti wrote:
long time ago uniqueName was used as a mooseId and I was wondering if we should introduce
a unique naming schema for new entity but this is not the case.
Hi guys
We are adding Author to Moose as an experience to learn how to extend moose.
In the past, for a moose entity with a unique name we were using the uniqueName as
mooseID
What is the status now?
I do not understand the question. mooseName is not essential for storage, but it can be
used to retrieve an element from a group based on it. For example we would to make sure that author can
be retrieved by their name
mooseModel entityNamed: 'me'
and that we do not have conflict with other Moose entity.
Then, make it unique :). For example: 'Author - me'. But, you would not want to use entityNamed on the
whole model because you might end up having to lookup throughout millions of objects.
Instead, you better use it on the group of authors:
Sure this is not the idea. In fact we are building a moose demo and as well practicing
with usman.
mooseModel allAuthors entityNamed: 'me'.
ok
Cheers,
Doru
Stef
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
--
www.tudorgirba.com
"Live like you mean it."
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev