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. What version of Lift are you using? 1.0, 1.1-SNAPSHOT, or something else? Thanks, Derek On Thu, Jul 23, 2009 at 8:44 AM, Jon <jon.klei...@usit.uio.no> wrote: > > I've now logged it as an issue. > > /Jon > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to liftweb@googlegroups.com To unsubscribe from this group, send email to liftweb+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~----------~----~----~----~------~----~------~--~---
