From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
---|---|
To: | Alexander Farber <alexander(dot)farber(at)gmail(dot)com>, pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: Should I add a new schema for my application? |
Date: | 2023-04-17 15:38:34 |
Message-ID: | 4ac84894e2bcf19ef0a9e51ba7ab078160a3ea1c.camel@cybertec.at |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Sat, 2023-04-15 at 12:06 +0200, Alexander Farber wrote:
> I am seeking for a general advice if it would be a good idea for a PostgreSQL/PostGIS using application to add a third schema.
>
> I am using postgis/postgis Docker image which comes with "public" schema.
>
> Then I have loaded OpenStreetMap data into the database and have created "osm_schema" for that:
>
> And now I need one more table, for the new mapping feature in my application, which would reference the osm_id column in the planet_osm_roads.
>
> I have not used database schemas at all until yet, I am looking for an advice if I should add a third schema here, just for my application?
I would add another schema.
The "public" schema for the extensions, "osm_schema" for the OpenStreetMap data,
and a third schema for your table. Perhaps you want to add additional objects later.
Yours,
Laurenz Albe
From | Date | Subject | |
---|---|---|---|
Next Message | John Howroyd | 2023-04-17 17:48:36 | Re: Guidance on INSERT RETURNING order |
Previous Message | Siddharth Jain | 2023-04-17 15:37:16 | Question on SSI - Serializable Snapshot Isolation |