Beefy Boxes and Bandwidth Generously Provided by pair Networks
Pathologically Eclectic Rubbish Lister

Re^3: Chronological Ordering of Nodes with the Same Timestamp

by RonW (Parson)
on Sep 14, 2017 at 22:11 UTC ( #1199424=note: print w/replies, xml ) Need Help??

in reply to Re^2: Chronological Ordering of Nodes with the Same Timestamp
in thread Chronological Ordering of Nodes with the Same Timestamp

I would presume createtime is the time stamp of the node's creation. Historically, files in Unix, and derived systems, had 3 time stamps: createtime, modtime and accesstime, referring to when a file was created, last modified and last accessed. Even when storing the nodes in a database, those names could be used as the corresponding field names. Also, it's quite possible for those fields to be auto-filled when a node record is created, updated or accessed.

It may be that the database engine actually stores a higher resolution value, internally, than is made available to the program code using the database's API. Therefore, the ORDER_BY modifier to the SELECT operation may be using a higher resolution time stamp value.

Also, it's possible that behavior similar to for (keys %hash) is occurring. If that is the case, then maybe changing:



ORDER_BY('createtime', 'nodeid')

would give the result you expected.

(Assuming, of course, the database engine supports that.)

Log In?

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://1199424]
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others having an uproarious good time at the Monastery: (8)
As of 2019-05-23 19:09 GMT
Find Nodes?
    Voting Booth?
    Do you enjoy 3D movies?

    Results (146 votes). Check out past polls.

    • (Sep 10, 2018 at 22:53 UTC) Welcome new users!