I have a database that holds information related to events. This is more of an internal project but I guess once proof of concept is complete it could be usable to others. That being said I would like to future proof it for higher volume use.
Back to the question. This event collection will be updated as more information becomes available. So initially it could just be a title and date with other information such as location, etc becoming available over time. Normally I would setup a form collect the data and update at one time. I feel like in this instance it’s going to need to be one field at a time as it becomes available.
I’m a little concerned about the API call frequency. I’m using Xano at this point, but my lack of knowledge is probably hindering my ability to develop this in the most efficient manner. Will this require a patch API call for each field in the collection? I’m concerned doing one post call and then reusing it will over write data with a null value if the field is not needed for the update. Maybe something that has already previously been populated. Maybe I’m just thinking about this in the wrong manner.
Any insight would be greatly appreciated.