[This message was posted by Brandon Yuille of BWY Systems <[email protected]> to the "FAST Protocol" discussion forum at http://fixprotocol.org/discuss/46. You can reply to it on-line at http://fixprotocol.org/discuss/read/332f60fa - PLEASE DO NOT REPLY BY MAIL.]
Jens, Thank you so much for this concise explanation! I can not tell you how confused I was about this after reading the spec. Thanks again! Brandon > Hi Rolf, > > Thanks a lot. Did miss that part. I have boiled those sections down for > people having the same trouble reading as me ;) > > All madatory fields are not nullable. All optional fields are nullable. > For operation Default, Copy and Increment the null updates the previous > value. For delta operations the null is bypassed. > > For decimal fields the exponent is nullable if the field is optional > else it is not nullable. Mantise is alway not nullable. > > Length fields follows the parent sequence and is nullable if the > sequence is optional. > > Fast to fix Jens G > > > Hi Jens, > > > > I was maybe a bit terse in my previous reply to you. The bilateral > > agreement I was referring to is the template exchange. The template > > carries the needed info. > > > > For details of when a field is nullable, see sections 10.4, 10.5 of > > the 1.1 spec. > > > > /Rolf [You can unsubscribe from this discussion group by sending a message to mailto:[email protected]] --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Financial Information eXchange" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/fix-protocol?hl=en -~----------~----~----~----~------~----~------~--~---
