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
Currently, the Trunk database type feature in our system allows for convenient expansion of new database implementations based on a certain database. However, there is a limitation in that it does not support the extension of new data types on this basis.
To address this limitation, we need to enhance the Trunk database type feature to support the extension of new data types. This enhancement will provide users with greater flexibility in defining and utilizing custom data types within the framework.
Describe the feature you would like.
We can implement extended data types based on a specific DB without copying an implementation class (DialectMetaDataLoader), the modifier for implementing a class is usually final, so it has to be copied.
The text was updated successfully, but these errors were encountered:
Feature Request
Currently, the Trunk database type feature in our system allows for convenient expansion of new database implementations based on a certain database. However, there is a limitation in that it does not support the extension of new data types on this basis.
To address this limitation, we need to enhance the Trunk database type feature to support the extension of new data types. This enhancement will provide users with greater flexibility in defining and utilizing custom data types within the framework.
Describe the feature you would like.
We can implement extended data types based on a specific DB without copying an implementation class (
DialectMetaDataLoader
), the modifier for implementing a class is usually final, so it has to be copied.The text was updated successfully, but these errors were encountered: