allow receiving and storing messages with the same timestamp #55

shunf4 · 2021-10-06T16:45:25Z

shunf4 commented

2021-10-06 16:45:25 +00:00

It's possible that some messages have the same timestamp (e.g. network is down when sending them; once network is up, they are sent simutaneously.).

We should allow storing them in the local archive, by specifying MDB_DUPSORT when creating order db.

This PR is based on #50. The changes for this PR is at the lastest commit.

It's possible that some messages have the same timestamp (e.g. network is down when sending them; once network is up, they are sent simutaneously.). We should allow storing them in the local archive, by specifying `MDB_DUPSORT` when creating `order` db. This PR is based on #50. The changes for this PR is at the lastest commit.

shunf4 added 17 commits 2021-10-06 16:45:26 +00:00

5fbb96618f adjust CMakeLists.txt, to prepare for win32 and macos builds

6764d8ea11 remove dependency libuuid

c55b7c6baf update docs for removed uuid dep and LMDB_DIR var

faa7d396a5 add liblmdb.so as possible lmdb lib name

923afe2420 [Fix] Merge branch 'feat/adapt_win_osx' into upstream_messageFeed

a1f3c00a54 remove dependency uuid

1e37aa762c generate app bundle for macOS

d1f108e69d update docs for win32 build

261b34b712 add forgotten cmake/MacOSXBundleInfo.plist.in

41d9fa7a1c fix macos bundle build

f3153ef1db ci: add appveyor.yml