Running a single node CouchDB 2.1.1 Reading: http://docs.couchdb.org/en/2.1.1/api/database/changes.html it says
» Returns a sorted list of changes made to documents in the database, in time order of application, can be obtained from the database’s _changes resource. « I have an irc bot that adds a couchdb document with a timestamp for each message it sees (and also there are no updates to any documents). I also have a web page that longpolls the _changes url. things work out well enough in a normal situation when the changes feed only returns a single document (irc is not that heavy traffic), but if I get more than one result in the changes feed they don't come ordered by insertion time Actually that can be seen with this query too: curl ' https://irc.softver.org.mk/api/_changes?feed=longpoll&heartbeat=30000&include_docs=true&filter=log%2Fchannel&channel=lugola&since=719335-g1AAAAFreJzLYWBg4MhgTmEQTM4vTc5ISXIwNDLXMwBCwxygFFMeC5BkWACk_v__vz8riYExvpmg8gcQ5f9ByhO2EFR-AKL8Pkh53Ao8ypMSgGRSPdTk-I34lDqAlMZDlcYWEnREA8QR88FuVsGjPJEhSR5qbFwGPhcogFxgD3NsVBYAEpxlew' | jq '.results[].doc.timestamp' Timestamps vary widely: 1514374352.9027328 1514356816.2731326 1514373751.1156774 1514373763.0645776 1514373727.7714481 1514375011.2094588 1514375223.591063 1514370254.6656752 1514375022.4995384 1514370272.3448327 Is this intentional behaviour and the docs are wrong? -- damjan
