Afficher un message
Vieux 07/01/2008, 11h07   #6
Paul Lautman
Aucun Avatar
 
Messages: n/a
Hébergeur:
Par défaut Re: stats database structure - design suggestions

FFMG wrote:
> Paul Lautman;112085 Wrote:
>>
>> >
>> > So, what do you suggest would be the best design?
>> >
>> > FFMG

>>
>> I would go for timestamp and pageid.

>
> hum... thanks, any particular reason why?
>
> FFMG[/color]

You then have all the information you need to cut the data up in any way you
want. For instance you may think initially that you only want to know how
many hits per day. But you may want to in future know when during the day
you get most hints. Of course other nice information to have is stuff that
things like Google Analytics gives you such as where it "thinks" the hits
were from. So maybe holding the IP address of the request would be good.

The more assumptions you make up front when storing the data (i.e. the more
preprocessing you do on it), the less you can actually do with the data. One
of the things about data analysis is that untill you analyse it, you don't
know whet there is to find out. If you scupper the data at the start, you
reduce the amount of analysis you can do.


  Réponse avec citation
 
Page generated in 1,09307 seconds with 9 queries