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

Jump to bottom

RDBMS schema allows null types #283

Closed

GoogleCodeExporter opened this issue Mar 16, 2015 · 1 comment

Labels

Component-RDBMS Defect GoogleCode Priority-Medium

GoogleCodeExporter commented Mar 16, 2015

The RDBMS schema in Subversion still allows the type_id column in many tables 
to be null, even though the API no longer allows this. This should be changed. 
The question is, is it safe to change just the schema, or does backend code 
also need to change?

Original issue reported on code.google.com by lar...@gmail.com on 29 Jul 2010 at 7:22

The text was updated successfully, but these errors were encountered:

GoogleCodeExporter added Priority-Medium GoogleCode Defect Component-RDBMS labels

Author

GoogleCodeExporter commented Mar 16, 2015

Made the type_id column required. I see no reason why this would break 
anything. Existing topic maps should be updated anyway.

Original comment by indiapaleale@gmail.com on 24 Sep 2010 at 7:47

Changed state: Fixed

GoogleCodeExporter closed this as completed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment