Tim Holloway wrote:I'm pretty sure that columns loaded via setObject will generate SQL text that's equivalent to what that object's toString() method would output. So using setObject on an Integer or Long would be OK, for a Date, the format would probably be wrong, and for arrays and classes that don't have customized toString() methods you'd probably get useless junk.
Yogesh Gandhi wrote:
Someone suggested this to add the agruments to the list while we are going thru the loop
And later use that arguments arraylist and use setObject to populate stmt object
But my question is, is the setObject method can be used in place of setString or setLong or setInteger method without any problems?
Tim Moores wrote:That doesn't sound like the full error message. There should be more lines that give information what package or class is missing, and in which class that happens.
update the war file
That doesn't sound solid. I advise to build an entirely new war file, minus all the source code, so that you have a reliably buildable project.
Ankit Garg wrote:See this tutorial, you have to run your application using Spring not directly by instantiating the class
[MileStoneDTO [mileStoneId=1, orderStageId=1, orderMileStoneName=ABC, orderMileStoneDate=Wed Dec 16 09:52:32 IST 2015, orderMileStoneSourceSystem=OHS, orderMileStoneEndDate=Wed Dec 16 09:52:32 IST 2015], MileStoneDTO [mileStoneId=2, orderStageId=2, orderMileStoneName=DEF, orderMileStoneDate=Wed Dec 16 09:52:32 IST 2015, orderMileStoneSourceSystem=OHS, orderMileStoneEndDate=Wed Dec 16 09:52:32 IST 2015]]
Roel De Nijs wrote:
Yogesh Gandhi wrote:SQL Error: ORA-06552: PL/SQL: Statement ignored
ORA-06553: PL S-382: expression is of wrong type
Pure SQL doesn't understand the boolean data type, although PL/SQL does. So although the function will work if invoked from another PL/SQL block, it won't work in a simple SQL SELECT statement.
So if you need to use it in SQL SELECT statements, use the integer data type as return value and return 0 or 1 instead.