I''m not sure if its an odd DB so much.. its the kind of thing that will
have
multiple UIs strung off it that want to look at different things.
I''m thinking a new view would be the best way to approach this, just
kind of
hesitant to set a precident of essentially creating a view for every intense
query that comes along.
Kevin
Eager fetching will be part of the next release. But if you need
to> join over more then two table then
> you have different problems.
>
> Obviously you can find_by_sql to get this kind of data but you are
> probably better off just doing 8 queries and putting a fragment cache
> in place because this way you can take advantage of all the help AR
> gives you with relations.
>
> Honestly, just wanting a join like this is a good indication of a odd DB.
>
> Don''t forget that rails is geared for new legacy free development
and
> because of this it does a better job at aiding this type of
> development then legacy aware systems like hibernate. It is made under
> the assumption that the Database is just a way to persist the data
> required by your models and business logic. Optimization comes from
> caching and not from 1990 style sql queries. That being said people
> added an array of tools to get legacy dbs working. Especially views
> seem to be very popular to get legacy db''s into AR mindset (
plural
> tables, lowercase columns, id for PK ).
_______________________________________________
Rails mailing list
Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org
http://lists.rubyonrails.org/mailman/listinfo/rails