Comment 2 for bug 755004

I think that makes sense in general. For our needs specifically, I
think we’ll be using all (or nearly all) strings. However, assuming
“value” is a kwarg in pymqi, I would assume the default value should
be None and the default type should be MQTYPE_NULL.

Phil

On Wed, Apr 27, 2011 at 3:19 PM, Dariusz Suchojad
<email address hidden> wrote:
> So I'm implementing MQSETMP right now and wonder what the default data
> type should be. I guess string will do, no? Most of the message
> properties will be strings not some fancy MQTYPE_FLOAT32 and that's what
> we should default to? What to do you think?
>
> --
> You received this bug notification because you are a direct subscriber
> of the bug.
> https://bugs.launchpad.net/bugs/755004
>
> Title:
>  Setting message properties
>
> Status in Python interface to WebSphere MQ:
>  Confirmed
>
> Bug description:
>  It has been reported in a private e-mail that PyMQI (as of version
>  1.2) is missing pretty much everything that's need for setting of and
>  querying by custom MQ 7.0-style message properties. These IBM
>  presentations give a good overview of what can be implemented
>  http://j.mp/hmoD2V http://j.mp/gQ2jHk This includes supporting new MQ
>  verbs, such as MQCMHO, MQCRTMH, MQINQMP etc.
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/pymqi/+bug/755004/+subscribe
>