Re: Canonical configuration database order

["David T. Perkins" <dperkins@dsperkins.com>]

HI,

Yes, and remember that the sort order for values is
not just the order if the values were text strings,
but the order is based on the type of the value.
For example, sorting as text, string "10" preceeds
string "2". But sorting as numbers, value "2"
preceeds value "10".

On Fri, 2 Jun 2006, Andy Bierman wrote:
> Randy Presuhn wrote:
> > Hi -
> > 
> >> From: "Andy Bierman" <ietf@andybierman.com>
> >> To: "Netconf (E-mail)" <netconf@ops.ietf.org>
> >> Sent: Friday, June 02, 2006 8:30 AM
> >> Subject: Canonical configuration database order
> > ...
> >> The canonical order for named sibling instances is the natural sort order,
> >> based on the key associated with the nodes.  For multiple unnamed
> > ...
> > 
> > What is meant by "the natural sort order"?
> 
> Ascending order for each component of the key.
> Keys are evaluated 'top to bottom', where the
> topmost component represents the major index,
> and each successive key component represents
> successive minor index components.
> 
> > 
> > Randy
> 
> Andy
> 
Regards,
/david t. perkins


--
to unsubscribe send a message to netconf-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/netconf/>