| overflow of oracle.xml.sql.dml.OracleXMLSave.insertXML() [message #91835] |
Mon, 24 March 2003 10:30  |
Brian
Messages: 38
Registered: October 1999
|
Member |
|
|
Does anyone know of a way to change the default behavior of oracle.xml.sql.dml.OracleXMLSave.insertXML() for choosing a larger java number type.
Based on testing, OracleXMLSave.insertXML() defaults to signed integer in Java for inserts into the Oracle table. (BTW, the Oracle columns for what I'm inserting are using Oracle NUMBER type).
I need to insert numbers larger than 2147483647 using the Oracle XML loader.
Thanks,
Brian
|
|
|
|
| Re: overflow of oracle.xml.sql.dml.OracleXMLSave.insertXML() [message #91879 is a reply to message #91835] |
Thu, 19 June 2003 09:29  |
Brian
Messages: 38
Registered: October 1999
|
Member |
|
|
Just posting the solution to this problem in case someone else runs into this problem in the future.
I've determined that if the column is a NUMBER type (without a precision value), oracle.xml.sql.dml.OracleXMLSave.insertXML() will default to type Integer. If the column is changed to have a larger precision (ie NUMBER(15)), oracle.xml.sql.dml.OracleXMLSave.insertXML() will match the column type and you can insert values larger than INT (in this example, up to NUMBER(15)).
Brian
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
