AWS aurora-dsql documentation change
Summary
Changed 'CACHE' to 'cache' in headings and text, and updated 'IDENTITY' to 'identity columns' throughout
Security assessment
Terminology standardization without security content. The cache discussion remains operational guidance without security implications.
Diff
diff --git a/aurora-dsql/latest/userguide/sequences-identity-columns-working-with.md b/aurora-dsql/latest/userguide/sequences-identity-columns-working-with.md index 4aedcddf5..e60e700d4 100644 --- a//aurora-dsql/latest/userguide/sequences-identity-columns-working-with.md +++ b//aurora-dsql/latest/userguide/sequences-identity-columns-working-with.md @@ -5 +5 @@ -Choosing identifier typesChoosing a CACHE size +Choosing identifier typesChoosing a cache size @@ -17 +17 @@ See the Important callout on the [CREATE SEQUENCE](./create-sequence-syntax-supp -Amazon Aurora DSQL supports both UUID-based identifiers and integer values generated using sequences or `IDENTITY` columns. These options differ in how values are allocated and how they scale under load. +Amazon Aurora DSQL supports both UUID-based identifiers and integer values generated using sequences or identity columns. These options differ in how values are allocated and how they scale under load. @@ -21 +21 @@ UUID values can be generated without coordination and are well suited to workloa -Sequences and `IDENTITY` columns generate compact integer values that are convenient for human-readable identifiers, reporting, and external interfaces. When numeric identifiers are preferred for usability or integration reasons, consider using a sequence or `IDENTITY` column in combination with UUID-based identifiers. When integer sequence or identity values are required, choosing an appropriate cache size becomes an important part of workload design. See the following section for guidance on choosing a cache size. +Sequences and identity columns generate compact integer values that are convenient for human-readable identifiers, reporting, and external interfaces. When numeric identifiers are preferred for usability or integration reasons, consider using a sequence or identity column in combination with UUID-based identifiers. When integer sequence or identity values are required, choosing an appropriate cache size becomes an important part of workload design. See the following section for guidance on choosing a cache size. @@ -23 +23 @@ Sequences and `IDENTITY` columns generate compact integer values that are conven -## Choosing a CACHE size +## Choosing a cache size @@ -25 +25 @@ Sequences and `IDENTITY` columns generate compact integer values that are conven -Selecting an appropriate `CACHE` value is an important part of using sequences and `IDENTITY` columns effectively. The `CACHE` setting determines how identifier allocation behaves under load, influencing both system throughput and how closely values reflect allocation order. +Selecting an appropriate cache value is an important part of using sequences and identity columns effectively. The cache setting determines how identifier allocation behaves under load, influencing both system throughput and how closely values reflect allocation order.