按说明更新2.0,打开workspaces页面报错

Docker-Compose方式安装,完全按说明更新2.0,打开网站正常,进入系统管理也正常
但是进入默认表格列表页,Loading刷不出来,Debug发现是/api/v2.1/workspaces/请求500错误
打开服务器日志,错误日志如下:

图片1

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

Traceback (most recent call last):
File “/opt/seatable/seatable-server-latest/dtable-web/thirdpart/django/core/handlers/exception.py”, line 34, in inner
response = get_response(request)
File “/opt/seatable/seatable-server-latest/dtable-web/thirdpart/django/core/handlers/base.py”, line 115, in _get_response
response = self.process_exception_by_middleware(e, request)
File “/opt/seatable/seatable-server-latest/dtable-web/thirdpart/django/core/handlers/base.py”, line 113, in _get_response
response = wrapped_callback(request, *callback_args, **callback_kwargs)
File “/opt/seatable/seatable-server-latest/dtable-web/thirdpart/django/views/decorators/csrf.py”, line 54, in wrapped_view
return view_func(*args, **kwargs)
File “/opt/seatable/seatable-server-latest/dtable-web/thirdpart/django/views/generic/base.py”, line 71, in view
return self.dispatch(request, *args, **kwargs)
File “/opt/seatable/seatable-server-latest/dtable-web/thirdpart/rest_framework/views.py”, line 509, in dispatch
response = self.handle_exception(exc)
File “/opt/seatable/seatable-server-latest/dtable-web/thirdpart/rest_framework/views.py”, line 469, in handle_exception
self.raise_uncaught_exception(exc)
File “/opt/seatable/seatable-server-latest/dtable-web/thirdpart/rest_framework/views.py”, line 480, in raise_uncaught_exception
raise exc
File “/opt/seatable/seatable-server-latest/dtable-web/thirdpart/rest_framework/views.py”, line 506, in dispatch
response = handler(request, *args, **kwargs)
File “/opt/seatable/seatable-server-latest/dtable-web/seahub/api2/endpoints/dtable.py”, line 198, in get
for view in shared_views_by_user:
File “/opt/seatable/seatable-server-latest/dtable-web/thirdpart/django/db/models/query.py”, line 274, in iter
self._fetch_all()
File “/opt/seatable/seatable-server-latest/dtable-web/thirdpart/django/db/models/query.py”, line 1242, in _fetch_all
self._result_cache = list(self._iterable_class(self))
File “/opt/seatable/seatable-server-latest/dtable-web/thirdpart/django/db/models/query.py”, line 55, in iter
results = compiler.execute_sql(chunked_fetch=self.chunked_fetch, chunk_size=self.chunk_size)
File “/opt/seatable/seatable-server-latest/dtable-web/thirdpart/django/db/models/sql/compiler.py”, line 1142, in execute_sql
cursor.execute(sql, params)
File “/opt/seatable/seatable-server-latest/dtable-web/thirdpart/django/db/backends/utils.py”, line 67, in execute
return self._execute_with_wrappers(sql, params, many=False, executor=self._execute)
File “/opt/seatable/seatable-server-latest/dtable-web/thirdpart/django/db/backends/utils.py”, line 76, in _execute_with_wrappers
return executor(sql, params, many, context)
File “/opt/seatable/seatable-server-latest/dtable-web/thirdpart/django/db/backends/utils.py”, line 84, in _execute
return self.cursor.execute(sql, params)
File “/opt/seatable/seatable-server-latest/dtable-web/thirdpart/django/db/utils.py”, line 89, in exit
raise dj_exc_value.with_traceback(traceback) from exc_value
File “/opt/seatable/seatable-server-latest/dtable-web/thirdpart/django/db/backends/utils.py”, line 84, in _execute
return self.cursor.execute(sql, params)
File “/opt/seatable/seatable-server-latest/dtable-web/thirdpart/django/db/backends/mysql/base.py”, line 71, in execute
return self.cursor.execute(query, args)
File “/opt/seatable/seatable-server-latest/dtable-web/thirdpart/MySQLdb/cursors.py”, line 206, in execute
res = self._query(query)
File “/opt/seatable/seatable-server-latest/dtable-web/thirdpart/MySQLdb/cursors.py”, line 319, in _query
db.query(q)
File “/opt/seatable/seatable-server-latest/dtable-web/thirdpart/MySQLdb/connections.py”, line 259, in query
_mysql.connection.query(self, query)
django.db.utils.OperationalError: (1054, “Unknown column ‘dtable_view_user_share.shared_name’ in ‘field list’”)

你的数据库没有按照说明来升级吧。

按说明执行了seatable.sh upgrade-sql 2.0
提示了[Warning] Using a password on the command line interface can be insecure. 后正常结束了

如果再次执行也提示不能再次执行了,修改重复

怎么确定执行是不是成功呢?

谢谢,解决了,把更新的SQL按版本彻底从低到高执行一遍,就Ok了
Thanks