good morning, happy Monday.
fyi, I upgraded postgres in AWS to 11.1 and the merge function for procedure is still not working. Still complained the same error that:
ERROR: "ecisdrdm.application_cdim" is not a known variable
LINE 14: MERGE INTO ecisdrdm.application_cdim prod
^
SQL state: 42601
Character: 348
v/r,
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 Sunday, September 22, 2019, 10:36:01 PM EDT, Morris de Oryx <morrisdeoryx@xxxxxxxxx> wrote:
Postgres has had stored functions for ages, but only added stored procedures in version 11. Historically, you'll see people calling stored functions in Postgres "stored procedures" as that's what other folks call them. It didn't matter because Postgres only had the one thing. For what's new in Postgres 11 stored procedures, here's a place to look:
The change you're referring to is that a stored procedure (but not a function) has the ability to manage its own transaction blocks.
I actually have no clue...I've only read about the new stored procedures. But if you're coming from Oracle, you're likely looking for PG 11 stored procedures, at least some of the time.
