table configuration advice also for me!

Hello from Italy!

I'm going to create a php script that registers and reports stats for
20/30 externals sites (with about 2.000 daily visitors each one).

I need to configure the tables (mysql) where I would store visitors data.

I need help to choose between these solutions:

a) two table visitors and visits whit a field site_id to distinguish
between monitorated sites visitors

b) two table for each site: site_1_visitors, site_1_visits,
site_2_visitors, site_2_visits etc...

What do you think about it?

Thanks!!

On Thu, 17 Apr 2008 19:06:06 +0200, nintesa <nintesa@nomaaaaail.it> wrote:

> Hello from Italy!
>
> I'm going to create a php script that registers and reports stats for
> 20/30 externals sites (with about 2.000 daily visitors each one).
>
> I need to configure the tables (mysql) where I would store visitors data.
>
> I need help to choose between these solutions:
>
> a) two table visitors and visits whit a field site_id to distinguish
> between monitorated sites visitors
>
> b) two table for each site: site_1_visitors, site_1_visits,
> site_2_visitors, site_2_visits etc...

Hmm, don't crosspost please.

(allthough this is a better group for it then comp.lang.php, in which I
answered your question)
--
Rik Wasmus

Rik Wasmus ha scritto:
> On Thu, 17 Apr 2008 19:06:06 +0200, nintesa <nintesa@nomaaaaail.it> wrote:
>
>> Hello from Italy!
>>
>> I'm going to create a php script that registers and reports stats for
>> 20/30 externals sites (with about 2.000 daily visitors each one).
>>
>> I need to configure the tables (mysql) where I would store visitors data.
>>
>> I need help to choose between these solutions:
>>
>> a) two table visitors and visits whit a field site_id to distinguish
>> between monitorated sites visitors
>>
>> b) two table for each site: site_1_visitors, site_1_visits,
>> site_2_visitors, site_2_visits etc...
>
> Hmm, don't crosspost please.
>
> (allthough this is a better group for it then comp.lang.php, in which I
> answered your question)

You're right! I before posted on php and then I remembered this group...

nintesa:
> Hello from Italy!
>
Hi from Germany

> I'm going to create a php script that registers and reports stats for
> 20/30 externals sites (with about 2.000 daily visitors each one).
>
> I need to configure the tables (mysql) where I would store visitors data.
> I need help to choose between these solutions:
>
> a) two table visitors and visits whit a field site_id to distinguish
> between monitorated sites visitors
>
> b) two table for each site: site_1_visitors, site_1_visits,
> site_2_visitors, site_2_visits etc...

In my opinion, you have an ER diagram with at least three entities:
sites, visits and visitors. Because visitors can visit multiple sites,
and sites are visited by multiple visitors, it should look like:


SITE--1----n--VISIT--m----1--VISITOR

Since you don't mention any attributes, I assume for now, that this would
do. Depending on possible repetitive attributes, you'd need to normalize
further.


--
Erick

Rik Wasmus wrote:
> On Thu, 17 Apr 2008 19:06:06 +0200, nintesa <nintesa@nomaaaaail.it>
> wrote:
>> Hello from Italy!
>>
>> I'm going to create a php script that registers and reports stats for
>> 20/30 externals sites (with about 2.000 daily visitors each one).
>>
>> I need to configure the tables (mysql) where I would store visitors
>> data.
>> I need help to choose between these solutions:
>>
>> a) two table visitors and visits whit a field site_id to distinguish
>> between monitorated sites visitors
>>
>> b) two table for each site: site_1_visitors, site_1_visits,
>> site_2_visitors, site_2_visits etc...
>
> Hmm, don't crosspost please.
>
> (allthough this is a better group for it then comp.lang.php, in which
> I answered your question)

He didn't cross post, he multi-posted, which is worse