Re: managing multiple db developers
От | S. Bob |
---|---|
Тема | Re: managing multiple db developers |
Дата | |
Msg-id | 07b5ce6b-3669-a652-e731-b24dbdce60e7@quadratum-braccas.com обсуждение исходный текст |
Ответ на | Re: managing multiple db developers ("David G. Johnston" <david.g.johnston@gmail.com>) |
Ответы |
Re: managing multiple db developers
|
Список | pgsql-admin |
PostgreSQL supports schema's as well, a schema in PostgreSQL is a simple namespace, which is a different concept from Oracle but you can accomplish the same thing with a schema, in particular via the "CREATE SCHEMA AUTHORIZATION" approach https://www.postgresql.org/docs/11/sql-createschema.html On 1/15/19 11:07 AM, David G. Johnston wrote: > On Tue, Jan 15, 2019 at 10:44 AM Mark Phillips > <mark.phillips@mophilly.com> wrote: >> When I worked for an Oracle shop, the dba set up individual “schemas” for each developer. That allowed us a database instanceof our own for experiments, including modifying stored procedures and such, without the risk of negative impact onother developers or modifying the stable dev-test and QA databases. >> >> I am wondering how to accomplish a similar arrangement in an postgres cluster. > I recommend leveraging the fact that PostgreSQL lacks per-instance > licensing fees and have each developer run (more or less) > > apt-get install postgresql > > on their personal development virtual machine > > David J. >
В списке pgsql-admin по дате отправления: