RE: [Quickfix-developers] messages_log table entries

[Sean K. <sea...@pi...>]

Ok.  That's pretty much what I figured.  The direction column would be a =
great addition; the ability to pull either incoming or outgoing messages =
is mainly for troubleshooting production/certification issues and =
operations log viewing.

Thanks!

--Sean

-----Original Message-----
From: Oren Miller [mailto:or...@qu...]
Sent: Wednesday, February 01, 2006 10:33 AM
To: Sean Kirkpatrick
Cc: qui...@li...
Subject: Re: [Quickfix-developers] messages_log table entries


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

We can't really alter the compid's as it would interfere with the=20
counterparties log.  Imagine you have an acceptor running on one=20
machine, and an initiator on another which are connected.  If they are=20
sharing the same database, they will sort of walk all over each other=20
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=20
message is incoming or outgoing.

--oren

Sean Kirkpatrick wrote:

> Hi Oren,
>
> I'm testing with 1.11.0 using the PostgreSQL store/log functionality=20
> and had a question.  I think it's great that the incoming/outgoing=20
> logs have been condensed into the single messages_log table, but I was =

> surprised that the sendercompid / targetcompid column values don't=20
> change to indicate the direction of the message.  I'm guessing these=20
> values are just set based on the sessionID for the configured=20
> session.  Without this functionality the text field has to be grepped=20
> 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=20
> incoming_log table, rather than the messages_log table.  Changing the=20
> name corrected the issue, but without the change, the Log doesn't=20
> write any of the messages.  Just a head's up.
>
> Regards,
>
> Sean Kirkpatrick
>
>
>