-
Notifications
You must be signed in to change notification settings - Fork 4
RIS light initial commit #1843
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
base: master
Are you sure you want to change the base?
RIS light initial commit #1843
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since these models look like more or less 1:1 copies of the PAS models I think we should move the lowest common denominator into a parliament
namespace with 'generic'``type
, then PAS and RIS/Org (not sure yet if we need a RIS namespace) can each make their own subclasses with their own extensions.
We can also drop the pas_
prefix from the tables, just make sure to add a migration to rename the tables (it's possible SQLAlchemy will already have created an empty table for the new name, so you may need to drop it first, if it exists but is empty).
Otherwise this looks mostly good to me, although you're missing a ContentMixin
for Commission
(we may want a ContentMixin
for all or at least most of the shared models, so we can more easily extend the specialized subclasses).
I created the namespace |
We usually don't use table prefixes, but I don't have strong feelings about using one, so we can keep it. I would keep the PAS specifc models like |
Make sure to add You could put the migration for renaming the tables in there, instead of putting it into PAS. |
Yes, that is what I missed! |
Co-authored-by: David Salvisberg <[email protected]>
RIS: Models for RIS light
TYPE: Feature
LINK: ogc-2245
The drawing shows the new models that are not adopted from
PAS
to get a quick overview.