Forum: Ruby on Rails Collision between Transaction::Simple and ActiveRecord

Announcement (2017-05-07): is now read-only since I unfortunately do not have the time to support and maintain the forum any more. Please see and for other Rails- und Ruby-related community platforms.
1d3833344f867728be21a476f9fd018a?d=identicon&s=25 Calle Dybedahl (Guest)
on 2007-01-30 10:46
(Received via mailing list)
I want to use PDF::Writer from Rails. Which works, basically, except
for the ugly error messages when PDF::Writer loads
Transaction:.Simple, and it tries to define its own constants -- which
have already been defined once by the copy of Transaction::Simple
that's wodged into a corner of ActiveRecord.

Now, I can play silly buggers in my cron scripts and such to filter
out those error messages, but that's quite a lot of work to get around
an exceptionally bad design decision in ActiveRecord. So I'd like to
know if there are any reasonable ways to either get ActiveRecord to
use the real gem-installed Transaction::Simple, or to get PDF::Writer
to use the one included in ActiveRecord?

(Problem exists with Rails 1.1.6, on at least RHEL4, FreeBSD 6.3 and
MacOS X 10.4.8).
Calle Dybedahl -*-
This topic is locked and can not be replied to.