message-db 2.0.2 → 2.1.4

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 8924f72521c7d2dfaad3524a3fc2f4be0d4f19ff8a8329ef59c2516e12f3e780
-  data.tar.gz: db54d8ee1604d9dd21f021d76ca7908efae849c1ae743c3089576f56fb55198c
+  metadata.gz: d86b37efb68b4f46fc655a3fc4f7ba8e7657197965087972bf4e8832f39f8a9e
+  data.tar.gz: 3ab551d95e717b5acc59774669f2b3d686ba0f2ffe0070b58d6dcb87344b1e06
 SHA512:
-  metadata.gz: f179f2d80ffb5a6768bab8cdedda241e6d27e81bfb91eff00bf976c91e7e3996e93998cf3e1542082269c2db225dda9abfb2ba5fe0e0228098f76ae2dbd0d751
-  data.tar.gz: '0378119403ae556f6fd26066dd4cac23dcf1093480087eb289f03fa6ae261d45cee9caf66981f990a4e57e486af45186f4f31269b8c2853b457cf0b8cd02d646'
+  metadata.gz: 2ca747525f2d3310df2420e5c4df5317585a2eca6ce88c7ba98616baf9dd2f0e9b8e84313d6c48599105855a4e9d5d1147330958ebbc28d0b892d2e70a1ca5bd
+  data.tar.gz: ca065829c7c968546e903789a3d877f4513f27a4a06503578ddf43601fe53f284f15ccdb969ac770fb1d387fd289070cf8e03573a4151f3578c97b976f4aa0ba

data/database/VERSION.txt

@@ -1 +1 @@
-1.1.6
+1.2.4

data/database/functions/get-category-messages.sql

@@ -101,9 +101,13 @@ BEGIN
 
   _command := _command || '
     ORDER BY
-      global_position ASC
-    LIMIT
-      $3';
+      global_position ASC';
+
+  IF get_category_messages.batch_size != -1 THEN
+    _command := _command || '
+      LIMIT
+        $3';
+  END IF;
 
   IF current_setting('message_store.debug_get', true) = 'on' OR current_setting('message_store.debug', true) = 'on' THEN
     RAISE NOTICE '» get_category_messages';

data/database/functions/get-stream-messages.sql

@@ -49,9 +49,13 @@ BEGIN
 
   _command := _command || '
     ORDER BY
-      position ASC
-    LIMIT
-      $3';
+      position ASC';
+
+  IF get_stream_messages.batch_size != -1 THEN
+    _command := _command || '
+      LIMIT
+        $3';
+  END IF;
 
   IF current_setting('message_store.debug_get', true) = 'on' OR current_setting('message_store.debug', true) = 'on' THEN
     RAISE NOTICE '» get_stream_messages';
@@ -60,7 +64,7 @@ BEGIN
     RAISE NOTICE 'batch_size ($3): %', get_stream_messages.batch_size;
     RAISE NOTICE 'condition ($4): %', get_stream_messages.condition;
     RAISE NOTICE 'Generated Command: %', _command;
-  end if;
+  END IF;
 
   RETURN QUERY EXECUTE _command USING
     get_stream_messages.stream_name,

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.1.6';
+  RETURN '1.2.4';
 END;
 $$ LANGUAGE plpgsql
 VOLATILE;

data/database/install.sh

@@ -22,6 +22,17 @@ else
   database=$DATABASE_NAME
 fi
 
+
+if [ -z ${CREATE_DATABASE+x} ]; then
+  CREATE_DATABASE="on"
+fi
+
+create_database=true
+if [ "$CREATE_DATABASE" = "off" ] ; then
+  create_database=false
+fi
+
+
 if [ -z ${PGOPTIONS+x} ]; then
   export PGOPTIONS='-c client_min_messages=warning'
 fi
@@ -66,7 +77,11 @@ echo
 
 echo "Creating Database"
 echo "- - -"
-create-database
+if [ "$create_database" = true ] ; then
+  create-database
+else
+  echo "Database creation is deactivated. Not creating the database."
+fi
 echo
 
 echo "Creating Schema"

data/database/privileges/functions.sql

@@ -1,5 +1,4 @@
 GRANT EXECUTE ON FUNCTION gen_random_uuid() TO message_store;
