Indeed. And to close out the discussion I can confirm that my FDW
implementations were using JSON columns, and the issue was resolved by
switching to JSONB instead.
On Sun, 18 Oct 2020, 14:40 Jason, wrote:
> looks like you got a response back, and there's more context in the linked
> ticket
looks like you got a response back, and there's more context in the linked
ticket too. tl;dr json is not jsonb, and django only works with the latter
On Thursday, October 15, 2020 at 10:02:30 AM UTC-4 shahee...@gmail.com
wrote:
> Thanks Jason, I filed
Thanks Jason, I filed https://code.djangoproject.com/ticket/32111#ticket.
On Thursday, 15 October 2020 at 12:51:22 UTC+1 Jason wrote:
> this is pretty interesting, and may be something to report to the devs at
> https://groups.google.com/g/django-developers, or open up a ticket at
>
this is pretty interesting, and may be something to report to the devs at
https://groups.google.com/g/django-developers, or open up a ticket at
https://code.djangoproject.com/ I don't see any tickets with the query
*jsonfield
foreign data* that are similar with your experience, so you may
Hi,
I have a Django model working fine under Django 3.0 (i.e. "Django<3.1")
which looks like this:
===
class Job(models.Model):
id = models.CharField(max_length=36, primary_key=True)
queue = models.CharField(max_length=40)
args = JSONField()
5 matches
Mail list logo