Best Practice to structure LR (reuse Parts of SQL)?

Hallo

quite often i use different SQL with the same (or Part of the same) WHERE stuff:

the simplest (e.g. i need to update some 100'000 Categories (takes hours) and whant to know, how many are yet done and how many are open), so i need 2 SQL with the same WHERE Part:

select a, b c where **** and YYY or ZZZ

select count(*) where **** and YYY or ZZZ

Is there a way to "reuse" Parts of one LR in another? (Just i did some changes in one SQL but forgett to do it in the other, and this is not the first time, this happend....)

Thomas

Find more posts tagged with

Comments

Colin_Schmidt

I'mnot sure what you mean by re-using. I re-use parts of SQL a lot of the time. I think we all do. So, I think you mean something different. I have a CASE for nearly all possible SUBTYPEs that I copy-n-paste elsewhere.

I think you're wanting to know perhaps if you can put reusable or generic code someplace to use or reference as a function to save coding time. You can do that with code for getting the path of an object.

Is this what you mean?