Obie Fernandez on 25 Apr 2006 19:59:20 -0000 |
Hi there, We didn't have to rewrite *all* of our SQL, just a couple of them. In one case we simply removed the :include option from a finder method, which re-introduced an N+1 select issue that isn't really an issue in our case. Obie On 4/25/06, trisberg@tridb.com <trisberg@tridb.com> wrote: > It's not so much a driver issue as an issue of the SQL your OR mapper > generates. They could have created an Oracle 8i dialect for Active > Record, if that is possible. The issue is that 8i does not support the > ANSI join syntax as in this example: > > 9i syntax (ANSI): > > SELECT pub_name, title > FROM publishers > INNER JOIN titles ON publishers.pub_id = titles.pub_id > > You would have to rewrite it like this: > > 8i syntax: > > SELECT pub_name, title > FROM publishers, titles > where publishers.pub_id = titles.pub_id > > > Thomas > > > > One of Obie's colleagues stated that since the db they were using > > didn't support joins the way active record did them (I think that is > > what he was saying), that they had to write the sql for all of their > > queries. I was wondering if there was a reason why they didn't make > > their own db "driver" and open source it? > > > > -- > > Randy Schmidt > > x@altorg.com > > 267.334.6833 > > _______________________________________________ > > talk mailing list > > talk@phillyonrails.org > > http://lists.phillyonrails.org/mailman/listinfo/talk > > > > _______________________________________________ > talk mailing list > talk@phillyonrails.org > http://lists.phillyonrails.org/mailman/listinfo/talk > _______________________________________________ talk mailing list talk@phillyonrails.org http://lists.phillyonrails.org/mailman/listinfo/talk
|
|