From 84fa17644ecafcfc72e936c147bb35a6f9e48961 Mon Sep 17 00:00:00 2001 From: signedav Date: Fri, 24 Nov 2023 10:20:23 +0100 Subject: [PATCH] changeme --- docs/background_info/oid_tid_generator.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/background_info/oid_tid_generator.md b/docs/background_info/oid_tid_generator.md index cb134c3d3..b1c08396c 100644 --- a/docs/background_info/oid_tid_generator.md +++ b/docs/background_info/oid_tid_generator.md @@ -81,7 +81,7 @@ As *local identification part* Model Baker suggests the counter provided by the In the QGIS Project the default value expression for `t_ili_tid` is therefore this: ``` -'ch100000' || lpad( T_Id, 8, 0 ) +'changeme0' || lpad( T_Id, 8, 0 ) ``` #### `ANYOID` @@ -105,7 +105,7 @@ In the QGIS Project the default value expression for `t_ili_tid` is therefore th |---|---| | INTERLIS.UUIDOID | `uuid('WithoutBraces')` | | INTERLIS.I32OID | `t_id` | -| INTERLIS.STANDARDOID | `'ch100000' \|\| lpad( t_id, 8, 0 )` | +| INTERLIS.STANDARDOID | `'changeme0' \|\| lpad( t_id, 8, 0 )` | | INTERLIS.ANYOID | `'_' \|\| uuid('WithoutBraces')` | | City_V1.TypeID | `'_' \|\| uuid('WithoutBraces')` | | not defined | `'_' \|\| uuid('WithoutBraces')` | @@ -142,4 +142,4 @@ When the OIDs are not UUIDs but e.g. `STANDARDOID`s instead, it's not possible t When resetting the T_Id (Sequence) value one needs to be careful, because it's used for the technical sequence id (used for foreign keys etc.) as well. This means it should not conflict with the `t_id`s of objects already existing. That's why it should only be decreased if you really know what you are doing. -The conflicts are handled differently depending on the database system. On PostgreSQL you would encounter a duplicate key violation while on GeoPackage it would take the next available autogenerated t_id, but since it's not known on creating the TID (OID) it would break those values (e.g. write to it `ch100000Autogene`.) +The conflicts are handled differently depending on the database system. On PostgreSQL you would encounter a duplicate key violation while on GeoPackage it would take the next available autogenerated t_id, but since it's not known on creating the TID (OID) it would break those values (e.g. write to it `changeme0Autogene`.)