Rails database requirements more or less boil down to tables, indexes, and CRUDs.
Everything that provides these functions should be able to serve as a back-end for a Rails application, and Oracle certainly does these parts somewhere in the midst of an extensive set of bloat functions . If you can use ActiveRecord migrations, you donβt need to worry too much about platform-specific aspects.
- ActiveRecord ( activerecord\lib\active_record\connection_adapters, ) , , , Oracle, , id.
Oracle , , , , , MySQL.
Oracle , , , . , , , "" , .
Rails/Oracle, OracleXE , - " " ( - , , , ) .
EDIT: activerecord-oracle_enhanced-adapter ( ) , / ( Oracle : DATE). , ...