| Key: |
QFJ-362
|
| Type: |
New Feature
|
| Status: |
Open
|
| Priority: |
Default
|
| Assignee: |
Unassigned
|
| Reporter: |
Alvin Wang
|
| Votes: |
0
|
| Watchers: |
0
|
|
If you were logged in you would be able to see more operations.
|
|
|
|
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.
|
|
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. |
Show » |
|
Enhance message and message_log table
