I think the issue was by ths following , Storing the data as an integer does not have to hide your information, you can create a lookup table that relates the integer constants to their textual values, and then join them if you want to look at a textual representation of the data. On the other hand, unless you plan on storing many millions of rows, or have to process many thousands of transactions per second, the extra few bytes in your state table will probably not make that much of a difference.
How to store global statuses and/or parameters of an iOS app with Objective-C?
To fix this issue In IOS SDK, its depend on user requirement and understanding. While you can store flags in NSUserDefault or Create Global variable using extern or create AppDelegate variable with define property. thanks
How to pull results from database and store in numeric array
this one helps. Your question is labelled MySQL, but you say it's about SQLLite - please label correctly, it helps others! It sounds like you're implementing an Entity-Attribute-Value like solution. There are lots of discussions on this concept - this is one of the most useful.
will be helpful for those in need There is nothing wrong with your proposed table layout. It's not inefficient either. MySql is built for this. It can handle millions of rows of this kind of thing without breaking a sweat. Do add an autoincrementing id value to each row, to use as a primary key. You may wish to consider adding a timestamp column too.