ios - How large of a String should generally be stored in one core data entity attribute? -


how large of string should stored in 1 core data entity attribute?

at point should string broken multiple attributes or multiple entities relationships?


i don't know how space-dense strings are. imagine wanting save text 100 pages 1 attribute: string.

other difficulties of querying core data specific attributes, cause problems?

basically, how large of string large store attribute?

whether use 1 attribute or multiple attributes depends on whether data logically single value or multiple values. is, depends entirely on structure of data, not size.

however, excessively large values, makes more sense save data in separate file , keep file name in core data. when need full value, file name core data , load file contents.

the advantage of approach avoid reading entire value memory when don't need it-- example, getting entire 100 page string value in memory when care other fields (like "title" field or something). splitting data multiple attributes doesn't fix problem , creates extra, unnecessary complexity.


Comments

Popular posts from this blog

c++ - Difference between pre and post decrement in recursive function argument -

php - Nothing but 'run(); ' when browsing to my local project, how do I fix this? -

php - How can I echo out this array? -