Skip to content
This repository has been archived by the owner on Jan 9, 2019. It is now read-only.

Remove status property from Node #175

Closed
ahonor opened this issue Jul 26, 2012 · 3 comments
Closed

Remove status property from Node #175

ahonor opened this issue Jul 26, 2012 · 3 comments
Assignees
Labels
Milestone

Comments

@ahonor
Copy link
Contributor

ahonor commented Jul 26, 2012

Remove the status property from the Node domain class. An attribute can be defined for users interested in a property like status.

See #169

@ghost ghost assigned ahonor Jul 26, 2012
@orubel
Copy link
Contributor

orubel commented Jul 26, 2012

Well this was for 'enabled','disabled','pending',etc. This allows people to build nodes without putting them into service as well as providing quick search without nested queries and/or lots of joins . Highly recommend not moving since this can be future function if not ready to enable yet but should be at this level in the tree.

It would be impossible by the way to build a node without putting it into service without building said attribute; with status IN node, you have said ability. You would have to build out the node to provide this capability first in the model you are describing. By default, this exists in current model.

@ahonor
Copy link
Contributor Author

ahonor commented Jul 26, 2012

Attributes should be easy to search as that is a key use pattern. We can optimize that for ease of use.

@orubel
Copy link
Contributor

orubel commented Jul 26, 2012

You would still need to be able to create the node and have it in a holding pattern without having to create any attributes, IMHO. Otherwise you are stating to users that this attribute has to be created EVERY time which is an annoyance.

@ahonor ahonor closed this as completed in 53ff901 Jul 26, 2012
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants