Re: 'Inter-Tables indexing' and perl

Quoting Dave Shield <[email protected]>:

>> Eh, no. For each job _ID_. The 'System' here is only _my_
>> name of a specific job group...
>
> Sorry - my mistake.   I'd missed that extra level of nesting.
> But for each job ID, there are the same five statistics - yes?
> [...]
> But regardless of the nesting, there seem to be
> the same five statistics at the bottom level.
> Is that correct?

Yes.

> If the group of five stats is associated with a particular
> jobID (which is associated with a particular job Name,
> which is associated with a particular client), then there
> are three levels of nesting going on.
>
> So the statistics would be represented by a single table,
> indexed by *three* index values (client, jobName, jobID)
> Each extra level of nesting introduces another index object
> to the table.
>
>   But you only need one table (with the expected five columns)
> for all the stats.

Oki, that was my original though (early this week). But I never
got it right, so I tried something new, something blue and ... :)

> But a full walk of the 5-column statistics table ought
> to look something like:
>
>   $ snmpwalk jobIDStatsTable
>   stat1.client1.job1.id1 = start date
>   stat1.client1.job1.id2 = start date
>   stat1.client1.job2.id1 = start date
>   stat1.client1.job2.id2 = start date
> 	  :
>   stat1.client2.job3.id3 = start date
>   stat2.client1.job1.id1 = end date
>   stat2.client1.job1.id2 = end date
>           :
>   stat5.client2.job3.id3 = bytes
>
>
> So it's *only* the indexing of each OID where there's any
> repetition. None of the index values need appear as
> accessible columns (in any table), and there doesn't need
> to be any duplication between client/name/id values.

Wasn't that EXACTLY what I put in my first mail in the thread?
*looking*
Hm, no. I never introduced the stats table, only the clients
table. But if I understand you correctly, that should be
split into two tables, one with the client info and one
with the job name info?

So, to recap and see if I understood you correctly:

    # The table with the client info, index from clientsTable
    $ snmpwalk clientsTable
    client1 = client1
    client2 = client2
       :

    # The table with the job names, index from clientsTable AND jobsTable
    $ snmpwalk jobsTable
    client1.job1 = job1
    client1.job2 = job2
       :
    client2.job1 = job1
    client2.job2 = job2
       :

    # The table with the stats info, index from clientsTable,
    # jobsTable AND statsTable
    $ snmpwalk statsTable
    stat1.client1.job1.id1 = start date
    stat1.client1.job1.id2 = start date
    stat1.client1.job2.id1 = start date
    stat1.client1.job2.id2 = start date
       :
    stat1.client2.job3.id3 = start date
    stat2.client1.job1.id1 = end date
    stat2.client1.job1.id2 = end date
       :
    stat5.client2.job3.id3 = bytes

Hm, you put the 'statX' differently than I had expected. I
would have (did earlier this week) swap the 'statX' and
'idX' parts.


And with your explanation and this discussion shows that
that was obviosly wrong. No wonder it didn't work :).

Thanx for the help. Did I get it right this time around?
-- 
killed DES Waco, Texas radar cryptographic class struggle CIA
counter-intelligence 767 South Africa Ft. Meade jihad Marxist Nazi
cracking
[See http://www.aclu.org/echelonwatch/index.html for more about this]
[Or http://www.europarl.eu.int/tempcom/echelon/pdf/rapport_echelon_en.pdf]
If neither of these works, try http://www.aclu.org and search for echelon.


-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Net-snmp-users mailing list
[email protected]
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users