Given that LoggingEvent properities are Strings and not general Objects, and given that in future versions of DBAppender events may be written in batches instead of one by one, there is not much point in revealing the  event_id as stored in the database to higher level components such as  chainsaw.
Given that LoggingEvent properities are Strings and not general Objects, and
given that in future versions of DBAppender events may be written in
batches instead of one by one, there is not much point in revealing the 
event_id as stored in the database to higher level components such as 
chainsaw.


git-svn-id: a7be136288eb2cd985a15786d66ec039c800a993@310593 13f79535-47bb-0310-9956-ffa450edef68

qos-ch/reload4j,sreekanthpulagam/log4j,sreekanthpulagam/log4j,MuShiiii/log4j,MuShiiii/log4j,prmsheriff/log4j,MuShiiii/log4j,prmsheriff/log4j,prmsheriff/log4j,sreekanthpulagam/log4j,smathieu/librarian_sample_repo_java,sreekanthpulagam/log4j,sreekanthpulagam/log4j,qos-ch/reload4j,prmsheriff/log4j,MuShiiii/log4j,smathieu/librarian_sample_repo_java,qos-ch/reload4j,MuShiiii/log4j,prmsheriff/log4j