src/java/org/apache/log4j/db/dialect/oracle.sql is incorrect. At least with Oracle 9.2 I had to make major changes. I'll attach the patch.
Created attachment 11514 [details] src/java/org/apache/log4j/db/dialect/oracle.sql update to work with Oracle 9.2
It appears the serverity should be normal.
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 +1 this patch, in fact, I'd recommend the use of Integer over int/bigint any day, mainly because of some postgres weirdness that burnt me to a crisp one day. However the patch seems to have lots-o-white-space, so rather than apply the patch as such, should I apply your recommendation of changing the int/bigints to number?
Hello James, Thank you for looking into this. I was expecting that some minor fixes would be required but not changing every single line. What is wrong with an SQL 92 type such as INTEGER? I would much prefer to change the lines which are wrong rather than the lines which get changed while hunting for the lines which were really wrong. My suggestion would be to continue to dialog on log4j-dev. If you agree, I'll close this bug report.
Created attachment 11521 [details] Updated diff with white space changes removed
Tested on my Oracle 9i.
Committed by Elias against log4j/trunk in rev 500776