What problem does it solve?
Oracle on JRuby with the oracle_enhanced adapter introduces many integration pitfalls compared with other databases: mismatched SQL dialect, DATE and CLOB handling differences, uppercase metadata, sequence-driven primary keys, and JRuby thread-based connection pool requirements. These issues lead to subtle bugs, performance regressions, and broken migrations if not handled with platform-specific patterns.
Core Features & Use Cases
- Oracle::Base conventions: guidance for creating an abstract base model with table_name_prefix, explicit primary_key, and sequence handling for EBS tables.
- Safe raw SQL & PL/SQL: patterns for bind-variable usage, anonymous PL/SQL blocks, and pagination using ROWNUM or FETCH/FIRST idioms.
- Type and connection handling: best practices for Oracle DATE vs time semantics, CLOB usage, NLS settings, JDBC properties, and pool sizing for JRuby + Puma.
- Use Case: implement a new model backed by an EBS table, write efficient cursor-based pagination, and debug oracle_enhanced adapter behavior in production.
Quick Start
Use the oracle-jruby skill to create an Oracle::Base model for table MTL_SYSTEM_ITEMS_B with an explicit primary key, example raw SQL using bind variables, and guidance on date and CLOB handling.
