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
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
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
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
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
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
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),
>-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
> 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
glemail.com]
> >Sent: Wednesday, September 01, 2010 4:29 PM
> >To: [MySQL]
> >Subject: Best method to keep totals
> >
> >Hi,
> >
> >I'm developing a system whereby a manager gets assigned points based a
> >certain number of factors which are saved a
d
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
>-Original Message-
>From: Tompkins Neil [mailto:neil.tompk...@googlemail.com]
>Sent: Wednesday, September 01, 2010 4:29 PM
>To: [MySQL]
>Subject: Best m
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 uses SUM to total the managers points gained
f
12 matches
Mail list logo