Appserver

[kenny.willems]

Procedures/Functions

Hi everyone

I've got a question for you all. In the company i'm working, we have several super procedures with a lot of procedures and functions. We tried to group our procedures/functions as good as we can. (i.e. a super procedure with proc/func about articles, a super procedure with proc/func about orders, and so on...)

This is working fine. But i'm wondering how you guys are working. Do you have general procedures to get data, do you do the same thing like us, ...

When you have procedures that gets data in a certain temp-table, do you create several procedures or do you create one procedure with several parameters? (like a 'get-all-articles' procedure, a 'get-articles-by-colour' procedure, ...)

I think we can increase our perfomance a lot, so all ideas / ways of working / tips are welcome

 

[TomBascom]

What is the relevance of the title to the body of the post?

I tend to group procedures into "libraries" as you've described. An additional distinction that I make is to keep procedures which require a database connection separate from those which do not.

 

[tamhas]

Re: Procedures/Functions

Depending on version, you might want to consider encapsulating such things in classes instead of SP. If you think of it that way, then it might be clearer what is a good grouping. See, for example, http://www.cintegrity.com/content/Why-Are-People-Talking-About-Good-OO