GitHub user lkskjjk added a comment to the discussion: [DISCUSS] [GSoC 2026] Proposal on Enhancing Multi-Database AT Mode Support for Apache Seata-Go
My decision is to use godror based on the following research: * Production Maturity: godror is built upon the official Oracle ODPI-C layer. In Seata's AT mode, we rely heavily on stable transaction boundary control and precise handling of Oracle-specific types (e.g., CLOB, TIMESTAMP). godror has proven robust in large-scale financial deployments where go-ora currently lacks comparable stability for complex transaction scenarios. * LOB/Complex Type Handling: The AT mode’s Before/After Image generation often involves large objects. godror’s direct integration with the native Oracle client allows for efficient, chunked streaming of LOB data, whereas go-ora would struggle with memory overhead in high-concurrency environments. * Transaction Boundary Control: godror provides finer-grained control over session-level parameters (e.g., NLS settings), which is critical for ensuring that date and timestamp precision remains constant across different client locales—a frequent pain point in distributed systems. GitHub link: https://github.com/apache/incubator-seata-go/discussions/1110#discussioncomment-16601298 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
