Thank you for clarification.
I perform "insert" a new row into a table is the union is not matched and "update" the row when it matched, the script compilation fine.
thank you all again.
Bach-Nga
No one in this world is pure and perfect. If you avoid people for their mistakes you will be alone. So judge less, love and forgive more.
No one in this world is pure and perfect. If you avoid people for their mistakes you will be alone. So judge less, love and forgive more.
To call him a dog hardly seems to do him justice though in as much as he had four legs, a tail, and barked, I admit he was, to all outward appearances. But to those who knew him well, he was a perfect gentleman (Hermione Gingold)
**Live simply **Love generously **Care deeply **Speak kindly.
*** Genuinely rich *** Faithful talent *** Sharing success
On Tuesday, September 24, 2019, 12:32:20 PM EDT, George Neuner <gneuner2@xxxxxxxxxxx> wrote:
On Mon, 23 Sep 2019 15:48:06 +0000 (UTC), Pepe TD Vo
<pepevo@xxxxxxxxx> wrote:
>Yes, I heard MERGE is not a command in Postgres but the others said
>merge statement added stored procedures in version 11
>
>I upgraded my postgresql from 10.6 to 11.1. in AWS, still not work.
>thank you,
>Bach-Nga
You misunderstood.
Postrgesql added stored procedures in version 11. Unlike stored functions (which PG has had forever), stored procedures allow transactions within their code. This is similar to the stored procedures in Oracle and it helps with Oracle -> Postgresql conversions.
However, Postgresql does NOT and never did have a MERGE command. The "documentation" page you discovered was just a proposal for an implementation that never happened.
Postgresql can detect conflicts on INSERT and perform an UPDATE instead (see https://www.postgresql.org/docs/current/sql-insert.html). This is not exactly the same as Oracle's MERGE so you'll have to study it carefully to make you understand the nuances and be sure it works as intended in your application ... but it is the closest you can get using Postgresql.
George
>Yes, I heard MERGE is not a command in Postgres but the others said
>merge statement added stored procedures in version 11
>
>I upgraded my postgresql from 10.6 to 11.1. in AWS, still not work.
>thank you,
>Bach-Nga
You misunderstood.
Postrgesql added stored procedures in version 11. Unlike stored functions (which PG has had forever), stored procedures allow transactions within their code. This is similar to the stored procedures in Oracle and it helps with Oracle -> Postgresql conversions.
However, Postgresql does NOT and never did have a MERGE command. The "documentation" page you discovered was just a proposal for an implementation that never happened.
Postgresql can detect conflicts on INSERT and perform an UPDATE instead (see https://www.postgresql.org/docs/current/sql-insert.html). This is not exactly the same as Oracle's MERGE so you'll have to study it carefully to make you understand the nuances and be sure it works as intended in your application ... but it is the closest you can get using Postgresql.
George
