Re: Stored procedure code no longer stored in v14 and v15, changed behaviour

get_viewdef returns the SELECT statement of a view, no column name specification, while pg_get_function_def returns a CREATE statement. So the implementation is different too. With regards, Martijn Tonies Upscene Productions https://www.upscene.com Database Workbench - developer tool for Oracle,

Re: Stored procedure code no longer stored in v14 and v15, changed behaviour

personally, that would be a corner case compared to day-to-day development of stored code. With regards, Martijn Tonies Upscene Productions https://www.upscene.com Database Workbench - developer tool for Oracle, SQL Server, PostgreSQL, MySQL, InterBase, NexusDB and Firebird. From: Jeremy Smith Sent

Re: Stored procedure code no longer stored in v14 and v15, changed behaviour

red a 'parsed version' (in binary). With regards, Martijn Tonies Upscene Productions https://www.upscene.com Database Workbench - developer tool for Oracle, SQL Server, PostgreSQL, MySQL, InterBase, NexusDB and Firebird.

Re: Stored procedure code no longer stored in v14 and v15, changed behaviour

On Thu, Dec 1, 2022 at 7:59 AM Martijn Tonies (Upscene Productions) wrote: Since version 14, the source code for a stored procedure or function written in plain (compound) SQL, a new feature, is no longer stored in pg_proc.prosrc, instead, there’s an additional column prosqlbody which

Stored procedure code no longer stored in v14 and v15, changed behaviour

code to store the original body in proc.prosrc again? It would be very helpful. With regards, Martijn Tonies Upscene Productions https://www.upscene.com Database Workbench - developer tool for Oracle, SQL Server, PostgreSQL, MySQL, InterBase, NexusDB and Firebird.