Document that a non-PK column shouldn't be specified as the id-column…

… [HZ-4211] (#1014) * documented that a non-PK column shouldn't be specified as the id-column * Update docs/modules/mapstore/pages/configuring-a-generic-mapstore.adoc Co-authored-by: rebekah-lawrence <[email protected]> * changed primary key to unique key --------- Co-authored-by: rebekah-lawrence <[email protected]>
hazelcast · Feb 27, 2024 · f2b8b68 · f2b8b68
1 parent 67afb5b
commit f2b8b68
Showing 1 changed file with 2 additions and 2 deletions.
diff --git a/docs/modules/mapstore/pages/configuring-a-generic-mapstore.adoc b/docs/modules/mapstore/pages/configuring-a-generic-mapstore.adoc
@@ -257,7 +257,7 @@ mapConfig.setMapStoreConfig(mapStoreConfig);
 ====
 
 |[[id-column]]`id-column`
-|Name of the column that contains the primary key.
+|Name of the column that contains the primary key. Do not specify a column without a unique key constraint as the id-column.
 
 |id
 |
@@ -381,7 +381,7 @@ You can use any database as the MapStore backend as long as you have its Hazelca
 
 Officially supported backend databases:
 
-- MySQL, PostgreSQL (it uses JDBC SQL Connector).
+- MySQL, PostgreSQL, Microsoft SQL Server, Oracle (it uses JDBC SQL Connector).
 - MongoDB (make sure you have `hazelcast-jet-mongodb` artifact included on the classpath).
 
 == Related Resources