Comment 8 for bug 1513981
Revision history for this message
| Shraddha Pandhe (shraddha-pandhe) wrote | #8 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
a60fb26
(Get the code!)
@garyk,
I went through the spec you referenced. Its not going to solve the problem. In fact, its probably going to make things worse.
To start with, tags have the same problem of people putting arbitrary data there. Maybe its not as bad as JSON blobs, but it is bad.
We want to put lot more information there and not just tags. We want to be able to schedule based on network information. I think its a valid use-case and potentially a more common use-case in future. In order to make scheduling decisions, ideal scenario would be storing the required data in separate columns in the database.
We could put all the information in the "tags" field itself, but we wont be able to do any intelligent DB operations on them. So IMHO, tags cannot be leveraged for scheduling purposes.