zxs1633079383 commented on issue #36978: URL: https://github.com/apache/shardingsphere/issues/36978#issuecomment-3479441270
@terrymanu ### š Thanks @terrymanu for the detailed and professional analysis! Really appreciate your deep dive into this issue and the clear step-by-step breakdown. Your explanation about the PostgreSQL custom type flow and the planned solution (from `varbit` fix ā generic UDT parser framework ā enhanced type resolution) is extremely insightful and well-structured. I especially like the **Phase 2 + Phase 3** plan ā introducing a `PostgreSQLUDTValueParser` and a `UDT_GENERIC` fallback feels like the right direction to make ShardingSphere more extensible and future-proof for PostgreSQLās custom ecosystem. Iāll follow your guidance: - Prepare a PR branch (`fix/postgresql-custom-types`) - Implement and test based on your design - Provide real PostgreSQL validation (varbit + user-defined types) Thanks again for your time and effort ā this is an awesome reference for contributors like me to understand how to extend ShardingSphereās type parsing mechanism. š _Respect from the trenches of debugging PostgreSQL custom types š_ -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
