UPDATE! – Ruby ActiveRecord and Oracle: Auto Incrementing Primary Keys using Triggers
Well, it looks like this has been fixed in the latest versions of the Oracle enhanced adapter for ActiveRecord. It looks like there was a reorganization of the different components of the ActiveRecord/Adapter relationship that had originally led to this problem, according to the documentation submitted with the fix. Thanks to whomever was able to provide the patch; You just made my life a little bit easier.
Use this link to trackback from your own site.