16

JSON data type for fields

Native lists and dicts would be nice to have. We store a lot of things on entities, and it doesn't always make sense to have a separate field for every value.

 

8 comments

  • Avatar
    Nephi Sanchez Official comment

    Hi Everyone,

     

    Thanks for the comments!  Curious if you all could elaborate on how your workflows would change if there was a JSON type field, v. a text field?

     

    cheers,
    Nephi

     

     

  • 0
    Avatar
    Kym Watts

    +1 , we currently store dictionary in string fields in shotgun, native support would be awesome.

  • 1
    Avatar
    Pete Addington

    I LIKE. Being able to manifest JSON custom data natively in a field type without serlialization would be very powerful. I am currently pushing this into text fields. Entity data storage outside the publish outputs really opens up highly nuanced tracking possibilities.

    Whilst this is an option, you have to ask support to enable it on a field. This does not help the workflow of being able to add and remove for different projects and when setting up new workflows. 

  • 0
    Avatar
    Jesse Lucas

    We are also pushing JSON into Text fields.

  • 0
    Avatar
    Baptiste

    +1

  • 0
    Avatar
    Benoit Leveau

    We also store JSON into text fields.

    Our main use case is for storing the list of delivery presets along with their settings for each project. We could use a custom entity for that, and each setting would be a field on the entity, but using JSON strings has helped us iterate through different versions more easily. It's hard to make entities evolve without filling up with every field that was ever used.

  • 0
    Avatar
    Tony Aiello

    One thing we wanted to do with a JSON field was store the EXIF data (creation datetime, etc) for *all* the individual images (camera shots) in a clip.

    But I think the main savings of JSON vs text field is being able not have to transmogrify text <> JSON <> python dictionary.  Either way the idea is to be able to create custom code objects that can be stored in the Shotgun db without having to add lots of fields to the db schema, especially when one is iterating on the data structure of the object.

  • 0
    Avatar
    Patrick Macdonald

    +1 ! Has there been any movement to having this implemented? 

Please sign in to leave a comment.