On 25/01/2008, Mike Ayers <[EMAIL PROTECTED]> wrote: > > We want to support duplicate attribute name in different > > table with different OID. > > You can have the same relative name for a column (attribute) > in two different tables.
Just as long as the two tables are defined in different MIBs. You can *no*t have the same MIB object name defined twice within the same MIB. In general, it's probably best to try and avoid duplicating names wherever possible. (Unless you have good reason to do so). The usual convention is to have a common prefix for all the column objects in a table - so it's immediately clear which objects belong together. For example - if you had two tables (table1 and table2) with essentially the same columns in each, the MIB object names might be something like: - t1index - t1name - t1rank - t1serialNo - t2index - t2name - t2rank - t2serialNo No problems with name clashes, it's clear which table a given column belongs to, but the meaning of the various columns is still clear. Dave ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ 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
