Re: [Quickfix-developers] messages_log table entries

[Brian E. <azz...@ya...>]

Oren -

Is that actually a realistic scenario? I'm struggling to come up with a situation where someone would have a FIX acceptor and a FIX initiator talking to each other and sharing the same database log file outside of a badly constructed test environment.

Isn't the log file supposed to show what actually was received, as opposed to some normalized view of the message data? Swapping the compIDs changes the message - if I want to reconstruct the message from the log table, I now have to have program logic that can figure out which direction the message was going and denormalize the data. I can't say that I like that design choice.

Of course, I vastly prefered having separate log files. I wouldn't have minded having the option to have a single log (especially if it was *in addition to* the separate logs), but I now have to modify my workflow (and some scripts) to deal with one log. It's kind of a drag.

- Brian Erst
Thynk Software, Inc.

----- Original Message ----
From: Oren Miller <or...@qu...>
To: Sean Kirkpatrick <sea...@pi...>
Cc: qui...@li...
Sent: Wednesday, February 01, 2006 9:32:34 AM
Subject: Re: [Quickfix-developers] messages_log table entries

QuickFIX Documentation: http://www.quickfixengine.org/quickfix/doc/html/index.html
QuickFIX Support: http://www.quickfixengine.org/services.html

Thanks Sean, I checked in a fix for the bug.

We can't really alter the compid's as it would interfere with the 
counterparties log.  Imagine you have an acceptor running on one 
machine, and an initiator on another which are connected.  If they are 
sharing the same database, they will sort of walk all over each other 
and then things will really get confusing.  So the sessionid fields need 
to remain constant so they can act as a key.

One option could be to add a direction column which indicates if a 
message is incoming or outgoing.

--oren

Sean Kirkpatrick wrote:

> Hi Oren,
>
> I'm testing with 1.11.0 using the PostgreSQL store/log functionality 
> and had a question.  I think it's great that the incoming/outgoing 
> logs have been condensed into the single messages_log table, but I was 
> surprised that the sendercompid / targetcompid column values don't 
> change to indicate the direction of the message.  I'm guessing these 
> values are just set based on the sessionID for the configured 
> session.  Without this functionality the text field has to be grepped 
> through to determine the direction of the message.  Was this by design?
>
> I also found a slight bug in the sql scripts packaged to create the db 
> tables.  The messages_log_table.sql file still creates the 
> incoming_log table, rather than the messages_log table.  Changing the 
> name corrected the issue, but without the change, the Log doesn't 
> write any of the messages.  Just a head's up.
>
> Regards,
>
> Sean Kirkpatrick
>
>
>


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Quickfix-developers mailing list
Qui...@li...
https://lists.sourceforge.net/lists/listinfo/quickfix-developers