Moving from master back to stable?

[StormTrooper]

I've been running Inventree master version for a number of years now and every few weeks do a update.

Inventree has become a few useful tool now as I use it to sync stock to various other eCommerce platforms.

For this reason I would like to rebuild my server (It's currently running on a old laptop that's powered on 24x7) on better hardware and use the stable version.

My question is since I'm running the master version I can't rebuilt and restore the database (Running mysql) to a stable version. Does this mean I'm stuck on the dev version forever? (I'm on 0.15.0 dev)

Or can I wait for the stable version to catch up to 0.15.0 dev (ie I stop doing upgrades) and then rebuild to 0.15.0 stable? Is that a option?

[SchrodingersGat]

The best approach would be to wait for the (imminent) 0.15.0 release, and do your switch at that point. Right at the point of release, stable and master will be the same. Not necessarily at the same git commit, but crucially the database schema and API will be the same.

At that point, checkout "stable" and run "invoke update". Then, just stay on stable.

[StormTrooper]

Thanks. Will wait for the stable to catchup and then proceed.

[StormTrooper]

With 0.15.0 released I thought I'd try moving my 0.15.0 dev to 0.15.0 stable.

Wow - is this giving me so many issues.

I've built a new server with 0.15.0 stable. First I tried exporting the mysql database from dev and importing into the stable database, and it's giving me loads of errors.

Data imports correctly and I can logon with my old password. List of parts are all there, but when I click into a part I get:

Traceback (most recent call last):

File "/opt/inventree/env/lib/python3.9/site-packages/django/db/backends/utils.py", line 89, in _execute
return self.cursor.execute(sql, params)

File "/opt/inventree/env/lib/python3.9/site-packages/django/db/backends/mysql/base.py", line 75, in execute
return self.cursor.execute(query, args)

File "/opt/inventree/env/lib/python3.9/site-packages/MySQLdb/cursors.py", line 179, in execute
res = self._query(mogrified_query)

File "/opt/inventree/env/lib/python3.9/site-packages/MySQLdb/cursors.py", line 330, in _query
db.query(q)

File "/opt/inventree/env/lib/python3.9/site-packages/MySQLdb/connections.py", line 261, in query
_mysql.connection.query(self, query)

MySQLdb.OperationalError: (1054, "Unknown column 'part_supplierpart.active' in 'field list'")


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


Traceback (most recent call last):

File "/opt/inventree/env/lib/python3.9/site-packages/django/core/handlers/base.py", line 197, in _get_response
response = wrapped_callback(request, *callback_args, **callback_kwargs)

File "/opt/inventree/env/lib/python3.9/site-packages/django/views/generic/base.py", line 104, in view
return self.dispatch(request, *args, **kwargs)

File "/opt/inventree/env/lib/python3.9/site-packages/django/contrib/auth/mixins.py", line 109, in dispatch
return super().dispatch(request, *args, **kwargs)

File "/opt/inventree/env/lib/python3.9/site-packages/django/views/generic/base.py", line 143, in dispatch
return handler(request, *args, **kwargs)

File "/opt/inventree/env/lib/python3.9/site-packages/django/views/generic/detail.py", line 109, in get
context = self.get_context_data(object=self.object)

File "/opt/inventree/src/backend/InvenTree/part/views.py", line 355, in get_context_data
ctx = part.get_context_data(self.request)

File "/opt/inventree/src/backend/InvenTree/part/models.py", line 438, in get_context_data
context['on_order'] = self.on_order

File "/opt/inventree/src/backend/InvenTree/part/models.py", line 2227, in on_order
for sp in self.supplier_parts.all():

File "/opt/inventree/env/lib/python3.9/site-packages/django/db/models/query.py", line 398, in __iter__
self._fetch_all()

File "/opt/inventree/env/lib/python3.9/site-packages/django/db/models/query.py", line 1881, in _fetch_all
self._result_cache = list(self._iterable_class(self))

File "/opt/inventree/env/lib/python3.9/site-packages/django/db/models/query.py", line 91, in __iter__
results = compiler.execute_sql(

File "/opt/inventree/env/lib/python3.9/site-packages/django/db/models/sql/compiler.py", line 1562, in execute_sql
cursor.execute(sql, params)

File "/opt/inventree/env/lib/python3.9/site-packages/django/db/backends/utils.py", line 67, in execute
return self._execute_with_wrappers(

File "/opt/inventree/env/lib/python3.9/site-packages/django/db/backends/utils.py", line 80, in _execute_with_wrappers
return executor(sql, params, many, context)

File "/opt/inventree/env/lib/python3.9/site-packages/django/db/backends/utils.py", line 89, in _execute
return self.cursor.execute(sql, params)

File "/opt/inventree/env/lib/python3.9/site-packages/django/db/utils.py", line 91, in __exit__
raise dj_exc_value.with_traceback(traceback) from exc_value

File "/opt/inventree/env/lib/python3.9/site-packages/django/db/backends/utils.py", line 89, in _execute
return self.cursor.execute(sql, params)

File "/opt/inventree/env/lib/python3.9/site-packages/django/db/backends/mysql/base.py", line 75, in execute
return self.cursor.execute(query, args)

File "/opt/inventree/env/lib/python3.9/site-packages/MySQLdb/cursors.py", line 179, in execute
res = self._query(mogrified_query)

File "/opt/inventree/env/lib/python3.9/site-packages/MySQLdb/cursors.py", line 330, in _query
db.query(q)

File "/opt/inventree/env/lib/python3.9/site-packages/MySQLdb/connections.py", line 261, in query
_mysql.connection.query(self, query)

django.db.utils.OperationalError: (1054, "Unknown column 'part_supplierpart.active' in 'field list'")

Then I retried again after another rebuild and according to the docs for DB migration I should use
invoke export-records -f data.json

This however gives me a error on the source server:

(env) inventree@inventree:~$ invoke export-records -f data.json
Can't find any collection named 'tasks'!

[StormTrooper]

Some more hacking around and got it working.

Needed to import the mysql data before installing inventree - all working now and no errors.

If I do it the other way round, ie. install inventree and get it to create a new DB, then drop the DB and import the old DB then it gives me errors.

[matmair]

So did you export from dev to stable? Interesting that that worked

[StormTrooper]

Yes, my dev was on 0.15.0 dev (16 April 2024) and exported to stable (0.15.0)

[matmair]

Ok maybe we should make the docs clearer that you should update your dev instance to stable, then export and start on the same stable version again. The data format can fluctuate between versions.
Good to know it works nonetheless, thank you for the feedback!