Question

I m writing an application that communicates with a web API, which responds with JSON. Currently, I m translating the JSON objects to Java objects using gson (which is awesome, by the way).

Now, I want to store some of these objects in an SQLite database. However, they have lots of properties that would never be used in queries (i.e. I won t be ORDERing, WHEREing, or anything like that with those properties), so I feel it s unnecessary to create columns for all of them. What I m thinking of doing is:

Only have columns for the essential data that will be used when querying the database
Have one TEXT or BLOB column (which one do you recommend?) that stores the actual JSON, so I can recreate my Java object from it and access all the data.

This would both make my life easier and streamline my code (I would not have to write very different code when dealing with data from the API vs. data from the database).

然而,尽管我看不出底部,但我感觉到底鱼。

如果我使用这一技术,你会遇到什么样的麻烦?

Answer 1

我要谈的主要事情是依靠所储存/受伤害的JSON的结构来有效,因为它完全脱离了数据库。你们不能对可能的问题采取预防措施,但如果是神学家以 trip子的方式run倒或以其他方式破坏他们,那么你就会再 missing掉整个物体,而不只是一个无效或拖.的财产。如果这种风险是可以接受的,则可能是一种合理的技术。

友情链接