Dev.to
7/5/2026

How GBase 8a Handles Masked Columns in WHERE, GROUP BY, and Projections
Short summary
GBase 8a applies data masking only when sensitive columns are projected to clients or copied to other storage locations, displaying masked values while WHERE, GROUP BY, and ORDER BY operations use the original unmasked data. This design preserves query correctness and performance without exposing sensitive information to unprivileged users. The behavior aligns with Oracle Data Redaction policies and is essential for secure database design.
- •Data masking in GBase 8a only affects projected data, not filtering or aggregation operations
- •WHERE, GROUP BY, and ORDER BY clauses work on original unmasked values for logical correctness
- •Data migration (UPDATE/INSERT SELECT) writes masked values without inheriting masking policies
Generated with AI, which can make mistakes.
Is this a good recommendation for you?



