Error 500 database with relational after upgrade

If update to 1.3.2 from 1.3.1 need to run migrate command?

TL;DR

User is experiencing an error 500 with a relational database after upgrading. There was a problem with the migration code in version 1.3.2 that caused the id of the relation to be null. Version 1.3.3 fixes the migration code. To fix the error, you need to restore from a backup or recreate your collections. You can downgrade to version 1.3.1 and then upgrade to 1.3.3 to fix the issue. If you can't see the data, you can't back it up. After backing up the database, delete the Relationship attribute and recreate it. Make sure to

Actually you're correct. My bad, sorry for the mistake.

From my walking through the code it seems like no change will happened when migrating the same DB version.

In the url can you add /settings to the end of it, and let us know what Document Security settings are?

Yes, I can

After you've done the backup you can try to delete Relationship attribute and recreate it.

Be sure again to backup all your database before, so you'll be able to go back in any case.

I cant's see the data, so I cant backup

I mean backing-up the database using Steven gist:

https://gist.github.com/stnguyen90/fee636ff652b8ecbf761935b2aa254fb

Okay, I’ll try it

yes, you need to run the migrate command. did you not?

Is it require to run migrate in Minor upgrades?

typically, not, but this time it's required

I have the same error too,

😬

@hamed @bluesky, I think y'all will have to restore from backup 😬

and downgrade 😬

There was a problem with the migration that messed up the relationships metadata. if you can restore to 1.3.1, you can upgrade to 1.3.3, instead, now (and run the migrate command)