From 446535fb7ccd55e680351ee75cba91cfe3a9ff7c Mon Sep 17 00:00:00 2001
From: Stevan <stevan.earl@asu.edu>
Date: Sat, 8 Feb 2025 22:06:20 +0000
Subject: [PATCH] correct macro suffix pdb_ -> sdb_

---
 bin/sokwedb-user-add.m4       | 4 ++--
 bin/sokwedb-user-delete.m4    | 6 +++---
 doc/src/architecture/users.m4 | 6 +++---
 3 files changed, 8 insertions(+), 8 deletions(-)

diff --git a/bin/sokwedb-user-add.m4 b/bin/sokwedb-user-add.m4
index 2575a1a..00a1fa9 100644
--- a/bin/sokwedb-user-add.m4
+++ b/bin/sokwedb-user-add.m4
@@ -117,9 +117,9 @@ EOF
 elif [ -n "$DEV" ] ; then
   psql "$CONNECTIONSTRING dbname=template1" <<EOF
 begin;
-set role to pdb_role_owner;
+set role to sdb_role_owner;
 create role $A_USER login password '$A_USER';
-grant pdb_admin_group to $A_USER;
+grant sdb_admin_group to $A_USER;
 reset role;
 alter role $A_USER createdb bypassrls;
 commit;
diff --git a/bin/sokwedb-user-delete.m4 b/bin/sokwedb-user-delete.m4
index e969959..9d0b932 100644
--- a/bin/sokwedb-user-delete.m4
+++ b/bin/sokwedb-user-delete.m4
@@ -64,7 +64,7 @@ if [ -z "$ADMIN" ] ; then
   psql "$CONNECTIONSTRING dbname=sokwedb_dev" <<EOF
 -- We start in sokwedb_dev
 begin;
-set role pdb_role_owner;
+set role sdb_role_owner;
 set role $A_USER;
 drop schema if exists $A_USER cascade;
 reset role;
@@ -72,7 +72,7 @@ reset role;
 commit;
 \c sokwedb_test
 begin;
-set role pdb_role_owner;
+set role sdb_role_owner;
 set role $A_USER;
 drop schema if exists $A_USER cascade;
 reset role;
@@ -80,7 +80,7 @@ reset role;
 commit;
 \c sokwedb
 begin;
-set role pdb_role_owner;
+set role sdb_role_owner;
 set role $A_USER;
 drop schema if exists $A_USER cascade;
 reset role;
diff --git a/doc/src/architecture/users.m4 b/doc/src/architecture/users.m4
index e4a3a91..ae41e4c 100644
--- a/doc/src/architecture/users.m4
+++ b/doc/src/architecture/users.m4
@@ -59,9 +59,9 @@ queries and monitoring database activity, are also done occasionally.
 The build system and other supplied tools automatically ensure that
 tasks performed as an administrator are done by the appropriate group
 on behalf of the administrator.
-Administrators are in, and can become, the ``pdb_role_owner`` group
+Administrators are in, and can become, the ``sdb_role_owner`` group
 and so can create and destroy roles.
-And they are in and can become the ``pdb_admin_group`` and therefore
+And they are in and can become the ``sdb_admin_group`` and therefore
 create and destroy tables, create and destroy user logins, etc.
 
 Only a few people are expected to have administrator privileges.
@@ -133,7 +133,7 @@ interacting with database content.
          or extension installation, and thus, like administrators, have
          access to the server's file system and server executables.
 
-.. [#f3] Developers are not in the ``pdb_role_owner`` group.
+.. [#f3] Developers are not in the ``sdb_role_owner`` group.
 
 .. [#f4] The Azure cloud platform does not allow logins (aka roles) to have
          the ``SUPERUSER`` `role attribute`.
-- 
2.34.1