surely I will look into snmptrapd_sql.c> Problems is the keys. Parent table
index and child table index makes the key for the child table.
I'm sorry - I don't understand what you mean by this.
SNMP doesn't have a concept of "parent tables" and "child tables".
A table is a table is a table.
Sorry to confuse here. Let me explain with an example . I understand there is
no Tree concept in SNMP land.
Let's say there is an ABC table and abcIndex is key which gets appended with
the root oid to form the oids from the oid for the individual row of the table.
Now there is second one DEF Table and its oid is formed using root oid of the
DEF table appended with abcIndex and defIndex. This is very common.
If I like to store the rows in database , abcIndex will be the primary key of
the ABC table( in database)
and for the second table , the primary key is abcIndex+defIndex.
So I was wondering what will be the easier way to store the snmp data in
database table. Rows are dynamic. I mean to say they are not scalar in nature.
More over generally the Index fields are MAX-ACCESS
not-accessible.
Parsing the oid and forming the primary key is the harder way to do .
Any easier way ?
------------------------------------------------------------------------------
Get a FREE DOWNLOAD! and learn more about uberSVN rich system,
user administration capabilities and model configuration. Take
the hassle out of deploying and managing Subversion and the
tools developers use with it. http://p.sf.net/sfu/wandisco-d2d-2
_______________________________________________
Net-snmp-coders mailing list
Net-snmp-coders@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
