Click here to Skip to main content
15,307,242 members
Please Sign up or sign in to vote.
0.00/5 (No votes)
See more:
The code looks to be running with no error, but no result is printing

What I have tried:

I have tried implementing the below code:

from pandas.core.frame import DataFrame
import cx_Oracle
import pandas as pd
import sys

class IFTDataCore:
    def __init__(self, accountCode):
            i = 0
            all_Procedures = []
            dns_tns = cx_Oracle.makedsn("", "1525", "INVU")
            db=cx_Oracle.connect("CORP-SVC-IFT", "C$Rp$vc1ftUat",dns_tns)
            cursor = db.cursor()
            cursor.execute("select procedure_name from all_procedures where object_name = 'PK_IVZ_IFT_EXTRACT' ")
            rows = cursor.fetchall()
            procedureName = ['PK_IVZ_IFT_EXTRACT.'+str(list(rows[indexRow])[0]) for indexRow in range(0,len(list(rows)))]
            l_cur = cursor.var(cx_Oracle.CURSOR)
            while i < len(procedureName):
                if procedureName[i] == 'PK_IVZ_IFT_EXTRACT.SP_IVZ_IFT_EXTRACT_ACCOUNTS':   
                    ret_cursor  = cursor.callproc(procedureName[i],(l_cur,))
                    dfx = pd.DataFrame(ret_cursor[0])  
                    ret_cursor  = cursor.callproc(procedureName[i],(l_cur,accountCode))
                    dfx = pd.DataFrame(ret_cursor[0])  
            i += 1
            self.all_Procedures = all_Procedures
        except Exception as err:

    def getallProcedures(self):
        return self.all_Procedures

if __name__ == '__main__':
    Procedures = []
    all_Proc  = IFTDataCore('TOUHI')
    Procedures = all_Proc.getallProcedures()

PS: The code works fine if I do not put the logic in init and call the def logic directly in code. Please let me know the possible reason why when class initialization is done in main, the definition is not called as no output is coming.
Updated 27-Jun-21 20:21pm
Richard MacCutchan 27-Jun-21 10:01am
Impossible to tell, as the error appears to be in response to an SQL command sent to Oracle. You need to use the debugger to find out exactly what data it is complaining about.

1 solution

Having your code run does not mean your code is right! :laugh:
Think of the development process as writing an email: compiling successfully means that you wrote the email in the right language - English, rather than German for example - not that the email contained the message you wanted to send.

So now you enter the second stage of development (in reality it's the fourth or fifth, but you'll come to the earlier stages later): Testing and Debugging.

Start by looking at what it does do, and how that differs from what you wanted. This is important, because it give you information as to why it's doing it. For example, if a program is intended to let the user enter a number and it doubles it and prints the answer, then if the input / output was like this:
Input   Expected output    Actual output
  1            2                 1
  2            4                 4
  3            6                 9
  4            8                16
Then it's fairly obvious that the problem is with the bit which doubles it - it's not adding itself to itself, or multiplying it by 2, it's multiplying it by itself and returning the square of the input.
So with that, you can look at the code and it's obvious that it's somewhere here:
int Double(int value)
   return value * value;

Once you have an idea what might be going wrong, start using the debugger to find out why. Put a breakpoint on the first line of the method, and run your app. When it reaches the breakpoint, the debugger will stop, and hand control over to you. You can now run your code line-by-line (called "single stepping") and look at (or even change) variable contents as necessary (heck, you can even change the code and try again if you need to).
Think about what each line in the code should do before you execute it, and compare that to what it actually did when you use the "Step over" button to execute each line in turn. Did it do what you expect? If so, move on to the next line.
If not, why not? How does it differ?
Hopefully, that should help you locate which part of that code has a problem, and what the problem is.

If you don't know how to use a debugger, then start here: pdb — The Python Debugger — Python 3.9.5 documentation[^]

This is a skill, and it's one which is well worth developing as it helps you in the real world as well as in development. And like all skills, it only improves by use!

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900