Migrating to django-idom==3.0.0a1

[numpde]

I'm migrating to

django-idom==3.0.0a1
idom==1.0.0a2

and on ./manage.py migrate get the following. Suggestions? Thank you.

2023-02-04T20:02:22+0000 | DEBUG | IDOM is in debug mode
Traceback (most recent call last):
  File "/usr/local/lib/python3.10/site-packages/django/db/backends/utils.py", line 89, in _execute
    return self.cursor.execute(sql, params)
psycopg2.errors.UndefinedTable: relation "django_idom_componentparams" does not exist
LINE 1: ...django_idom_componentparams"."last_accessed" FROM "django_id...
                                                             ^


The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/biohire-root/client/./manage.py", line 22, in <module>
    main()
  File "/biohire-root/client/./manage.py", line 18, in main
    execute_from_command_line(sys.argv)
  File "/usr/local/lib/python3.10/site-packages/django/core/management/__init__.py", line 446, in execute_from_command_line
    utility.execute()
  File "/usr/local/lib/python3.10/site-packages/django/core/management/__init__.py", line 420, in execute
    django.setup()
  File "/usr/local/lib/python3.10/site-packages/django/__init__.py", line 24, in setup
    apps.populate(settings.INSTALLED_APPS)
  File "/usr/local/lib/python3.10/site-packages/django/apps/registry.py", line 124, in populate
    app_config.ready()
  File "/usr/local/lib/python3.10/site-packages/django_idom/apps.py", line 24, in ready
    db_cleanup(immediate=True)
  File "/usr/local/lib/python3.10/site-packages/django_idom/utils.py", line 327, in db_cleanup
    if not cleaned_at_str and ComponentParams.objects.all():
  File "/usr/local/lib/python3.10/site-packages/django/db/models/query.py", line 408, in __bool__
    self._fetch_all()
  File "/usr/local/lib/python3.10/site-packages/django/db/models/query.py", line 1867, in _fetch_all
    self._result_cache = list(self._iterable_class(self))
  File "/usr/local/lib/python3.10/site-packages/django/db/models/query.py", line 87, in __iter__
    results = compiler.execute_sql(
  File "/usr/local/lib/python3.10/site-packages/django/db/models/sql/compiler.py", line 1398, in execute_sql
    cursor.execute(sql, params)
  File "/usr/local/lib/python3.10/site-packages/django/db/backends/utils.py", line 103, in execute
    return super().execute(sql, params)
  File "/usr/local/lib/python3.10/site-packages/django/db/backends/utils.py", line 67, in execute
    return self._execute_with_wrappers(
  File "/usr/local/lib/python3.10/site-packages/django/db/backends/utils.py", line 80, in _execute_with_wrappers
    return executor(sql, params, many, context)
  File "/usr/local/lib/python3.10/site-packages/django/db/backends/utils.py", line 84, in _execute
    with self.db.wrap_database_errors:
  File "/usr/local/lib/python3.10/site-packages/django/db/utils.py", line 91, in __exit__
    raise dj_exc_value.with_traceback(traceback) from exc_value
  File "/usr/local/lib/python3.10/site-packages/django/db/backends/utils.py", line 89, in _execute
    return self.cursor.execute(sql, params)
django.db.utils.ProgrammingError: relation "django_idom_componentparams" does not exist
LINE 1: ...django_idom_componentparams"."last_accessed" FROM "django_id...

[rmorshea]

Ping: @Archmonger

[numpde]

This may be helpful. The error occurs on remote, but everything previously worked on local. So, I ran ./manage.py sqlmigrate django_idom 0001 locally which gives:

BEGIN;
--
-- Create model ComponentParams
--
CREATE TABLE "django_idom_componentparams" ("uuid" char(32) NOT NULL PRIMARY KEY, "data" BLOB NOT NULL, "created_at" datetime NOT NULL);
COMMIT;

On remote, I don't have the table django_idom_componentparams. When I try this initial migration in the psql shell on remote, I get:

ERROR:  type "blob" does not exist
LINE 1: ...("uuid" char(32) NOT NULL PRIMARY KEY, "data" BLOB NOT N...

==

On remote:
PostgreSQL server: 15.1 (Debian 15.1-1.pgdg110+1)
Client (psql): 13.9 (Debian 13.9-0+deb11u1)

==

EDIT: Ok, I think I fixed it with the query (but don't understand why it's necessary; I see the Django migrations in the django_idom site package):

CREATE TABLE "django_idom_componentparams" ("uuid" uuid NOT NULL PRIMARY KEY, "data" bytea NOT NULL, "last_accessed" timestamp with time zone NOT NULL);

[Archmonger]

Thanks for the details, I'll fix it in the next pre-release of Django-IDOM