-GRANT EXECUTE ON FUNCTION md5(text) TO message_store;
 
 GRANT EXECUTE ON FUNCTION message_store.acquire_lock(varchar) TO message_store;
 GRANT EXECUTE ON FUNCTION message_store.cardinal_id(varchar) TO message_store;

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/uninstall.sh

@@ -28,7 +28,6 @@ fi
 
 function delete-user {
   echo "» message_store user"
-  psql postgres -P pager=off -q -c "DROP OWNED BY message_store;"
   psql postgres -P pager=off -q -c "DROP ROLE IF EXISTS message_store;"
 }
 

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))

data/database/update/1.2.2.md

@@ -0,0 +1,12 @@
+# 1.2.2 Update
+
+Note: There are no backward-incompatible changes in this update.
+
+This update requires the execution of the v1.2.2 update script: `1.2.2.sh`. For instructions on applying update scripts, see:
+
+[http://docs.eventide-project.org/user-guide/message-db/update.html](http://docs.eventide-project.org/user-guide/message-db/update.html)
+
+The following changes are made by the 1.2.2.sh update script:
+
+- The `get_category_messages` server function will return the entire, unlimited extent of messages in a category if -1 is sent as the `batch_size` argument
+- The `get_stream_messages` server function will return the entire, unlimited extent of messages in a stream if -1 is sent as the `batch_size` argument

data/database/update/1.2.2.sh

@@ -0,0 +1,65 @@
+#!/usr/bin/env bash
+
+set -e
+
+echo
+echo "Message DB"
+echo
+echo "Update the message_store database to v1.2.2"
+echo
+echo "WARNING:"
+echo "This script updates a post-v1 message_store database to Message DB v1.2.2"
+echo "Do not run this script on a Message DB pre-v1 database"
+echo
+echo "Fore more information about the changes made to the message store by"
+echo "this update, see: https://github.com/message-db/message-db/blob/master/database/update/1.2.2.md"
+echo
+echo "- Press CTRL+C to stop this script from running"
+echo "- Press RETURN to allow the script to proceed"
+echo
+
+read
+
+function script_dir {
+  val="$( cd "$( dirname "${BASH_SOURCE[0]}" )" && pwd )"
+  echo "$val"
+}
+
+base="$(script_dir)/.."
+echo $base
+
+echo
+echo "Updating Database"
+echo "Version: $(cat $base/VERSION.txt)"
+echo "= = ="
+
+if [ -z ${DATABASE_NAME+x} ]; then
+  echo "(DATABASE_NAME is not set. Default will be used.)"
+  database=message_store
+  export DATABASE_NAME=$database
+else
+  database=$DATABASE_NAME
+fi
+echo
+
+if [ -z ${PGOPTIONS+x} ]; then
+  export PGOPTIONS='-c client_min_messages=warning'
+fi
+
+function install-functions {
+  echo "» get_stream_messages function"
+  psql $database -q -f $base/functions/get-stream-messages.sql
+
+  echo "» get_category_messages function"
+  psql $database -q -f $base/functions/get-category-messages.sql
+}
+
+echo "Installing Functions"
+echo "- - -"
+install-functions
+echo
+
+echo "= = ="
+echo "Done Updating Database"
+echo "Version: $(cat $base/VERSION.txt)"
+echo

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: message-db
 version: !ruby/object:Gem::Version
-  version: 2.0.2
+  version: 2.1.4
 platform: ruby
 authors:
 - The Eventide Project
-autorequire: 
+autorequire:
 bindir: scripts
 cert_chain: []
-date: 2020-01-07 00:00:00.000000000 Z
+date: 2021-03-08 00:00:00.000000000 Z
 dependencies: []
 description: " "
 email: opensource@eventide-project.org
@@ -81,6 +81,8 @@ files:
 - database/update.sh
 - database/update/1.0.0.md
 - database/update/1.0.0.sh
+- database/update/1.2.2.md
+- database/update/1.2.2.sh
 - database/views/category-type-summary.sql
 - database/views/stream-summary.sql
 - database/views/stream-type-summary.sql
@@ -110,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
@@ -125,8 +127,8 @@ required_rubygems_version: !ruby/object:Gem::Requirement
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
-rubygems_version: 3.0.1
-signing_key: 
+rubygems_version: 3.1.2
+signing_key:
 specification_version: 4
 summary: Microservice native event store and message store for Postgres
 test_files: []