ScriptRunner Fails on stored proceedures

This fails for me with postgres stored procedures

Mar 29 '17 16:03 spyhunter99

I'm sorry to hear that. Feel free to fix the errors, I don't use postgres personnally.

Mar 29 '17 20:03 BenoitDuffez

I think the root cause is that a stored procedure can have a semicolon on it, yet it's technical one sql statement. There's a few keyword checks can be added to detect this situation and treat it as a single command

On Wed, Mar 29, 2017 at 4:48 PM, Benoit Duffez [email protected] wrote:

I'm sorry to hear that. Feel free to fix the errors, I don't use postgres personnally.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/BenoitDuffez/ScriptRunner/issues/6#issuecomment-290220998, or mute the thread https://github.com/notifications/unsubscribe-auth/AB4kGVrSAfYJMP2_kNt9mP5Oj_5Z2jCbks5rqsOQgaJpZM4MtM9O .

Mar 29 '17 22:03 spyhunter99

Did you overcome that issue?

Jun 26 '17 14:06 BenoitDuffez

no, i worked around the issue by redesigning my database setup to no longer need the stored procedures

Jun 26 '17 22:06 spyhunter99