logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From James Stauffer <jstau...@spscommerce.com>
Subject RE: Oracle.sql incorrect
Date Wed, 12 May 2004 14:10:30 GMT
INTEGER/INT and SMALLINT can be left as is.  I just tested it.  I wrongly
assumed that since BIGINT didn't work none of the others would.

James Stauffer


-----Original Message-----
From: Ceki Gülcü [mailto:ceki@qos.ch] 
Sent: Wednesday, May 12, 2004 9:07 AM
To: Log4J Developers List
Subject: Re: Oracle.sql incorrect



James,

After comparing with
http://java.sun.com/j2se/1.3/docs/guide/jdbc/getstart/mapping.html#996857

section: 8.9.7 JDBC Types Mapped to Database-specific SQL Types

my suggestion would be:

BIGINT -> NUMBER(20)   OK
TEXT -> VARCHAR2(4000) OK
SMALLINT -> NUMBER(5), should stay as SMALLINT?
INT -> NUMBER(10),  should be INTEGER?
VARCHAR -> VARCHAR2. OK



At 02:20 PM 5/12/2004, James Stauffer wrote:

>My changes where:
>Prefix comment lines with "--".  "#" didn't parse.
>BIGINT -> NUMBER(20)
>TEXT -> VARCHAR2(4000)
>SMALLINT -> NUMBER(5)
>INT -> NUMBER(10)
>VARCHAR -> VARCHAR2
>

-- 
Ceki Gülcü

      For log4j documentation consider "The complete log4j manual"
      ISBN: 2970036908 http://www.qos.ch/shop/products/clm_t.jsp  



---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org

Mime
View raw message