(Apr-10-2020, 07:52 AM)buran Wrote: First of all - I don't have information about the whole picture, but even based on the information you have provided so far, I would go for separate table. It's the proper DB design.
As to the performance/cost of INSERT vs. UPDATE (I assume you will either insert new records or update existing by concatenating new values to existing string, right?) - it's really a tricky question and depends on many factors, so I definitely cannot give a definitive answer. Probably you can run comparison test. I would expect that inserts in separate table would be less CPU intensive, though.
Thank you. I will go for a separate table as it is the correct way to design a database.
The insert and update queries will likely be more CPU intensive than separating a string, but, it's not like I am storing thousands of values. 10 at the most. So I may lose like 5 minutes of battery life out of a total of three hours. So that's fine.