On 30/03/12 07:40, nathanelrick wrote: > http://www.addsimplicity.com/downloads/eBaySDForum2006-11-29.pdf Because I'm a masochist, I'll have a read of that later!
> No business logic in database > no stored procedure > only very simple triggers (default population) > > Move CPU intensive work to applications > Referential integrity > joins > sorting They are certainly keeping the database simple then. Wonder why they bothered to pay huge sums of money to Oracle for licenses and features to make their lives simple, and then completely ignore them and do everything in code, in the application. Sounds like their head of development needs a good (metaphorical) kicking. This database will be corrupted at some point as soon as someone runs a script that manages to avoid all the check constraints, referential integrity and so on, unless they have to build it into each and every script that touches the database. Madness. Complete madness. A prime example on how not to create a database system! > Extensive use of prepared statements and variables Yes, and I'll bet they do what every Java application I've seen does, prepares the same statement hundreds of times, even though they should do it only once. See http://qdosmsq.dunbar-it.co.uk/blog/2009/02/it-must-be-efficient-im-using-bind-variables/ for details. :-) Cheers, Norm. -- Norman Dunbar Dunbar IT Consultants Ltd Registered address: Thorpe House 61 Richardshaw Lane Pudsey West Yorkshire United Kingdom LS28 7EL Company Number: 05132767
