title: Resolving a class name conflict in a Rails application
body: <p>I have been building a Rails application that performs accounting functionality. As part of this, I have a model with the class name <code>Transaction</code>. So far so good, I have been building this functionality for a month or so, and everything is working as expected.</p>
  
  <p>Until now...</p>
  
  <p>I have just discovered some older reporting functionality that was developed months ago using the Ruport library has stopped working. It appears that Ruport, when generating PDFs, requires a library that also has a class/module named <code>Transaction</code>.</p>
  
  <pre><code>TypeError in Admin/team reportsController#generate
  Transaction is not a module
  
  ...
  
  This error occurred while loading the following files:
    pdf/writer
    transaction/simple
  </code></pre>
  
  <p>So, I'm looking for a quick fix here. One that hopefully doesn't involve renaming my <code>Transaction</code> model and refactoring the last few weeks worth of code.</p>
  
  <p>Looking forward to some clever suggestions :)</p>