>-----Original Message----- >From: Jan Steinman [mailto:j...@bytesmiths.com] >Sent: Thursday, September 02, 2010 1:52 PM >To: mysql@lists.mysql.com >Subject: RE: Best method to keep totals > >> From: "Jerry Schwartz" <je...@gii.co.jp> >> >> IMNSHO, never store dynamic data in a field unless you absolutely have to. > >I agree, and yet, it's so darned handy if it's a calculation you need quite >often. > [JS] You run the risk of introducing inconsistencies.
>In FileMaker Pro (hold the "boos," please :-) you can have calculated >fields -- >a "pseudo field" that holds references to other fields in an equation. > [JS] I've used similar products. I suspect that the calculations are done on demand just as they would be with MySQL. >To do something similar in MySQL, I've used views (which is somewhat clumsy), >but is there a better way? Or is this necessarily part of domain knowledge >programming in your interface language? > [JS] Wouldn't the appropriate place for the calculation be in whatever queries retrieve the data, or in a store procedure that they share? That's basically the same as a calculated field. Regards, Jerry Schwartz Global Information Incorporated 195 Farmington Ave. Farmington, CT 06032 860.674.8796 / FAX: 860.674.8341 E-mail: je...@gii.co.jp Web site: www.the-infoshop.com >---------------- > >:::: Jan Steinman, EcoReality Co-op :::: > > >-- >MySQL General Mailing List >For list archives: http://lists.mysql.com/mysql >To unsubscribe: http://lists.mysql.com/mysql?unsub=je...@gii.co.jp -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/mysql?unsub=arch...@jab.org
