This is a discussion on RE: [Fwd: Re: related tables design] within the SNMP Users forums, part of the Networking and Network Related category; > From: net-snmp-users-bounces@lists.sourceforge.net > [mailto:net-snmp-users-bounces@lists.sourceforge.net] On > ...
|
|||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
|
|||
|
> From: net-snmp-users-bounces@lists.sourceforge.net
> [mailto:net-snmp-users-bounces@lists.sourceforge.net] On > Behalf Of Xuan Pan > Sent: Friday, January 18, 2008 1:48 AM > Since I still have the problem in my last post unsolved, I > don't really > understand why the order of indexes matters. I'm not sure what unsolved problem you refer to, but the chief reason for putting the augmented index first is to allow a walk of [table].[augmented index] to return all the rows which match the augmented row. If you really are doing a table of DHCP ranges, are you sure you need to augment each interface with a table of values? It seems to me that a DHCP server would only have one range to serve, an thus the second index would be moot. HTH, Mike ------------------------------------------------------------------------- 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 Net-snmp-users@lists.sourceforge.net Please see the following page to unsubscribe or change other options: https://lists.sourceforge.net/lists/...net-snmp-users |