From: | Erik Wienhold <ewie(at)ewie(dot)name> |
---|---|
To: | Wells Oliver <wells(dot)oliver(at)gmail(dot)com> |
Cc: | pgsql-admin(at)lists(dot)postgresql(dot)org |
Subject: | Re: Allowing users to create objects in version controlled schema |
Date: | 2022-11-08 02:29:51 |
Message-ID: | 1103549459.284197.1667874591587@office.mailbox.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
> On 08/11/2022 02:19 CET Wells Oliver <wells(dot)oliver(at)gmail(dot)com> wrote:
>
> Feels like more of a process question and less of a technical postgres
> question.
You're right. But I'm wondering what's possible on the technical front.
> In our world, each DB user has their own schema they have full access to, and
> can grant privileges as required.
Right, the standard approach with search_path = "$user".
> All schema definitions tables/views/etc are versioned using git in a structured
> repository of flat sql files. It works well. Table defs etc get code reviewed
> and deployed by more DB-minded engineers,
That's what I meant with version controlled migrations. And I actually don't
want users to bypass that process to create and reference their own database
structures when those structures should rather be part of the common application
schema.
> and people are cognizant of writing optimized SQL.
That's where I have my doubts when it comes to inexperienced "devs" and no
guiding code reviews.
--
Erik
From | Date | Subject | |
---|---|---|---|
Next Message | Bo Victor Thomsen | 2022-11-08 04:42:17 | Re: Allowing users to create objects in version controlled schema |
Previous Message | Wells Oliver | 2022-11-08 01:19:02 | Re: Allowing users to create objects in version controlled schema |