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

required fields too restrictive on equipment #136

Open
smrgeoinfo opened this issue Jun 26, 2017 · 0 comments
Open

required fields too restrictive on equipment #136

smrgeoinfo opened this issue Jun 26, 2017 · 0 comments
Assignees
Labels

Comments

@smrgeoinfo
Copy link

in equipment, not null constraints are too restrictive
equipmentmodelid integer NOT NULL,
equipmentserialnumber varchar (50) NOT NULL,
equipmentownerid integer NOT NULL,
equipmentvendorid integer NOT NULL,
equipmentpurchasedate timestamp NOT NULL,
This information is rarely known for legacy data.
Not only that, but modelid, owerid, and vendorid are foreign keys to equipment models, people and organizations, so in cases where the information is not known, a dummy record has to be present as the target of the FK. These fields should all be nilable, with recommended nil-values like OGC uses (missing, not applicable, with held...).

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