hi, honestly i see nothing bad in your approach, it is the thing you need to get your job done. it handles only selects which might be all you need. a real abstraction layer (as mentioned earlier) is way more. it abstracts away the differences between supported databases and does all kinds of handy things you want to have in a larger application. if you just need a small thing this might be a good solution. cheers lenz
On Thu, May 21, 2009 at 10:10 AM, Jochen Daum <[email protected]> wrote: > > Hi, > > On Thu, May 21, 2009 at 9:15 AM, Robin <[email protected]> wrote: > > I have been looking at different database abstraction layers such as > propel > > or pearDB and they seem soooo overly abstracted resulting in average > > performance at best that I decided to write the simplest query > abstraction I > > could and I would like to get your opinions on why I would use propel or > > pearDB instead of http://pastie.org/484625. > > > > > > > > Its really pointless to worry about the performance of the abstraction > layer when: > > > - unoptimised Mysql queries have 100 times the slow down effect > - lack of query caching has huge effect > - lack of page/snippet caching has huge effect > > > Do you have any factual sources to claim "average" performance of a db > abstraction layer? > > > HTH, Jochen > > > > -- iWantMyName.com painless domain registration (finally) --~--~---------~--~----~------------~-------~--~----~ NZ PHP Users Group: http://groups.google.com/group/nzphpug To post, send email to [email protected] To unsubscribe, send email to [email protected] -~----------~----~----~----~------~----~------~--~---
