Submitted by: Philip Williams (unordained)

Is related to QA653

Votes: 8

32k limit on trigger and stored procedure PSQL bodies isn't normally a problem, but in my case, I'm auto-generating code (workflow procedures & triggers based on workflow definition), and the typical "solution" of splitting the code out into separate procedures isn't nearly as easy to apply. I really don't want to auto-split it into chunks like process0, process1, process2, etc. It's especially bad for triggers, where I'm auto-generating code that deals with NEW and OLD variables -- I can't just hand that off to one (or more) stored procedures, I'd have to auto-generate multiple triggers instead, and then I have to worry about the order in which they run, etc.

So what I'm saying is that there are cases where 32k really is a problem, and it'd be nice to fix. (Next problem: I'm building these procedures IN procedures, using a varchar to hold the DDL before it's executed -- even if the PSQL bodies could be larger than 32k, I'd need better blob-handling / execute-statement(blob) to support the whole mess!)