Project: datalens
81 entity types
Matrix/Architecture/Design Decision: Skip Column/Table Name Translation
DesignDecisionArchitecture

Design Decision: Skip Column/Table Name Translation

Decided to keep column and table names unchanged to maintain data integrity and avoid query errors, using prompts to instruct language responses instead.

Attributes
labelsEntity,DesignDecision
rationaleThe decision to skip column and table name translation was made to maintain data integrity, ensuring that column and table names stay unchanged for query accuracy, data exports, and compatibility with existing schemas. This approach simplifies the process by avoiding complex dynamic renaming during data processing, thereby reducing potential errors and ensuring consistent reference to data sources.
alternatives consideredTranslating table and column names to the target language or format was considered but rejected due to the risk of data corruption, broken queries, and loss of reference consistency. Instead, prompts are designed to instruct the system to respond in the desired language without altering the underlying schema.
decided byArchitectural team consensus based on best practices for data integrity and system simplicity.
decision date2026-03-03
tier2
Relationships0 connections
Loading graph...
Related Entities