Track event sequences globally, not per channel.

Per-channel event sequences were a cute idea, but it made reasoning about event resumption much, much harder (case in point: recovering the order of events in a partially-ordered collection is quadratic, since it's basically graph sort). The minor overhead of a global sequence number is likely tolerable, and this simplifies both the API and the internals.

1 files changed, 0 insertions, 38 deletions

diff --git a/.sqlx/query-df3656771c3cb6851e0c54a2d368676f279af866d0840d6c2c093b87b1eadd8c.json b/.sqlx/query-df3656771c3cb6851e0c54a2d368676f279af866d0840d6c2c093b87b1eadd8c.json
deleted file mode 100644
index 87e478e..0000000
--- a/.sqlx/query-df3656771c3cb6851e0c54a2d368676f279af866d0840d6c2c093b87b1eadd8c.json
+++ /dev/null
@@ -1,38 +0,0 @@
-{
-  "db_name": "SQLite",
-  "query": "\n                select\n                    channel.id as \"channel_id: channel::Id\",\n                    channel.name as \"channel_name\",\n                    channel.created_at as \"channel_created_at: DateTime\",\n                    message.id as \"message: message::Id\"\n                from message\n                    join channel on message.channel = channel.id\n                    join login as sender on message.sender = sender.id\n                where sent_at < $1\n            ",
-  "describe": {
-    "columns": [
-      {
-        "name": "channel_id: channel::Id",
-        "ordinal": 0,
-        "type_info": "Text"
-      },
-      {
-        "name": "channel_name",
-        "ordinal": 1,
-        "type_info": "Text"
-      },
-      {
-        "name": "channel_created_at: DateTime",
-        "ordinal": 2,
-        "type_info": "Text"
-      },
-      {
-        "name": "message: message::Id",
-        "ordinal": 3,
-        "type_info": "Text"
-      }
-    ],
-    "parameters": {
-      "Right": 1
-    },
-    "nullable": [
-      false,
-      false,
-      false,
-      false
-    ]
-  },
-  "hash": "df3656771c3cb6851e0c54a2d368676f279af866d0840d6c2c093b87b1eadd8c"
-}