DO NOT REPLY [Bug 28908] - Oracle.sql incorrect

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 28908] - Oracle.sql incorrect

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

cvs commit: logging-log4j/src/java/org/apache/log4j/db/dialect postgresql.sql mysql.sql oracle.sql

ceki2004/05/15 11:23:35 Modified:src/java/org/apache/log4j/db/dialect postgresql.sql mysql.sql oracle.sql Log: Wider fields, minor changes... Revision ChangesPath 1.7 +1 -1 logging-log4j/src/java/org/apache/log4j/db/dialect

RE: Oracle.sql incorrect

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

RE: oracle.sql

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

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 w

Re: Oracle.sql incorrect

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

RE: oracle.sql

27; > Subject: 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 c

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

RE: oracle.sql

- > From: James Stauffer [SMTP:[EMAIL PROTECTED] > Sent: Thursday, 13 May 2004 6:47 AM > To: '[EMAIL PROTECTED]' > Subject: oracle.sql > > One more update to the trigger. I couldn't get it to work without the > variable. I am not familiar with triggers ver

oracle.sql

Title: oracle.sql One more update to the trigger.  I couldn't get it to work without the variable.  I am not familiar with triggers very much but our app uses a lot of them so I have a lot of examples that are very close to this.  Basically, I don't know if this is the best way bu

cvs commit: logging-log4j/src/java/org/apache/log4j/db/dialect postgresql.sql mysql.sql oracle.sql

ceki2004/05/12 07:59:53 Modified:src/java/org/apache/log4j/db/dialect postgresql.sql mysql.sql oracle.sql Log: *** keyword substitution change *** Revision ChangesPath 1.6 +42 -42 logging-log4j/src/java/org/apache/log4j/db/dialect

cvs commit: logging-log4j/src/java/org/apache/log4j/db/dialect oracle.sql

ceki2004/05/12 07:57:33 Modified:src/java/org/apache/log4j/db/dialect oracle.sql Log: Changes based input by by James Stauffer ( jstauffe at spscommerc zzot com) Revision ChangesPath 1.6 +27 -22logging-log4j/src/java/org/apache/log4j/db/dialect/oracle.sql

RE: Oracle.sql incorrect

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

RE: Oracle.sql incorrect

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

RE: Oracle.sql incorrect

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

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

RE: Oracle.sql incorrect

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

RE: Oracle.sql incorrect

So what does the oracle.sql file look like now? At 02:47 PM 5/12/2004, you wrote: 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

RE: Oracle.sql incorrect

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

RE: Oracle.sql incorrect

0 AMTo: 'Log4J Developers List'Subject: Oracle.sql incorrect My changes where: Prefix comment lines with "--".  "#" didn't parse. BIGINT -> NUMBER(20) TEXT -> VARCHAR2(4000) SMALLINT -> NUMBER(5) INT -> NUMBER(10) VARCHAR -> VARCHAR2 I also had to cha

DO NOT REPLY [Bug 28908] - Oracle.sql incorrect

gzilla/show_bug.cgi?id=28908 Oracle.sql incorrect --- Additional Comments From [EMAIL PROTECTED] 2004-05-12 12:26 --- Created an attachment (id=11521) Updated diff with white space changes removed - To unsubscribe, e-mail:

Oracle.sql incorrect

Title: Oracle.sql incorrect My changes where: Prefix comment lines with "--".  "#" didn't parse. BIGINT -> NUMBER(20) TEXT -> VARCHAR2(4000) SMALLINT -> NUMBER(5) INT -> NUMBER(10) VARCHAR -> VARCHAR2 I also had to change the trigger to use a declar

DO NOT REPLY [Bug 28908] - Oracle.sql incorrect

gzilla/show_bug.cgi?id=28908 Oracle.sql incorrect [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |ASSIGNED Priority

DO NOT REPLY [Bug 28908] - Oracle.sql incorrect

gzilla/show_bug.cgi?id=28908 Oracle.sql incorrect --- Additional Comments From [EMAIL PROTECTED] 2004-05-11 22:40 --- Diff's can be hard to read, but is this basically changing all 'int' columns to INTEGER(10) and BIGINTS to INTEGER(20)? If this is the case, then I would +

RE: org\apache\log4j\db\dialect\oracle.sql

Title: org\apache\log4j\db\dialect\oracle.sql That would be most appreciated. -Original Message-From: James Stauffer [mailto:[EMAIL PROTECTED]Sent: Wednesday, 12 May 2004 3:18 AMTo: '[EMAIL PROTECTED]'Subject: org\apache\log4j\db\dialect\oracle.sql The current

DO NOT REPLY [Bug 28908] - Oracle.sql incorrect

gzilla/show_bug.cgi?id=28908 Oracle.sql incorrect [EMAIL PROTECTED] changed: What|Removed |Added Severity|Major |Normal --- Additional Comments From

DO NOT REPLY [Bug 28908] - Oracle.sql incorrect

gzilla/show_bug.cgi?id=28908 Oracle.sql incorrect --- Additional Comments From [EMAIL PROTECTED] 2004-05-11 18:07 --- Created an attachment (id=11514) src/java/org/apache/log4j/db/dialect/oracle.sql update to work with Orac

DO NOT REPLY [Bug 28908] New: - Oracle.sql incorrect

gzilla/show_bug.cgi?id=28908 Oracle.sql incorrect Summary: Oracle.sql incorrect Product: Log4j Version: 1.3alpha Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: Other Component: Ap

org\apache\log4j\db\dialect\oracle.sql

Title: org\apache\log4j\db\dialect\oracle.sql The current version of org\apache\log4j\db\dialect\oracle.sql doesn't run on my Oracle instance (9.2).  After I get it to work should I create a bugzilla issue with my changes? James Stauffer

cvs commit: logging-log4j/src/java/org/apache/log4j/db/dialect oracle.sql

ceki2004/05/04 03:04:42 Modified:src/java/org/apache/log4j/db/dialect oracle.sql Log: - Added (untested!) support for oracle dialect. - Added missing Apache copyright Revision ChangesPath 1.2 +32 -4 logging-log4j/src/java/org/apache/log4j/db/dialect

cvs commit: logging-log4j/src/java/org/apache/log4j/db/dialect postgresql.sql MySQLDialect.java mysql.sql oracle.sql SQLDialect.java PostgreSQLDialect.java

/apache/log4j/db/dialect postgresql.sql MySQLDialect.java mysql.sql oracle.sql SQLDialect.java PostgreSQLDialect.java Log: An initial draft of DBAppender. It seems to work on MySQL and PostgreSQL using the URLConnectionSource Revision Changes