Hey,
It''s more about resources than the database. They''re not one
to one,
but the way most rails models are designed usually, they''re very close
to a resource. For instance, you may have a product resource, which
might have an attribute called name. The data for that might not
actually be inside the products table, or perhaps your product
resource might aggregate several associations of the product model.
Either way there''s no implicit direct coupling of models with
resources, but more often they tend to be close. Hope that helps.
Blog: http://random8.zenunit.com/
Learn rails: http://sensei.zenunit.com/
On 02/05/2009, at 10:03 AM, chaitanya
<nagachaitanya.vellanki-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
>
> I have some questions regarding restful rails applications.
> Is the concept of restful so tied to the database ?
>
> What if a application does not use a database at all or if the
> application is using a legacy database which you cannot modify or does
> not have the concept of ids. How will restful urls and crud come into
> this picture.
>
>
> >