Changes between Initial Version and Version 1 of Ticket #12990, comment 25


Ignore:
Timestamp:
05/27/11 13:49:55 (12 years ago)
Author:
ShawnMilo
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #12990, comment 25

    initial v1  
    11I'd like to see this as well, because we use a JSON field frequently. I think the argument against that searching JSON in a queryset is poor design is a straw-man argument. I haven't heard anyone ask for a JSON field with this in mind. It's just convenient to store serialized data to avoid unnecessary auxiliary storage and proliferation of extra fields and models.
    22
    3 Having a canonical JSON field is better than people implementing their own, in my opinion, because it makes it provides consistency across projects without needing to copy/paste code into each no project.
     3Having a canonical JSON field is better than people implementing their own, in my opinion, because it makes it provides consistency across projects without needing to copy/paste code into each new project.
Back to Top