Title: RE: Oracle.sql incorrect
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
Title: RE: oracle.sql
I just tries it in SQL*Plus and it works for me. Go figure. :-)
James Stauffer
-Original Message-
From: Simon Dorrat [mailto:[EMAIL PROTECTED]]
Sent: Thursday, May 13, 2004 9:01 PM
To: 'Log4J Developers List'
Subject: RE: oracle.sql
Yes, work
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 w
Ceki Gülcü wrote:
At 02:47 PM 5/12/2004, James Stauffer wrote:
It appears the only thing wrong with the trigger is that it needs "/"
on the line right after it ends.
What's with the "/" voodoo? :-)
"/" is used in sqlplus to execute all the lines in the current buffer.
Using certain commands i
an do more research into why it isn't working for me.
>
> -Original Message-
> From: Simon Dorrat [ <mailto:[EMAIL PROTECTED]>]
> Sent: Thursday, May 13, 2004 7:02 PM
> To: 'Log4J Developers List'
> Subject: RE: oracle.sql
>
>
>
Title: RE: oracle.sql
I would get a parse error when I tried to run it without the variable. It might have been the tool I was using (Benthic Golden32), but I couldn't get it to work without the variable. If it works for you without the variable then I can do more research into why it
What was the error? You should not need a variable - the following code
should work fine.
SELECT logging_event_id_seq.NEXTVAL
INTO :new.event_id
FROM dual
Doesn't make that much difference, but simpler is better!
Simon
> -Original Message-
> From: Jame
Title: RE: Oracle.sql incorrect
It seems to be mean "run" or "execute". I know that without it I get a parse error. In Oracle SQL Plus "/" causes the last command to run (again).
James Stauffer
-Original Message-
From: Ceki Gülcü [mailto:[EMAIL PRO
Title: RE: Oracle.sql incorrect
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:[EMAIL PROTECTED]]
Sent: Wednesday, May 12, 2
AIL PROTECTED]>mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 12, 2004 7:33 AM
To: 'Log4J Developers List'
Subject: RE: Oracle.sql incorrect
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.
James
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 ->
Title: RE: Oracle.sql incorrect
The warning can probably now be removed also. :-)
--- Begin file
-- This SQL script creates the required tables by org.apache.log4j.db.DBAppender and
-- org.apache.log4j.db.DBReceiver.
--
-- It is intended for Oracle databases
gt;mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 12, 2004 7:33 AM
To: 'Log4J Developers List'
Subject: RE: Oracle.sql incorrect
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.
James Stauffer
-
Title: RE: Oracle.sql incorrect
It appears the only thing wrong with the trigger is that it needs "/" on the line right after it ends.
Also, for me it has been helpful to have the drop commands in the file. Do we want to included them in a comment?
--drop TRIGGER logging_event_i
Title: Message
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.
James
Stauffer
-Original Message-From: James Stauffer
[mailto:[EMAIL PROTECTED] Sent: Wednesday, May 12, 2004 7:20
AMTo: 'Log4J Developer
15 matches
Mail list logo
