Re: Best method to keep totals

Just another quick question - following my initial question regarding the best method to keep totals, I wondered if I should adopt a table to record team league standings like based on each result like team_id home_win home_draw home_loss home_goals home_conceded away_win away_draw away_loss away_

Re: Best method to keep totals

Thanks for all the useful information. I'm going to ensure the relevant fields are indexed and our db is optimised. On 4 Sep 2010, at 16:10, Arthur Fuller wrote: 100% agreed. Arthur The other exception is also where financial data is being stored. If you have, say, a database containi

Re: Best method to keep totals

100% agreed. Arthur The other exception is also where financial data is being stored. If you > have, say, a database containing sales order records, then as well as > storing the individual values of each item in each order, you also need to > store the total value of the order, the total price c

Re: Best method to keep totals

On 03/09/2010 16:32, Arthur Fuller wrote: While I agree with the general take on this subject ("Never store totals without a good reason" and "where there is duplication there is the opportunity for skew"), I must say that there are exceptions. A couple of years ago I worked on an inherited datab

Re: Best method to keep totals

While I agree with the general take on this subject ("Never store totals without a good reason" and "where there is duplication there is the opportunity for skew"), I must say that there are exceptions. A couple of years ago I worked on an inherited database in which the operant principle was "sum

Re: Best method to keep totals

On 01/09/2010 10:29 p, Tompkins Neil wrote: Hi, I'm developing a system whereby a manager gets assigned points based a certain number of factors which are saved alongside a football result. However, I also want to keep a total for each manager. My question is it best to just have a query that

Re: Best method to keep totals

On 2 Sep 10, at 13:58, Jerry Schwartz wrote: >> From: Jan Steinman [mailto:j...@bytesmiths.com] >> >>> From: "Jerry Schwartz" >>> >>> IMNSHO, never store dynamic data in a field unless you absolutely have to. ... >> To do something similar in MySQL, I've used views (which is somewhat clumsy),

RE: Best method to keep totals

>-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" >> >> IMNSHO, never store dynamic

RE: Best method to keep totals

> From: "Jerry Schwartz" > > 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. In FileMaker Pro (hold the "boos," please :-) you can have calculated fields -- a "pseudo field" that hold

Re: Best method to keep totals

Thanks for your quick response. So like I thought, I'll just calculate the totals on the fly and like you mentioned the manager is going to participate in 50 games per season, with a season being twice per year. Thanks for the help. Neil On Wed, Sep 1, 2010 at 10:06 PM, Jerry Schwartz wrote:

RE: Best method to keep totals

IMNSHO, never store dynamic data in a field unless you absolutely have to. There are going to be exceptions, but unless a manager is going to participate in hundreds of thousands of fixtures I don't think this is one of them. Regards, Jerry Schwartz Global Information Incorporated 195 Farmingto