NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.

To learn about what's going on, see About the Archive Site.

Re: Schedule decision

NOTE: The netcdf-hdf mailing list is no longer active. The list archives are made available for historical reasons.

Quincey Koziol <koziol@xxxxxxxxxxxxx> writes:

>     I was planning on including a hidden field to disambiguate objects that
> were created at the same time, so this wouldn't happen.  Since there's no
> advantage to using a creation order field instead of using the creation time
> when determining the n'th object inserted into a group (when factoring deleted
> objects into the equation), I'm still leaning toward using a time instead of 
> an
> index for this purpose.  Using the time provides the same functionality and
> adds information as well.
>
>     I'm still somewhat split on the issue however and would welcome persuasive
> arguments in favor of one mechanism or the other.  :-)  I'm also thinking 
> about
> including both fields (creation order and creation time) and allowing users to
> create an index on either, to suit their particular needs...

Quincey,

What happens is a machine with an inaccurate time adds a variable to a
dataset?

Ed

-- 
Ed Hartnett  -- ed@xxxxxxxxxxxxxxxx


  • 2005 messages navigation, sorted by:
    1. Thread
    2. Subject
    3. Author
    4. Date
    5. ↑ Table Of Contents
  • Search the netcdf-hdf archives: