DO NOT REPLY [Bug 33146] New: - Log4J should accept columns that are NOT NULL with DEFAULT

[bu...@apache.org]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=33146>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=33146

           Summary: Log4J should accept columns that are NOT NULL with
                    DEFAULT
           Product: Log4j
           Version: 1.2
          Platform: All
        OS/Version: Solaris
            Status: NEW
          Severity: minor
          Priority: P4
         Component: Appender
        AssignedTo: log4j-dev@logging.apache.org
        ReportedBy: dominik.stadler@gmx.at


If we use Log4J to log to a database using JDBC, we use setColumn() to define
all the columns that we want to set. Normally if a column is not defined and the
column is nullable, Log4J ignores that column.

If one of the columns is "NOT NULL DEFAULT something", then Log4J complains with
"log4j:ERROR Not ready to append ! Column EVENT_DATE is not nullable, and must
be specified by setLogType() !" 
and will then not write to the database at all, although the column would always
have a value if it is not specified in the insert-statement.

Maybe Log4J can be enhanced to handle columns with "NOT NULL DEFAULT" that are
not defined in the Appender to behave the same way as nullable-columns?

Currently we have to adjust the code and add a statement
  setColumn("event_date~EMPTY~");
to ignore this column.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

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