Обсуждение: Toll Schema Diff
Hello.
Your toll Schema Diff tool has saved me a lot of time and nerves, but I encountered one unpleasant problem when creating scripts for functions. The synchronization strategy involves creating source functions and deleting target functions. In most cases this works. But if a function changes its output type or output parameters, it is not considered an overload in PostgreSQL, and it is impossible to create such a function before deleting it in the target, which leads to script execution errors.
Your toll Schema Diff tool has saved me a lot of time and nerves, but I encountered one unpleasant problem when creating scripts for functions. The synchronization strategy involves creating source functions and deleting target functions. In most cases this works. But if a function changes its output type or output parameters, it is not considered an overload in PostgreSQL, and it is impossible to create such a function before deleting it in the target, which leads to script execution errors.
Hi
On Fri, Jul 28, 2023 at 5:47 PM Дмитрий Иванов <firstdismay@gmail.com> wrote:
Hello.
Your toll Schema Diff tool has saved me a lot of time and nerves, but I encountered one unpleasant problem when creating scripts for functions. The synchronization strategy involves creating source functions and deleting target functions. In most cases this works. But if a function changes its output type or output parameters, it is not considered an overload in PostgreSQL, and it is impossible to create such a function before deleting it in the target, which leads to script execution errors.
Can you please create an issue in GitHub with function definitions on source and target both?
--Regards, Dmitry!
пт, 28 июл. 2023 г. в 17:23, Akshay Joshi <akshay.joshi@enterprisedb.com>:
HiOn Fri, Jul 28, 2023 at 5:47 PM Дмитрий Иванов <firstdismay@gmail.com> wrote:Hello.
Your toll Schema Diff tool has saved me a lot of time and nerves, but I encountered one unpleasant problem when creating scripts for functions. The synchronization strategy involves creating source functions and deleting target functions. In most cases this works. But if a function changes its output type or output parameters, it is not considered an overload in PostgreSQL, and it is impossible to create such a function before deleting it in the target, which leads to script execution errors.Can you please create an issue in GitHub with function definitions on source and target both?--Regards, Dmitry!