message-db 2.1.3 → 2.1.4

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 60fb7ed9471b4be0489977a4f78d9d93f5c602ae85bac76f13df67c36333932a
-  data.tar.gz: a092763059f1078bb53bd6b3152e858355cb9d78d36c7a8a97af2f7004ab4e58
+  metadata.gz: d86b37efb68b4f46fc655a3fc4f7ba8e7657197965087972bf4e8832f39f8a9e
+  data.tar.gz: 3ab551d95e717b5acc59774669f2b3d686ba0f2ffe0070b58d6dcb87344b1e06
 SHA512:
-  metadata.gz: 35719a3fa46617702d978dd242ba044f4db977f95df0ede94188064cdd938b8da9dcd83a029831df51bf7ef9b5793541bcd2d0c3e461a96aaa695a0b7d893840
-  data.tar.gz: 7bcba0df3cdd2361f5e6be61fe44569b87814708db8fcf1c6565707bad804c71c4e49afb971b6e23f3772945df5cd001001d2c2ff3f0132fe65f261cac67cb45
+  metadata.gz: 2ca747525f2d3310df2420e5c4df5317585a2eca6ce88c7ba98616baf9dd2f0e9b8e84313d6c48599105855a4e9d5d1147330958ebbc28d0b892d2e70a1ca5bd
+  data.tar.gz: ca065829c7c968546e903789a3d877f4513f27a4a06503578ddf43601fe53f284f15ccdb969ac770fb1d387fd289070cf8e03573a4151f3578c97b976f4aa0ba

data/database/VERSION.txt

@@ -1 +1 @@
-1.2.3
+1.2.4

data/database/functions/message-store-version.sql

@@ -2,7 +2,7 @@ CREATE OR REPLACE FUNCTION message_store.message_store_version()
 RETURNS varchar
 AS $$
 BEGIN
-  RETURN '1.2.3';
+  RETURN '1.2.4';
 END;
 $$ LANGUAGE plpgsql
 VOLATILE;

data/database/tables/messages.sql

@@ -1,12 +1,12 @@
 CREATE TABLE IF NOT EXISTS message_store.messages (
-  id UUID NOT NULL DEFAULT gen_random_uuid(),
+  global_position bigserial NOT NULL,
+  position bigint NOT NULL,
+  time TIMESTAMP WITHOUT TIME ZONE DEFAULT (now() AT TIME ZONE 'utc') NOT NULL,
   stream_name text NOT NULL,
   type text NOT NULL,
-  position bigint NOT NULL,
-  global_position bigserial NOT NULL,
   data jsonb,
   metadata jsonb,
-  time TIMESTAMP WITHOUT TIME ZONE DEFAULT (now() AT TIME ZONE 'utc') NOT NULL
+  id UUID NOT NULL DEFAULT gen_random_uuid()
 );
 
 ALTER TABLE message_store.messages ADD PRIMARY KEY (global_position) NOT DEFERRABLE INITIALLY IMMEDIATE;

data/database/update/1.0.0.md

@@ -6,21 +6,21 @@ The following changes are made by the 1.0.0.sh update script:
 
 - **Note: There are no changes to the `messages` table, and no data migration is necessary**
 - The executables named `evt-pg-*` are renamed to `mdb-*`
