removing decimal with precision and decimal count

common/proto/table_definition.proto

@@ -275,15 +275,12 @@ message ColumnDefinition {
   //   DATE
   //   DURATION
   //   PERIOD
-  //   DECIMAL(p,s) → NUMERIC(p,s)
   //   LINK(table) → BIGINT referencing that table in the same profile, indexed
   //                 automatically. A table may hold several links to the same
   //                 target as long as the columns are named differently.
   //   FROM(link.source) → stored, read-only copy of an atomic column reached
   //                 through another column in this definition whose type is
   //                 LINK(...). SQL type and money metadata are inferred.
-  // DECIMAL args must be integers (no sign, no dot, no leading zeros);
-  // s ≤ p and p ≥ 1.
   string field_type = 2;
 
   // MONEY rounding applied before a value is stored.
@@ -530,10 +527,7 @@ enum ColumnTypeSpelling {
   // The name is the whole spelling: "text", "money", "gtin_13".
   COLUMN_TYPE_SPELLING_BARE = 0;
 
-  // The name takes a precision and a scale: "decimal(12,3)". Precision must be
-  // at least 1 and scale no greater than precision; neither may carry a sign,
-  // a decimal point, or leading zeros.
-  COLUMN_TYPE_SPELLING_DECIMAL = 1;
+  reserved 1;
 
   // The name takes the name of another table in the same profile:
   // "link(adresar)". The column holds that table's id, and the server creates
@@ -558,8 +552,7 @@ message ListColumnTypesResponse {
     string name = 1;
 
     // Underlying PostgreSQL type the logical type maps to (e.g. "NUMERIC").
-    // Empty when `compound` is true. For COLUMN_TYPE_SPELLING_DECIMAL this is
-    // the unparameterised type; the declared precision and scale are appended.
+    // Empty when `compound` is true.
     string sql_type = 2;
 
     // False for types the server generates on its own and rejects when a client