From: Erik Wienhold <ewie@ewie.name>
To: Ron <ronljohnsonjr@gmail.com>
To: pgsql-admin@lists.postgresql.org
Subject: Re: Allowing users to create objects in version controlled schema
Date: Tue, 8 Nov 2022 02:10:31 +0100 (CET)
Message-ID: <1581955070.282646.1667869831483@office.mailbox.org> (raw)
In-Reply-To: <4240dcf8-2226-15dc-3a0d-1fd76f8c38bc@gmail.com>
References: <903563259.260181.1667842135503@office.mailbox.org>
<4240dcf8-2226-15dc-3a0d-1fd76f8c38bc@gmail.com>
> On 07/11/2022 21:18 CET Ron <ronljohnsonjr@gmail.com> wrote:
>
> On 11/7/22 11:28, Erik Wienhold wrote:
> > I want to get some feedback on the idea of allowing users to create objects in
> > a database whose schema is already managed with version controlled migrations.
> >
> > One of my team mates is displeased with our setup because he cannot create his
> > own tables without bypassing version control. This is a bad idea IMO even if
> > it's technically possible to give users a reserved shared namespace that is
> > never touched by versioned migrations.
>
> Why does a developer(?) need to create his own tables in a production(?)
> database?
Not developers as in "software developer". They work in QGIS to modify data,
create maps/documents. Also pgAdmin or psql to export CSV. For that purpose
they may also write queries. On the production database of course.
There's also a web application on top where I have more control but I still have
to deal with the database schema.
As far as I can tell, own tables are "necessary" to prepare geometric data for
layouts. Beats me why those tables have to be created that way and where the
data is coming from. Or why it has to be a table and not a view.
Maybe it's the mindset and habit. The team started before I joined. Nobody had
any experience in software development much less database development. It all
started with databases where everybody was superuser. A dumping ground for CSV
imports as I like to call it. I still see a lot of mistakes[1] being made.
That's why I am pushing for version control and proper role management.
[1] https://wiki.postgresql.org/wiki/Don%27t_Do_This
--
Erik
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: ewie@ewie.name, ronljohnsonjr@gmail.com, pgsql-admin@lists.postgresql.org
Subject: Re: Allowing users to create objects in version controlled schema
In-Reply-To: <1581955070.282646.1667869831483@office.mailbox.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox