Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Types are confusingly named #3

Open
ramdyne opened this issue Jan 21, 2015 · 3 comments
Open

Types are confusingly named #3

ramdyne opened this issue Jan 21, 2015 · 3 comments
Labels

Comments

@ramdyne
Copy link
Contributor

ramdyne commented Jan 21, 2015

Types, classes, what?

@ramdyne ramdyne added the bug label Oct 6, 2015
@ramdyne
Copy link
Contributor Author

ramdyne commented Oct 22, 2015

Note that the whole types thing is a mess. A hardcoded set of types that then point to a table? Why?

How to improve?

@vandenzel
Copy link

Where? Mongo and Python are more or less dynamically typed, aren't they?

Or do you mean type of machine (like "computer" or "printer", more "category" than "class" or "type"). Could be free text in the mongo documents, but selected from a pulldown, with the option to add a new value, which will appear the next time the pulldown is used.

@ramdyne
Copy link
Contributor Author

ramdyne commented Oct 23, 2015

Checkout museumdbtypes.py

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants