|
> -----Original Message----- > From: Behalf Of Joe Pluta > > > update pricefile set unit_price = unit_price * 1.05 > > where product_type = "widgets" > > I've seen this example in so many SQL references as to make me > ill. This is > a very rare occurence for every business I've seen. It's not at all unusual in industries where pricing is based upon the commodities markets. > > Yes, and for those things, SQL is good. For transaction > processing, SQL is > bad. For queries and wholesale data replacement, SQL works wonders, but > when programmers start using it to update data (especially a record at a > time), that's when I shake my head. Why? If you're achieving sub-second response time with the SQL update, does it really matter that a native opcode would have taken a few milliseconds less to complete? In an interactive TP application, the difference isn't noticable. John Taylor
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.