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 Fri, 14 May 2004 11:16:41 GMT
I also noticed that the size of the field is quite large when using INTEGER
(number(38)).

describe logging_event;
Name	            Null?	Type
SEQUENCE_NUMBER	NOT NULL	NUMBER(20)
TIMESTAMP	      NOT NULL	NUMBER(20)
RENDERED_MESSAGE	NOT NULL	VARCHAR2(4000)
LOGGER_NAME	      NOT NULL	VARCHAR2(254)
LEVEL_STRING	NOT NULL	VARCHAR2(254)
NDC		                  VARCHAR2(4000)
THREAD_NAME		            VARCHAR2(254)
REFERENCE_FLAG		      NUMBER(38)
EVENT_ID	      NOT NULL	NUMBER(38)

James Stauffer


-----Original Message-----
From: Raymond DeCampo [mailto:rdecampo@twcny.rr.com] 
Sent: Thursday, May 13, 2004 10:17 PM
To: Log4J Developers List
Subject: Re: Oracle.sql incorrect


James Stauffer wrote:
> Ceki is correct INTEGER doesn't need to be changed to NUMBER(10).  
> Also
> I think my trigger still isn't correct.  I'll check.
>  

It has been my experience with Oracle that "INTEGER" doesn't mean 
integer.  That is, "INTEGER" is mapped to NUMBER (without adornments). 
A NUMBER will allow non-integer values.

Ray


---------------------------------------------------------------------
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