Defect #7826
closed
bigdecimal-segfault-fix.rb must be removed for Oracle
Added by Matthew Rupert about 13 years ago.
Updated about 12 years ago.
Description
config/initializers/bigdecimal-segfault-fix.rb was added to take care of the DoS bug in Ruby 1.8.7-p160 and all prior versions. As I am trying to get Redmine working with Oracle 11 I found that this file throws an error when I do the db migrate. Since I am using Ruby 1.8.7-p174 I simply removed bigdecimal-segfault-fix.rb.
Can there be some kind of check put in the file or installation to first check the Ruby version before attempting to apply the bigdecimal fix?
- Target version set to 1.4.0
Why not for 1.4.0 which will no more support Ruby 1.8.6 anymore?
As there are 1.8.6 and 1.8.7 ruby versions that fix this issue, we could remove this patch indeed.
BTW, Oracle is not officialy supported as I do not run tests with this DBMS. How does Redmine behave with it?
I try to relate every issue created about Oracle to #944 to keep a track of what could be done to support it; those issues are real even if closed as Invalid.
According to forums, people generally succeed to install Redmine with Oracle but this requires a few monkey patches (but not a lot); I specifically remember of issues related to 1 or 2 tables name length too long for an Oracle DB.
Adding support to Oracle (and why not, even if less often evoked, MSSQL) should not be that hard and would help integration/promotion of Redmine in companies tied by global contracts with Oracle (or Microsoft).
Moreover, I guess that setting up a CI with Oracle XE or SQL Server Express is possible.
- Status changed from New to Closed
- Assignee set to Jean-Philippe Lang
- Resolution set to Fixed
Fix removed in r8788.
How Oracle and MSSQL are supported in recent versions of Rails? Because they were in the early versions then they were not.
From what I've seen when I had a quick look 2 weeks ago, both ActiveRecord adapers are on GitHub and updated frequently and recently; I saw that SQL Server adapter was even already compatible with Rails 3.2.
I would say that supporting both of them is worth it, especially Oracle since it seems to be the most frequently asked for, but that's only my POV.
It would be great some attempts to make this working in Oracle without tweaks. I have 1.2.0 working with Oracle + JRuby and I fear to upgrade to latest because of possible new tweaks to be made.
- Related to Defect #4856: roadmap display crashes when a ticket has 'Estimated Time' too big added
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by 
Updated by