Hi again, As a follow-up; if you have many `message_source_id`s you could also do:
CREATE TABLE integration_time ( message_source_id uuid, traffic_data_type varchar, integration_period varchar, integration_time timestamp, PRIMARY KEY (message_source_id,traffic_data_type,integration_period) ); This might enable you to easier be able to query all traffic_data_types and integration_periods for a single message_source_id without having to do a heavy query across all of your cluster. You'll have the same uniqueness property but this might, depending on your application, make things more debuggable. The flip side is that your cluster could be slightly more unbalanced if each message_source_id has a varied number of `integration_time`s. Just an idea, Jens On Tue, Jul 1, 2014 at 8:37 AM, Wim Deblauwe <wim.debla...@gmail.com> wrote: > Hi, > > I have the following table: > > CREATE TABLE integration_time ( > message_source_id uuid, > traffic_data_type varchar, > integration_period varchar, > integration_time timestamp, > PRIMARY KEY ((message_source_id,traffic_data_type,integration_period)) > ); > > I want the combination of (message_source_id, traffic_data_type, > integration_period) to be unique. Is this the correct way to do it (with > the double brackets) ? > > This table will be relative small, it just stores the last time something > was done in the application for that unique combination of those 3 > parameters. Worst case there will be 30000 rows in that table and they will > always be fetched by quering on the 3 parameters at the same time. > > regards, > > Wim >
