Details
-
Type:
New Feature
-
Status:
Open
-
Priority:
Default
-
Resolution: Unresolved
-
Affects Version/s: None
-
Fix Version/s: Future Releases
-
Component/s: Engine
-
Labels:None
Description
To faciliate user to monitor and manage FIX messages, I think we should add more columns into those 2 tables:
1. time (missing in messages_log)
2. message type
3. msgseqnum (missing in messages_log)
4. id (missing in messages)
5. isInbound (Y/N. Right now, sendercompid is the company and targetcompid is the counterparty. this is confusing from FIX message point of view and it is difficult to differentiate the direction)
Also I suggest to make column naming of these 2 tables be consistent to help developer to reuse code.
1. time (missing in messages_log)
2. message type
3. msgseqnum (missing in messages_log)
4. id (missing in messages)
5. isInbound (Y/N. Right now, sendercompid is the company and targetcompid is the counterparty. this is confusing from FIX message point of view and it is difficult to differentiate the direction)
Also I suggest to make column naming of these 2 tables be consistent to help developer to reuse code.
Activity
- All
- Comments
- History
- Activity
- Subversion Commits
- Builds
Just FYI, the messages table is for message resend and should not be used by anything other than the internal session functionality.