Formbuilder Changing Schema

[JoshLewis]

Finally getting around to using form builder beyond just testing outputs and possibilities. But before filling in data wanted to check in if it's okay to change the formbuilder schema over time? For example for now jr_additions currently has two text fields for storing image IDs to act as secondary and third primary images:

{
    "title": "",
    "type": "object",
    "properties": {
      "image": {
        "title": "Image 1 ",
        "type": "string",
        "options": {
            "input_width": "15em"
        }
      }
      ,"image2": {
        "title": "Image 2 ",
        "type": "string",
        "options": {
            "input_width": "15em"
        }
      }
    }
}

At first was tempted to simply use two integer field types but then figured perhaps it makes more sense to apply all non searchable fields (that are simple) to a single formbuilder field. On one hand this will create less database columns per listing. But is it more resource intensive (speed/performance) to use formbuilder instead of integer fields? Not worried about micro seconds in this scenario. 😉

Edited September 8, 2021 at 08:33 PM by JoshLewis

[Alejandro]

This section is only visible with a valid subscription. If you have a valid subscription, please login.

[JoshLewis]

This section is only visible with a valid subscription. If you have a valid subscription, please login.

[Alejandro]

This section is only visible with a valid subscription. If you have a valid subscription, please login.

[JoshLewis]

This section is only visible with a valid subscription. If you have a valid subscription, please login.