You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Auto tables currently lack canonical names, which means that during synchronization, the system relies solely on matching dbName. This approach is flawed, both in the context of potential changes to dbNamingPolicy and possible modifications to the dbName values stored in the database structure. Such changes might occur, for instance, if we decide to normalize these dbName values to lowercase or if we aim to support future backward compatibility when running on an older version of the platform.
Additionally, at the reflection level, table canonical names are not stored (probably due to their absence in auto tables). Instead, identification is performed using dbName, which could also lead to issues if these dbName values are changed.
The text was updated successfully, but these errors were encountered:
Auto tables currently lack canonical names, which means that during synchronization, the system relies solely on matching
dbName
. This approach is flawed, both in the context of potential changes todbNamingPolicy
and possible modifications to thedbName
values stored in the database structure. Such changes might occur, for instance, if we decide to normalize thesedbName
values to lowercase or if we aim to support future backward compatibility when running on an older version of the platform.Additionally, at the reflection level, table canonical names are not stored (probably due to their absence in auto tables). Instead, identification is performed using
dbName
, which could also lead to issues if thesedbName
values are changed.The text was updated successfully, but these errors were encountered: