should I just use sql and serialize the nested stu...
# random
u
should I just use sql and serialize the nested stuff as json and call it a day?
l
We recently performed some evaluations on various SQL and no-sql solutions for a new android app. In the end we settled on room - there doesn't seem to be a compelling nosql solution at the moment
u
so json strings inside it for nonconforming data?
l
No, we are decomposing things down into different tables, with relationships between them, etc. This is so that we can query for things properly. If its just a big blob of json, then we won’t be able to access it by SQL
u
til: json1 extension