Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

I cannot see schemas after upgrading #3238

Closed
spapas opened this issue Oct 10, 2023 · 3 comments
Closed

I cannot see schemas after upgrading #3238

spapas opened this issue Oct 10, 2023 · 3 comments
Labels
type: bug Something isn't working user reported Reported by a Mathesar user work: backend Related to Python, Django, and simple SQL

Comments

@spapas
Copy link
Contributor

spapas commented Oct 10, 2023

Description

After upgrading to latest version I can't see any of the schemas of the mathesar data database.

Expected behavior

To see the schemas. Do I need to do something more after upgrading ?

To Reproduce

I'm not really sure. I updated from the version I had to the latest version from the develop branch

Environment

  • OS: Centos 7
  • Browser: Chrome
  • Browser Version: Latest
  • Other info:

Additional context

This is what I see after login with the administrator:

image

Please notice that with the previous version I was seeing the schemas I had (and of course the schemas are there).

No errors on the backend console or js.

@spapas
Copy link
Contributor Author

spapas commented Oct 10, 2023

It seems that the issue was related to #3158 , the mathesar_database table contained garbage for the username and an empty db_name, It was fixed after I run

update mathesar_database set username='mathsar' db_name='mathesar_data'

My understanding is that it doesn't convert the MATHESAR_DATABASES env var to the correct values in the database.

@pavish
Copy link
Member

pavish commented Oct 10, 2023

@spapas Thanks for letting us know! Do you need any further help with this issue?

Regarding upgrades:

The develop branch contains unstable development code. It isn't fully tested and certainly not meant for installation and regular usage.

When upgrading, we recommend you to make use of our releases, which are more stable and tested (unless you prefer the latest dev code, in which case, we're glad to help sort out issues). Keep in mind that we're still in alpha, so there may be some breaking changes between releases.

@rajatvijay rajatvijay added work: backend Related to Python, Django, and simple SQL status: draft user reported Reported by a Mathesar user and removed status: triage labels Oct 10, 2023
@spapas
Copy link
Contributor Author

spapas commented Oct 10, 2023

No let's close it since it's working

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: bug Something isn't working user reported Reported by a Mathesar user work: backend Related to Python, Django, and simple SQL
Projects
No open projects
Development

No branches or pull requests

3 participants