My application requires configurable columns, and the headings of these columns are configured in the beginning, if the connection database I would have made the normal column for this requirement in the table like code, codeb etc. Because it helps in queuing on these columns (code A = 11), it also helps to display values (if the column code And stores the value), Lake And now I should use the non-related database datastore (and I'm new to it), should I follow the same old approach or should I use the structure (key value pair) type structure
these columns There will be a lot of filters on it. Please suggest that
what you have described in the classic scenario for the key-value database Here's the limit here that you will not have many set-based tools that you are using.
Most KV Databases are really good at loading a "record" or a small set of them. However, they do not do any good to load anything, which may require any involvement. Given that you are using AppEngine, you probably appreciate this limit. But it is worth saying.
As an important note, all KV's database will allow you to "not select from any column". Many KV stores actually allow only one primary key to choose if you take a look at MongoDB, you will find that you can ask from any column that looks like an essential feature.
Comments
Post a Comment