Subject | Re: [firebird-support] Stored Procedure - Request syncronization error |
---|---|
Author | Ann W. Harrison |
Post date | 2004-07-23T18:00:35Z |
At 01:37 PM 7/23/2004, Luciano Rodrigues wrote:
One stored procedure can invoke another, just as one
program routine can call another.
In 3GL programming, the individual callable pieces are
subroutines. They make code easier write, understand,
and debug. Most 21st century programmers use subroutines.
Look at your stored procedure, break it down into functional
areas, encapsulate each area as its own procedure. You'll
be doing yourself, your employer, and your successors a favor.
The request synchronization error is a bug and should get
fixed. Bugs get fixed faster when the pieces necessary
to reproduce them are part of the bug report.
But do yourself a favor, don't write huge procedures. If
it's big enough to confuse the compiler, think what it
will do to the next unfortunate human who has to change it.
Regards,
Ann
>I´m creating a Stored Procedure that has about 980 lines,Why?
One stored procedure can invoke another, just as one
program routine can call another.
In 3GL programming, the individual callable pieces are
subroutines. They make code easier write, understand,
and debug. Most 21st century programmers use subroutines.
Look at your stored procedure, break it down into functional
areas, encapsulate each area as its own procedure. You'll
be doing yourself, your employer, and your successors a favor.
The request synchronization error is a bug and should get
fixed. Bugs get fixed faster when the pieces necessary
to reproduce them are part of the bug report.
But do yourself a favor, don't write huge procedures. If
it's big enough to confuse the compiler, think what it
will do to the next unfortunate human who has to change it.
Regards,
Ann