Open t-book opened 1 month ago
HI @t-book
The migration to geonode-data
is carried out by the geonode-importer
tool. This importer not only handles the import process, but also enables the creation of dynamic models for each imported dataset. With this feature, the imported dataset can be directly queried from geonode, allowing users to navigate through the dataset data via Django.
Currently, the dynamic model feature is disabled by default, but it can be activated by adding the environment variable IMPORTER_ENABLE_DYN_MODELS
. The migration on geonode-data is necessary for the dynamic model app. The Django-migration table is available there.
We can consider making the migration on geonode-data optional if the IMPORTER_ENABLE_DYN_MODELS
is enabled.
Expected Behavior
The
django_migrations
table should live in databasegeonode
?Should this not read
--database=default
instead of--database=datastore
?https://github.com/GeoNode/geonode/blob/4b6d872682ef0efd1ae61bf515b1f7d2250ba448/tasks.py#L326
or is there some reason to keep migrations table in geonode_data?
Actual Behavior
The table is created in
geonode_data
.Steps to Reproduce the Problem
Specifications