Context Navigation

Changes between Version 1 and Version 2 of Ticket #35268

Timestamp:: Mar 4, 2024, 5:04:08 AM (7 months ago)
Author:: Mariusz Felisiak
Comment:: Hi, I don't think you've explained the issue in enough detail to confirm a bug in Django. Please reopen the ticket if you can debug your issue and provide details about why and where Django is at fault (or a sample project that reproduced the issue). If you're having trouble understanding how Django works, see TicketClosingReasons/UseSupportChannels for ways to get help.

Ticket #35268
- Property Component Uncategorized → Database layer (models, ORM)
- Property Resolution → needsinfo
- Property Status new → closed
- Property Summary Error in Django Migration in PostgreSQL : UnicodeDecodeError during 'python manage.py migrate' → Migrations raise UnicodeDecodeError on PostgreSQL.

-              v1
+              v2
 When running the command 'python manage.py migrate' in a Django project, a UnicodeDecodeError occurs during the migration process.
  The error trace indicates that the issue is related to decoding a byte (0xbb) at position 79, and the problematic code is within the PostgreSQL database backend connection setup. The error originates from the 'psycopg2' library, and the specific context points to a Unicode decoding problem in the 'data_handler.py' file. The error disrupts the migration process and prevents the successful execution of the command.
+The error trace indicates that the issue is related to decoding a byte (0xbb) at position 79, and the problematic code is within the PostgreSQL database backend connection setup. The error originates from the 'psycopg2' library, and the specific context points to a Unicode decoding problem in the 'data_handler.py' file. The error disrupts the migration process and prevents the successful execution of the command.
 Here is also Database Setting in  my  Django Project :
+{{{
 DATABASES = {
     'default': {
 …
+    }
+}
+}}}