summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorPjotr Prins2021-12-31 16:31:16 +0100
committerPjotr Prins2021-12-31 16:31:16 +0100
commitaa71edbc3f96e99b17c9e831dec67a77f104f162 (patch)
treebab422b202646feaafebb376f32b017ac045c469
parentda244b89c3ab716749e5d893efd418a3ef0155bc (diff)
downloadgn-gemtext-aa71edbc3f96e99b17c9e831dec67a77f104f162.tar.gz
innodb
-rw-r--r--topics/systems/mariadb/ProbeSetData.gmi2
1 files changed, 2 insertions, 0 deletions
diff --git a/topics/systems/mariadb/ProbeSetData.gmi b/topics/systems/mariadb/ProbeSetData.gmi
index 0e077ad..9fb8306 100644
--- a/topics/systems/mariadb/ProbeSetData.gmi
+++ b/topics/systems/mariadb/ProbeSetData.gmi
@@ -106,6 +106,8 @@ MariaDB [db_webqtl]> select max(Id) from ProbeSetData;
For StrainID MediumInt is a better fit with unsigned range is 0 to 16777215 and Id should be a INT (instead of BIGINT for the time being). That will make the table+indices smaller and faster.
+When a value overflows MariaDB will throw an error. So even if we grow out of values we can quickly resize the table in, say, 10 years. That is, if we are still using SQL.
+
### Check GN1,2,3 code for use of table
```