Replies: 1 comment
-
I can confirm that the upgrade from 3.7.8 to 4.1.11 works fine without any changes to the database. It appears that a truly safe re-encoding from SQL_ASCII to UTF8 is a bit tricky, so I'll probably spin up a test container at some point to play with that. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
The below sounds like it's related to the breaking collation change that came with 4.2, so I will shortly revert using my pre-upgrade snapshot and have a go at going only as far as 4.1 if I can't otherwise fix this.
This is using a git release upgrade with Ubuntu 24.04.1, Postgresql 14, python 3.12.3.
My best reading of the django (which I'm not really familiar with) documentation is that, by default at least, it is much happier with all text in the database using UTF8. I can't see any indication that netbox overrides this, but did want to confirm that I'm not missing the point here somehow.
And, yes, the current server_encoding value for my netbox database is "SQL_ASCII".
Beta Was this translation helpful? Give feedback.
All reactions