Ruby on Rails: models that do not have a table
Posted
by randombits
on Stack Overflow
See other posts from Stack Overflow
or by randombits
Published on 2010-04-08T00:16:57Z
Indexed on
2010/04/08
0:23 UTC
Read the original article
Hit count: 700
ruby-on-rails
|ruby
What's the best way to create a model in Ruby on Rails that doesn't have an underlying implementation in as far as a database table goes? It's very common to write classes that perform behavior on a particular problem domain, yet can use some of the benefits that ActiveRecord has such as validation.
Is it best to just create it as a module or helper? What is the best practice here?
© Stack Overflow or respective owner