If you look at the DBReceiverJob class, you'll see a commented-out line, which is why sequence number was in there:


LoggingEvent previously had a 'setsequencenumber'.

The event_id field isn't preserved in the event and it could be - by having the value set as a property.


On Fri, Aug 3, 2012 at 3:00 AM, Antonio Petrelli <antonio.petrelli@gmail.com> wrote:
I noticed that in DBAppender it uses two IDs in LOGGING_EVENT table:
1. the SEQUENCE_NUMBER column that always is set to 0 and not used anywhere else
2. the EVENT_ID that should be autoincremented and it is used for foreign keys.

Is there a reason for SEQUENCE_NUMBER to exist?
If not, I will prepare a patch to fix it.


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