Converting PL/SQL to PL/pgSQL: Key Differences & Challenges Quiz Home › PostgreSQL DBA › Converting PL/SQL to PL/pgSQL: Key Differences & Challenges 📝 Postgres Database Administration – Converting PL/SQL to PL/pgSQL: Key Differences & Challenges 20 questions · 15 min timer · Explanations included · Free 1. Which of the following is a common issue when converting PL/SQL triggers to PL/pgSQL? PL/pgSQL triggers must be written as functions. PL/pgSQL triggers can only be row-level, not statement-level. PL/pgSQL triggers cannot access OLD and NEW values. PL/pgSQL does not support triggers. None 1 out of 20 2. In PL/pgSQL, how are OUT parameters handled differently compared to PL/SQL? PL/pgSQL requires OUT parameters to be explicitly returned. PL/pgSQL requires OUT parameters to be declared as INOUT. PL/pgSQL does not support OUT parameters. PL/pgSQL automatically returns OUT parameters without explicit RETURN statement. None 2 out of 20 Loading questions... 3 out of 20 Loading questions... 4 out of 20 Loading questions... 5 out of 20 Loading questions... 6 out of 20 Loading questions... 7 out of 20 Loading questions... 8 out of 20 Loading questions... 9 out of 20 Loading questions... 10 out of 20 Loading questions... 11 out of 20 Loading questions... 12 out of 20 Loading questions... 13 out of 20 Loading questions... 14 out of 20 Loading questions... 15 out of 20 Loading questions... 16 out of 20 Loading questions... 17 out of 20 Loading questions... 18 out of 20 Loading questions... 19 out of 20 Loading questions... 20 out of 20 Click Submit to see your final score! Previous Start Quiz Next Time's up
