dchenbecker
commented
15 years ago Based on this line:
oracle.jdbc.driver. OraclePreparedStatement.setObject(OraclePreparedStatement.java:9316)
I have a feeling that we're handing an Object to the driver that doesn't map correctly to the type of the column. For instance, we could be handing a Long to something with type DOUBLE. Normally JDBC drivers attempt to coerce the object based on internal mappings but they don't always match up the same between vendors in my experience. In particular, the fact that "validated" and "superuser" are being defined as NUMBER (because Oracle's JDBC driver doesn't support boolean, http://www.oracle.com/technology/tech/java/sqlj_jdbc/htdocs/jdbc_faq.html#34_05) makes me think that we're handing a java Boolean to the driver. I think that this should be a simple fix with an extra case statement in MetaMapper.
github-importer
I just tried to run the todo app. (http://liftweb.net/docs/getting_started/mod_master.html) against our Oracle (10.2) database. I used Oracle's SQLDeveloper to confirm that the tables had been created and had the right columns. However, when I tried to "Sign Up" in the todo app., I got this stuff right in the browser (nothing in the log): Exception occured while processing /user_mgt/sign_up Message: java.sql.SQLException: Invalid column type
More details about this exception can be found here: http://groups.google.com/group/liftweb/browse_thread/thread/9adaf97d0ccb1fbd
I'm using Lift 1.0.
/Jon