Stored procedure implementation instead of hard coded queries In Postgres

210 Views Asked by At

Aurora Postgres 11.9

In SQL Server we strictly follow the good programming practice that "every single call land on DB from the application will be a stored procedure instead of simple queries". In Oracle, we haven't experienced the same thing may be due to select stored procedures required additional cursors, and so on.

Can any expert Postgres person advise me what practice should we follow in progress in this regard and what are pros and cons in this case of Postgres?

In addition in SQL Server we use "rowversion" for data sync with BI and other external modules, is there any built-in alternate available in Postgres or should we have to do it with manual triggers?

0

There are 0 best solutions below