Melvin Davidson schrieb am 13.10.2017 um 21:42:
If that is what you need to do, then definitely use multiple schemas.
In PostgreSQL, the only way to do cross db queries / DML, is with the
dblink extension, and from personal use, it is a PIA to use.
dblink is not the only way to do that.
On 10/13/2017 12:47 PM, John R Pierce wrote:
On 10/13/2017 12:29 PM, Igal @ Lucee.org wrote:
The main things that I need to do is:
a) Be able to backup/restore each "part" separately. Looks like
pg_dump allows that for schemas via the --schema=schema argument.
b) Be able to query
On 10/13/2017 12:29 PM, Igal @ Lucee.org wrote:
I have read quite a few articles about multiple schemas vs. multiple
databases, but they are all very generic so I wanted to ask here for a
specific use case:
I am migrating a Web Application from MS SQL Server to PostgreSQL.
For the sake of
On Fri, Oct 13, 2017 at 3:29 PM, Igal @ Lucee.org wrote:
> Hello,
>
> I have read quite a few articles about multiple schemas vs. multiple
> databases, but they are all very generic so I wanted to ask here for a
> specific use case:
>
> I am migrating a Web Application from MS
Hello,
I have read quite a few articles about multiple schemas vs. multiple
databases, but they are all very generic so I wanted to ask here for a
specific use case:
I am migrating a Web Application from MS SQL Server to PostgreSQL. For
the sake of easier maintenance, on SQL Server I have