Hi Gautam, Sorry we haven't responded by now, but we've been busy today. We can only guarantee quick response times with a support contract, especially as those take more of our time these days. We can't always guarantee that you'll receive a response the same day or even within a few days of posting here on the community support list. Just depends on our availability. If you're interested in hearing what comes with support, I can send you some details and get a quote to you.
1) You can leave the CHARSET alone, but utf8 is preferred to latin1. You'll need to change them through an ALTER TABLE, if you want to change them, so that text can be re-encoded. Don't edit it in a database dump. 2) Without knowing the context of this error, I can't say for sure, but: 3) SECRET_KEY must be the same, or you will definitely have issues like #2. All repository credentials, tokens, etc. are encrypted based on your SECRET_KEY, and if it changes, things will break. Sometimes a different SECRET_KEY will still sort of decrypt the content, but to garbage (rather than the expected Unicode content). Christian On Wed, Aug 7, 2019 at 10:23 PM Gautam Bajaj <[email protected]> wrote: > Hi, > > Can someone please respond to my queries? thanks. > > -Gautam. > > On Wednesday, August 7, 2019 at 12:55:12 PM UTC+5:30, Gautam Bajaj wrote: >> >> Hi, >> >> We have upgraded the RB site from v2.5.6.1 to v3.0.15. For that we had >> imported the current DB to new test DB as per the doc: >> >> https://www.reviewboard.org/docs/manual/3.0/admin/installation/creating-sites/#creating-sites >> >> While created the new empty DB, we have used the default CHARSET as utf8. >> But in the imported DB tables, we observe that the CHARSET of the tables >> are still 'latin1' (because they were imported from current to new DB. In >> current DB of v2.5.6.1 CHARSET of tables were 'latin1'). >> >> The questions are: >> >> 1) Do we need to change the CHARSET of imported tables to utf8 or can we >> leave those tables as is with CHARSET=latin1? Please suggest. >> >> 2) What else we should be modifying/changing to ensure we do not get the >> below error? >> >> UnicodeDecodeError: 'utf8' codec can't decode byte 0xef in position 0: >> invalid continuation byte >> >> 3) I assume we need to keep the SECRET_KEY value in settings_local.py >> same as what we had in v2.5.6.1. Please confirm. >> >> Highly appreciate if you could respond to all 3 questions. >> >> Regrads, >> Gautam. >> > -- > Supercharge your Review Board with Power Pack: > https://www.reviewboard.org/powerpack/ > Want us to host Review Board for you? Check out RBCommons: > https://rbcommons.com/ > Happy user? Let us know! https://www.reviewboard.org/users/ > --- > You received this message because you are subscribed to the Google Groups > "Review Board Community" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/reviewboard/bf625787-77ef-45b3-b4e5-c48e7c9c3792%40googlegroups.com > <https://groups.google.com/d/msgid/reviewboard/bf625787-77ef-45b3-b4e5-c48e7c9c3792%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- Christian Hammond President/CEO of Beanbag <https://www.beanbaginc.com/> Makers of Review Board <https://www.reviewboard.org/> -- Supercharge your Review Board with Power Pack: https://www.reviewboard.org/powerpack/ Want us to host Review Board for you? Check out RBCommons: https://rbcommons.com/ Happy user? Let us know! https://www.reviewboard.org/users/ --- You received this message because you are subscribed to the Google Groups "Review Board Community" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/reviewboard/CAE7Vndkjn7LTDHTPK0evW7gb5v5uyJhKFjP%2B04WK59VDHUY6Kw%40mail.gmail.com.
