Tag Info

New answers tagged

0

As NoSQL databases typically do not support joins, they expect you to store the data in de-normalized form. (So, throw the codd normalization rule book away. Just kidding). In this case, the thrid table better have the values duplicated something like (orderid, ordertime, [itemnames], waitername, orderserviced yes/no, servicetime, ...). itemnames can be a ...


0

I think that you don't need table "Ranking". Instead create a function that calculate ranking over different fields.


0

I would separate the bets from the results so there is redundancy but your querying on results is much easier - all the data is there, and you can incorporate smarts and filters: Table Bets (populated by the users via client app) - objectId (String, managed by Parse) - gameId (Pointer<Games>) - userId (Pointer<User>) - bet ...


0

The two NoSQL DBs that come to mind when mentioning cross datacenter replication ("master-master replications around the world") are: Cassandra Couchbase Both of them seem to have fairly decent cross datacenter replication abilities, so which you should go with should be decided upon in a different manner. If you want a KV-Store (where you can simply ...


0

We are doing something very similar at my place and this very question was in my head for a while a few weeks back. After noticing that logs were consuming 98% of our DBs in SQL Server I did some research on how we should handle this problem. It all depends on the structure of your logs but our logs are not really relational so storing them in a RDBMS and ...


0

You can also set the bin to null to delete it. http://www.aerospike.com/docs/client/java/usage/kvs/write.html#delete-a-bin



Top 50 recent answers are included