Re: Reg:- Data Modelling For Hierarchy Data

2017-06-09 Thread @Nandan@
t; *Sent:* vendredi 9 juin 2017 10:27 > *To:* Jacques-Henri Berthemet <jacques-henri.berthe...@genesys.com> > *Cc:* user@cassandra.apache.org > *Subject:* Re: Reg:- Data Modelling For Hierarchy Data > > > > Hi, > > Yes, I am following with single Users table. > &g

RE: Reg:- Data Modelling For Hierarchy Data

2017-06-09 Thread Jacques-Henri Berthemet
ubject: Re: Reg:- Data Modelling For Hierarchy Data Hi, Yes, I am following with single Users table. Suppose my query patterns are:- 1) Select user by email. 2) Select user by user_type 1st query pattern will satisfy the Users table, but in the case of second query pattern, either have

Re: Reg:- Data Modelling For Hierarchy Data

2017-06-09 Thread @Nandan@
Hi, Yes, I am following with single Users table. Suppose my query patterns are:- 1) Select user by email. 2) Select user by user_type 1st query pattern will satisfy the Users table, but in the case of second query pattern, either have to go with another table like user_by_type or I have to create

RE: Reg:- Data Modelling For Hierarchy Data

2017-06-09 Thread Jacques-Henri Berthemet
Hi, According to your model a use can only be of one type, so I’d go with a very simple model with a single table: string email (PK), string user_type, map attributes user_type can be Buyer, Master_Seller, Slave_Seller and all other columns go into attribute map as long as all