DECLARE
l_limit CONSTANT PLS_INTEGER := 1000;
TYPE varchar2_tab_typ IS TABLE OF VARCHAR2(100) INDEX BY PLS_INTEGER;
varchar2_tab varchar2_tab_typ;
CURSOR grants_cur IS
SELECT 'GRANT SELECT ON '||table_name||' TO some_schema'
FROM user_tables;
BEGIN
varchar2_tab.DELETE;
OPEN grants_cur;
LOOP
FETCH grants_cur BULK COLLECT INTO varchar2_tab LIMIT l_limit;
EXIT WHEN grants_cur%NOTFOUND;
END LOOP;
CLOSE grants_cur;
FOR i IN 1..varchar2_tab.COUNT LOOP
EXECUTE IMMEDIATE varchar2_tab(i);
END LOOP;
END;
/
Saturday, December 10, 2011
Implicit Cursors are Wonderful
I was sent this script for review. Can you see what's wrong with this picture?
Monday, December 5, 2011
Too much of a good thing?
I remember one fateful day when I found the following line of PL/SQL code at a client site
Constants are great. They allow you to rely on a persistent value for processing. They are also really good if you need to use a value again and again in code, the value must be the same throughout the code, and if the value could change due to new requirements, change in direction, etc. For example, your code uses the following constant to denote a value of "True"
At some later point it is decided that the value should simply be the letter 'T' and not 'TRUE'. If you've used the constant throughout your code it's as simple as changing the value of the constant in one place - where it's declared. Quick and easy. That's just good programming.
The g_period example listed above is a little overboard. All the programmer had accomplished was declared a constant of something that is already a constant! If we followed that example we might as well declare every character as a constant and use them everywhere in the code.
Now I can spell my name and never worry about the letters changing!
It looks a little silly when it's put like that, doesn't it?
Using constants properly can save you a lot of pain, and using them improperly can cause just as much pain as you may save. Food for thought.
Happy coding.
g_period CONSTANT VARCHAR2(1) := '.';
Constants are great. They allow you to rely on a persistent value for processing. They are also really good if you need to use a value again and again in code, the value must be the same throughout the code, and if the value could change due to new requirements, change in direction, etc. For example, your code uses the following constant to denote a value of "True"
g_true CONSTANT VARCHAR2(4) := 'TRUE';
At some later point it is decided that the value should simply be the letter 'T' and not 'TRUE'. If you've used the constant throughout your code it's as simple as changing the value of the constant in one place - where it's declared. Quick and easy. That's just good programming.
g_true CONSTANT VARCHAR2(1) := 'T';
The g_period example listed above is a little overboard. All the programmer had accomplished was declared a constant of something that is already a constant! If we followed that example we might as well declare every character as a constant and use them everywhere in the code.
g_c CONSTANT VARCHAR2(1) := 'C'; g_h CONSTANT VARCHAR2(1) := 'H'; g_r CONSTANT VARCHAR2(1) := 'R'; g_i CONSTANT VARCHAR2(1) := 'I'; g_s CONSTANT VARCHAR2(1) := 'S';
Now I can spell my name and never worry about the letters changing!
DECLARE l_my_name VARCHAR2(5); BEGIN l_my_name := g_c||g_h||g_r||g_i||g_s; END; /
It looks a little silly when it's put like that, doesn't it?
Using constants properly can save you a lot of pain, and using them improperly can cause just as much pain as you may save. Food for thought.
Happy coding.
Wednesday, November 16, 2011
Me too
Yup. I have a blog now. I make no promises regarding the frequency of posts, nor do I harbour any delusions on the matter.
Subscribe to:
Posts (Atom)