INVALID COULMN NAME EXCEPTION

Question

hi!
again got struck with small thing.i am inserting record in a table using prepare statement.
exception it shows is:
exceptionjava.sql.SQLException: [Microsoft][ODBC driver for Oracle][Oracle]ORA-00904: invalid column name
have look at the following piece of code and table structure.
code ::
PreparedStatement s=conn.prepareStatement("insert into Account_holder_transaction_r values(?,getDate(),?,?,?)");
s.setString(1,accountno);
s.setString(2,vparticulars);
s.setString(3,chequeno);
s.setDouble(4,mdeposit);
rows=s.executeUpdate();
SQL> desc account_holder_transaction_r;
Name Null? Type
CACCOUNT_ID VARCHAR2(20)
CDATE DATE
CPARTICULARS VARCHAR2(40)
CCHECKNUM VARCHAR2(40)
CAMOUNT NUMBER(12,3)

Answer 1

Actually, the lack of column names isn't the problem, (although it's horrible design). Thats valid syntax for Oracle, for inserting a value for all columns in the table in the order the DB happens to have them in.
Syntax:
http://download-east.oracle.com/docs/cd/B19306_01/server.102/b14200/statements_9014.htm
Examples:
http://download-east.oracle.com/docs/cd/B19306_01/server.102/b14200/statements_9014.htm#sthref7305
It's horrible design because:
a) if you add a new column to the table, it breaks the Java code
b) if you do table maintenance that reorders the columns, it breaks the Java code
c) having the columns in the Java code self-documents the relationship between the Java variables and the database columns
The actual problem is the SQL itself. getDate() is not a native Oracle function, the analogous Oracle thing to do if you want the current time on the databse server is to use the SYSDATE pseudo-value, e.g.:
PreparedStatement s=conn.prepareStatement("insert into Account_holder_transaction_r  (CACCOUNT_ID, CDATE, CPARTICULARS, CCHECKNUM, CAMOUNT) values(?,SYSDATE,?,?,?)");This will insert the current time on the dababasse server as of the moment the executeUpdate is performed on the database. (If the times of the database server and the Java application server are not synchronized, this can be confusing).
Besides that, the stack trace tells us that you're using an MS ODBC driver; you probably ought to look very very seriously at using the Oracle JDBC driver.