Add a `--devel` option to `hop new`
Closed this issue · 1 comments
joel-m commented
When creating a new package from an existing database, hop new <package name>
adds two schemas to the database:
half_orm_meta
half_orm_meta.view
It should not be mandatory to use hop
. Without those metadata, you loose the ability to know what is the current revision of the database. This information is modified when you use apply-patch
, undo-patch
, commit-patch
in development or upgrade
, restore
in production.
hop
could still be useful without this information to keep in sync the python package with an evolving model maintained by another team. In this case, hop apply-patch
would just modify the modules impacted by the new database release.
proposition
hop new <package>
only works for an existing database and doesn't modify this database by addinghalf_orm_meta
andhalf_orm_meta.view
to the model.hop new <package> --devel
doesn't need an existing database to work. If the database exists, the model is modified with the two schemashalf_orm_meta
andhalf_orm_meta.view
.