-- **[breaking change]** The `get_category_messages` server function supports pub/sub directly by receiving a `correlation` argument and composing the correlation metadata query condition directly in the server function ([http://docs.eventide-project.org/user-guide/message-store/server-functions.html#get-messages-from-a-stream](http://docs.eventide-project.org/user-guide/message-store/server-functions.html#get-messages-from-a-stream))
+- **[breaking change]** The `get_category_messages` server function supports pub/sub directly by receiving a `correlation` argument and composing the correlation metadata query condition directly in the server function ([http://docs.eventide-project.org/user-guide/message-db/server-functions.html#get-messages-from-a-category](http://docs.eventide-project.org/user-guide/message-db/server-functions.html#get-messages-from-a-category))
 - **[breaking change]** The message_store database and its objects are contained in a Postgres schema named `message_store`
-- **[breaking change]** The `get_category_messages` server function supports consumer groups via the `consumer_group_member` and `consumer_group_size` parameters ([http://docs.eventide-project.org/user-guide/message-store/server-functions.html#get-messages-from-a-category](http://docs.eventide-project.org/user-guide/message-store/server-functions.html#get-messages-from-a-category))
-- The retrieval server functions provide debugging output that is activated via the Postgres setting, `message_store.debug_get` ([http://docs.eventide-project.org/user-guide/message-store/server-functions.html#debugging-output](http://docs.eventide-project.org/user-guide/message-store/server-functions.html#debugging-output))
-- The write server function provides debugging output that is activated via the Postgres setting, `message_store.debug_write` ([http://docs.eventide-project.org/user-guide/message-store/server-functions.html#debugging-output](http://docs.eventide-project.org/user-guide/message-store/server-functions.html#debugging-output))
-- The `message_store.debug` Postgres setting activates both the retrieval and write debug output ([http://docs.eventide-project.org/user-guide/message-store/server-functions.html#debugging-output](http://docs.eventide-project.org/user-guide/message-store/server-functions.html#debugging-output))
-- `id` stream parsing function ([http://docs.eventide-project.org/user-guide/message-store/server-functions.html#get-the-id-from-a-stream-name](http://docs.eventide-project.org/user-guide/message-store/server-functions.html#get-the-id-from-a-stream-name))
-- `cardinal_id` stream parsing function ([http://docs.eventide-project.org/user-guide/message-store/server-functions.html#get-the-cardinal-id-from-a-stream-name](http://docs.eventide-project.org/user-guide/message-store/server-functions.html#get-the-cardinal-id-from-a-stream-name))
-- `acquire_lock` function encapsulates the application of the advisory lock used by the `write_message` function ([http://docs.eventide-project.org/user-guide/message-store/server-functions.html#get-message-store-database-schema-version](http://docs.eventide-project.org/user-guide/message-store/server-functions.html#get-message-store-database-schema-version))
+- **[breaking change]** The `get_category_messages` server function supports consumer groups via the `consumer_group_member` and `consumer_group_size` parameters ([http://docs.eventide-project.org/user-guide/message-db/server-functions.html#get-messages-from-a-category](http://docs.eventide-project.org/user-guide/message-db/server-functions.html#get-messages-from-a-category))
+- The retrieval server functions provide debugging output that is activated via the Postgres setting, `message_store.debug_get` ([http://docs.eventide-project.org/user-guide/message-db/server-functions.html#debugging-output](http://docs.eventide-project.org/user-guide/message-db/server-functions.html#debugging-output))
+- The write server function provides debugging output that is activated via the Postgres setting, `message_store.debug_write` ([http://docs.eventide-project.org/user-guide/message-db/server-functions.html#debugging-output](http://docs.eventide-project.org/user-guide/message-db/server-functions.html#debugging-output))
+- The `message_store.debug` Postgres setting activates both the retrieval and write debug output ([http://docs.eventide-project.org/user-guide/message-db/server-functions.html#debugging-output](http://docs.eventide-project.org/user-guide/message-db/server-functions.html#debugging-output))
+- `id` stream parsing function ([http://docs.eventide-project.org/user-guide/message-db/server-functions.html#get-the-id-from-a-stream-name](http://docs.eventide-project.org/user-guide/message-db/server-functions.html#get-the-id-from-a-stream-name))
+- `cardinal_id` stream parsing function ([http://docs.eventide-project.org/user-guide/message-db/server-functions.html#get-the-cardinal-id-from-a-stream-name](http://docs.eventide-project.org/user-guide/message-db/server-functions.html#get-the-cardinal-id-from-a-stream-name))
+- `acquire_lock` function encapsulates the application of the advisory lock used by the `write_message` function ([http://docs.eventide-project.org/user-guide/message-db/server-functions.html#get-message-store-database-schema-version](http://docs.eventide-project.org/user-guide/message-db/server-functions.html#get-message-store-database-schema-version))
 - Database management tool output is clarified
-- **[breaking change]** All server function parameter names are no longer named with underscore prefixes ([http://docs.eventide-project.org/user-guide/message-store/server-functions.html](http://docs.eventide-project.org/user-guide/message-store/server-functions.html))
-- Indexes are no longer built with the `CONCURRENTLY` option ([http://docs.eventide-project.org/user-guide/message-store/anatomy.html#source-code](http://docs.eventide-project.org/user-guide/message-store/anatomy.html#source-code))
+- **[breaking change]** All server function parameter names are no longer named with underscore prefixes ([http://docs.eventide-project.org/user-guide/message-db/server-functions.html](http://docs.eventide-project.org/user-guide/message-db/server-functions.html))
+- Indexes are no longer built with the `CONCURRENTLY` option ([http://docs.eventide-project.org/user-guide/message-db/anatomy.html#source-code](http://docs.eventide-project.org/user-guide/message-db/anatomy.html#source-code))
 - **[breaking change]** The `messages_category_global_position_idx` is removed and replaced with the `messages_category` index, which now indexes correlation metadata
 - **[breaking change]** The `messages_stream_name_position_uniq_idx` is removed and replaced with the `messages_stream` index, which now indexes correlation metadata
 - **[breaking change]** The `messages_id_uniq_idx` is removed and replaced with the `messages_id` index
 - Message DB RubyGem: [https://github.com/message-db/ruby-gem](https://github.com/message-db/ruby-gem)
 - Message DB NPM Module: [https://github.com/message-db/npm-module](https://github.com/message-db/npm-module)
-- Improvements to interactive tests ([https://github.com/eventide-project/postgres-message-store/tree/master/test](https://github.com/eventide-project/postgres-message-store/tree/master/test))
+- Improvements to interactive tests ([https://github.com/eventide-project/message-store-postgres/tree/master/test](https://github.com/eventide-project/message-store-postgres/tree/master/test))

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: message-db
 version: !ruby/object:Gem::Version
-  version: 2.1.3
+  version: 2.1.4
 platform: ruby
 authors:
 - The Eventide Project
-autorequire: 
+autorequire:
 bindir: scripts
 cert_chain: []
-date: 2020-05-16 00:00:00.000000000 Z
+date: 2021-03-08 00:00:00.000000000 Z
 dependencies: []
 description: " "
 email: opensource@eventide-project.org
@@ -112,7 +112,7 @@ homepage: https://github.com/message-db/message-db
 licenses:
 - MIT
 metadata: {}
-post_install_message: 
+post_install_message:
 rdoc_options: []
 require_paths:
 - lib
@@ -128,7 +128,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
       version: '0'
 requirements: []
 rubygems_version: 3.1.2
-signing_key: 
+signing_key:
 specification_version: 4
 summary: Microservice native event store and message store for Postgres
 test_files: []