tag:blogger.com,1999:blog-7395977411859619892.post5374186825907566388..comments2024-01-30T09:21:06.579+01:00Comments on About Oracle: Oracle OpenWorld 2009, the last three daysRob van Wijkhttp://www.blogger.com/profile/00499478359372903250noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-7395977411859619892.post-10302058963460940642009-10-18T09:45:46.957+02:002009-10-18T09:45:46.957+02:00Hi Steven,
Thanks for stopping by and clarifying ...Hi Steven,<br /><br />Thanks for stopping by and clarifying the statements.<br /><br />Of course I agree that repetition of SQL statements is one of the things that makes an application hard to maintain. I'm experiencing this one first hand at my current client. So three way joins or even seven way joins are perfectly acceptable in PL/SQL, provided they are only implemented in the bottom Rob van Wijkhttps://www.blogger.com/profile/00499478359372903250noreply@blogger.comtag:blogger.com,1999:blog-7395977411859619892.post-64427203908026941922009-10-17T15:43:13.863+02:002009-10-17T15:43:13.863+02:00Thanks for your kind comments, Rob. You also wrote...Thanks for your kind comments, Rob. You also wrote:<br /><br />"However, there were a few statements here that I strongly disagree with. Statements like 'SQL statements with 3 table joins, or 7; that's crazy!' or 'It doesn't make sense for developers to have to learn the ins and outs of tuning SQL!'"<br /><br />You know, those sound objectionable to me, too, so ISteven Feuersteinhttps://www.blogger.com/profile/16619706770920320550noreply@blogger.com