Changes between Initial Version and Version 1 of Ticket #32135, comment 2
- Timestamp:
- Oct 23, 2020, 3:13:00 PM (4 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #32135, comment 2
initial v1 1 1 Update: I see this may be a duplicate (or at least closely related to): https://code.djangoproject.com/ticket/31973 and https://code.djangoproject.com/ticket/32111 2 2 3 In th isexisting tickets, the bugs are closed with the assertion "It looks that you use json instead of jsonb datatype in your database, which is not supported."3 In these existing tickets, the bugs are closed with the assertion "It looks that you use json instead of jsonb datatype in your database, which is not supported." 4 4 5 5 Is there a reason `json` was permitted via workaround in 3.0 and appears forcefully disabled in 3.1? Is there another option suggested for Django applications that need to preserve the sequence of similar data structures, and where a format like JSON appears to be the cleanest & simplest option for doing so?