Imagine a small vendor needing to process credit card information but
not wanting, in any cases, to store the data locally. Ideal case for
ActiveRecord methods without a database persistance.
On Jun 8, 12:47 pm, djolley wrote:
> > Does that help?
>
> Yes, it does. So, I think that you are sayi
> Does that help?
Yes, it does. So, I think that you are saying that, in the right
circumstances, it's perfectly fine to create a model that inherits
directly from object. That does help.
FWIW, I'm still digesting Rob's response. I think that there is
likely a lot of help there as well. I ju
Doug Jolley wrote:
[...]
> Do we only use models with databases or do they have other uses?
They certainly have other uses. Models represent any domain object that
you need. Sometimes these objects will correspond to DB records,
sometimes not.
>
> Models descend from ActiveRecord::Base. Tha
On Jun 7, 2009, at 2:28 PM, doug wrote:
> Embarrassingly, I must admit that I have never understood models. I
> am hoping that with this post I can clear up a basic question that
> will allow me to get a toe-hold into understanding models. The basic
> question is this:
>
> Do we only use models
I'm not a Rails pro, but I would like to make the following comments:
A model
- represents your Data you deal with, like students/products... which you
save in a database!
- should include operations/methods which exclusively deal with the
object/data, like setter/getter moethds and/or
5 matches
Mail list logo
