Gluesync SQL to NoSQL

Working with clustered indexes

Got a clustered index in a table or with no pre-defined primary keys? This option let’s you perform a manual definition of fields that will be then used as unique row identifiers in your table(s). Same applies if you’ve got a clustered index configuration on one of your tables.

Here following the configuration snippet you can use and customize in order to sync your table with both a clustered index and a single primary key config, Gluesync will use this keys in order to compose your unique row identifier instead of looking for a single Primary Key:

{
  ...
  "databasename": {
    "tableKeys": {
      "articles": ["id1", "id2"],
      "drivers": ["driver_unique_id"],
      "customers": ["customer_name", "customer_surname", "customer_age", "customer_id"]
    }
  },
  ...
}

Where:

databasename: refer to the name of the current Gluesync source database, for example "sybase" for Sybase ASE or "oracle" for any Oracle db. All lowercased;
tableKeys: is the object that represents the key-value pair list of tables and its columns that are composing your clustered index;