Re: PostgreSQL equivalents to dbms_metadata.get_ddl & dbms_metadata.get_dependent_ddl

Thomas,
Thanks for letting me know about this product. Looking at their page
doesn't fill me with a sense of comfort. There's too little information,
nothing clear about on prem. vs in cloud, no pricing information, etc.
Just a lot of marketing fluff and directions to contact their sales people.

Of course, this doesn't address the fundamental concern which is that
currently PostgreSQL makes it needlessly difficult to get basic database
information, in this case DDL via SQL. Liquibase, like pg_dump, is yet
another utility needed to fill in for this gap in PostgreSQL native
functionality.

I've resigned myself to having assemble the information I need by hand. I
can only hope that the PostgreSQL developers see their way to including it
in future versions.

Thanks again,
rik.

On Mon, Mar 20, 2023 at 12:10 PM Thomas Kellerer <shammat(at)gmx(dot)net> wrote:

> richard coleman schrieb am 20.03.2023 um 16:48:
> > My use case is copying and maintaining the same tables in Oracle and
> > PostgreSQL as well as detecting and applying DDL changes between the
> > two systems.
> We are using Liquibase as a schema migration tool which allows us to
> specify a single "changelog" (using their XML format) that can be
> applied to Oracle and Postgres alike.
>
> So we never need to "compare" definitions, we just run the changelog
> script to update the database schema.
>
> Some differences in e.g. available data types can be dealt with using
> Liquibase's properties or if everything else fails using different
> changesets for Postgres and Oracle (which is typically only needed
> for views and procedural code).
>
>
> Of course it might not be feasible to re-structure your existing
> infrastructure for schema migrations to use a completely different
> approach.
>
> Thomas
>
>
>