A really WEIRD thing!! Maybe you could give me a suggest.... :-(

Question

Hello everyone... I'm trying to create this as follow:
CREATE TABLE OFFICE_DATI_TEST
ID NUMBER NOT NULL,
FIELD1 NUMBER,
FIELD2 NUMBER,
FIELD3 NUMBER,
CONSTRAINT PK_ID_DATI PRIMARY KEY (ID)
USING INDEX TABLESPACE test_indexes
CREATE SEQUENCE SEQ_OFFICE_DATI_TEST
INCREMENT BY 1
START WITH 1
MAXVALUE 1E27
MINVALUE 1
NOCYCLE
NOCACHE
NOORDER;
CREATE TRIGGER TRG_OFFICE_DATI_TEST BEFORE INSERT ON MCROFFICE.OFFICE_DATI_TEST
REFERENCING NEW AS NEW OLD AS OLD FOR EACH ROW
BEGIN
SELECT seq_office_dati_test.NEXTVAL INTO :NEW.ID FROM dual;
END;
CREATE OR REPLACE TYPE T_OFFICE_DATI_TEST IS OBJECT
ID NUMBER,
FIELD1 NUMBER,
FIELD2 NUMBER,
FIELD3 NUMBER,
CONSTRUCTOR FUNCTION T_OFFICE_DATI_TEST(SELF IN OUT NOCOPY T_OFFICE_DATI_TEST)
RETURN SELF AS RESULT
CREATE OR REPLACE TYPE BODY T_OFFICE_DATI_TEST IS
CONSTRUCTOR FUNCTION T_OFFICE_DATI_TEST(SELF IN OUT NOCOPY T_OFFICE_DATI_TEST)
RETURN SELF AS RESULT IS
BEGIN
RETURN;
END;
END;
CREATE OR REPLACE TYPE t_t_office_dati_test AS TABLE OF T_OFFICE_DATI_TEST;
CREATE OR REPLACE FUNCTION FUN_OFFICE_DATI_TEST
RETURN T_T_OFFICE_DATI_TEST PIPELINED PARALLEL_ENABLE IS
BEGIN
DECLARE
TYPE c_office_dati_test IS REF CURSOR;
c1 c_office_dati_test;
out_rec T_OFFICE_DATI_TEST;
BEGIN
OPEN c1 FOR SELECT ID, FIELD1, FIELD2, FIELD3
FROM OFFICE_DATI_TEST;
LOOP
FETCH c1 INTO out_rec;
EXIT WHEN c1%NOTFOUND;
PIPE ROW (out_rec);
END LOOP;
CLOSE c1;
RETURN;
END;
END;
then I do just:
SELECT * FROM TABLE(FUN_OFFICE_DATI_TEST);
and I get an error as this:
ORA-06504: PL/SQL: Return types of Result Set variables or query do not match
ORA-06512: a "FUN_OFFICE_DATI_TEST", line 11
Why?...it's really simple and looks really ok looking at table structure and objects...
even compiling each object no errors appears....
Thanks
Luigi

Answer 1

Why are you making your thing utterly complicated? :(
Luigino wrote:
Hello everyone... I'm trying to create this as follow:
CREATE TRIGGER TRG_OFFICE_DATI_TEST BEFORE INSERT ON MCROFFICE.OFFICE_DATI_TEST
REFERENCING NEW AS NEW OLD AS OLD FOR EACH ROW
BEGIN
SELECT seq_office_dati_test.NEXTVAL INTO :NEW.ID FROM dual;
END;
What the hell is this? Why do you need this trigger when you are just fetching sequence value?
Please explain.
CREATE OR REPLACE TYPE T_OFFICE_DATI_TEST IS OBJECT
ID NUMBER,
FIELD1 NUMBER,
FIELD2 NUMBER,
FIELD3 NUMBER,
CONSTRUCTOR FUNCTION T_OFFICE_DATI_TEST(SELF IN OUT NOCOPY T_OFFICE_DATI_TEST)
RETURN SELF AS RESULT
CREATE OR REPLACE TYPE BODY T_OFFICE_DATI_TEST IS
CONSTRUCTOR FUNCTION T_OFFICE_DATI_TEST(SELF IN OUT NOCOPY T_OFFICE_DATI_TEST)
RETURN SELF AS RESULT IS
BEGIN
RETURN;
END;
END;You are using NO_COPY. Why? Please explain.
>
CREATE OR REPLACE TYPE t_t_office_dati_test AS TABLE OF T_OFFICE_DATI_TEST;
CREATE OR REPLACE FUNCTION FUN_OFFICE_DATI_TEST
RETURN T_T_OFFICE_DATI_TEST PIPELINED PARALLEL_ENABLE IS
BEGINWhat is the function of this begin, when you are not using or writing any code in this outer begin block?
DECLARE
TYPE c_office_dati_test IS REF CURSOR;You want to create a type like this? Why?
c1 c_office_dati_test;
out_rec T_OFFICE_DATI_TEST;
BEGIN
OPEN c1 FOR SELECT ID, FIELD1, FIELD2, FIELD3
FROM OFFICE_DATI_TEST;
LOOP
FETCH c1 INTO out_rec;
EXIT WHEN c1%NOTFOUND;
PIPE ROW (out_rec);
END LOOP;
CLOSE c1;
RETURN;
END;
END;
then I do just:
SELECT * FROM TABLE(FUN_OFFICE_DATI_TEST);
and I get an error as this:
ORA-06504: PL/SQL: Return types of Result Set variables or query do not match
ORA-06512: a "FUN_OFFICE_DATI_TEST", line 11
Why?...it's really simple and looks really ok looking at table structure and objects...Is it? Is it a simple looking structure?
even compiling each object no errors appears....
If it is syntactically correct - then it won't show any compilation errors.
Thanks
LuigiWelcome.
My dear friend, please don't take my words personally. If you have any alternative easy process then you should go for that. Always try to achieve this with a Single SQL. If you cannot then only you should go for PL/SQL and if you are restricted there due to some non availability feature then you can go for Java Based Procedure.
Even if you are using PL/SQL, don't make simple thing complicated. Because, that may hamper your performance, too.
And, finally it will be wise to decide and design your PL/SQL solution in a simpler manner rather than making things more complicated way. Results may not only increase the overhead but also create a maintenance problem in future of that coding.
Hope you get my idea.
My best wishes. :)
Regards.
Satyaki De.