drjdpowell

I've never used Network Streams. It appears to me to be an API that makes TCP communication easier, for a specific use case of a one-way stream. But I've seen, on more than one occasion, people use it build APIs for entirely different use cases, ones that would (in the end) be simpler and more performant to base on straight TCP.

I've done this kind of thing, with a 32-bit-only dll needed from a 64-bit one. Actually, it was two 64-bit Test Stations that both needed the same info from the 32-bit equipment, so having both be Clients of the 32-bit Server worked well. I used the TCP capability of Messenger Library, which is very little effort. One question: why Network Streams? If you are wrapping things in your own API then why not a standard TCP connection? What are Network Streams giving you?

Your DB Browser and LabVIEW are possibly using different versions of sqlite. Can you run this in each to detect the version: select sqlite_version();

Does anyone actually use Variants in clusters in this way? To me, this is not even a tertiary use case of JSONtext, so it would be helpful to hear from people with real-world uses. I am tempted to suggest throwing a "Variants not supported" error, but even that would add overhead which I am loath to do.

Can you attach a small VI demonstrating the error?

Please try this fix: jdp_science_jsontext-1.6.6.106.vip

Issue 92: https://bitbucket.org/drjdpowell/jsontext/issues/92/all-integer-types-needed-for-set-map

Again, Variants are tricky, and have two names and serve two purposes. Viewed as a container of named data, your Variants are just placeholders, not actual data themselves (which is why I suggested in the last post to put a named Variant as Data inside the placeholder).

Consider just not including those parameters. Rather than {"A":123,"B":null,"C":789} just have {"A":123,"C":789}; then "B" will be default. Alternately you could put named-Variant values inside your variants (which teh Variant-to-Data node will pass through: Variants are quite tricky, as they can serve both as a temporary container for a value, and a value itself.

LabVIEW Clusters and Arrays do not map directly onto JSON Objects and Arrays. LabVIEW Clusters are fixed-size ordered sets of optionally-named values JSON Objects are variable-size, unordered sets of must-be-named values LabVIEW Arrays are variable sized ordered sets of values all the same type JSON Arrays are variable sized ordered sets of values that can all be different type So a LabVIEW Cluster with unnamed elements cannot map onto a JSON Object, but can map onto a JSON Array. Similarly, mixed-type JSON Arrays cannot be converted to a LabVIEW array, but can be converted to a LabVIEW cluster (assuming you know the number of elements and types). JSONtext thus supports two mappings for LabVIEW Clusters, as explained in Help>>JDP Science>>JSONtext...

People who wish to use Variants and JSON generally want to do this: Put Static-Typed Data in a Variant in a larger data structure Convert larger structure to JSON Send the JSON somewhere Convert JSON back to larger structure (containing Variant) Convert Variant to Static-Typed Data But Step (4) is a big problem, as at that point we don't have access to the Type-description information to rebuild the Variant. But I say do this: Convert Static-Typed Data to JSON Assemble larger JSON from this subJSON Send the JSON somewhere Extract the subJSON Convert subJSON to Static-Typed Data This avoids the problem, as we only need the Type at the first and last steps,where we statically know the type.

I've had multiple requests to "support Variants", but there is a mismatch between Variants (Data plus full type description including name) and JSON (Data with only weak type info: string, number, etc.). To support unflattening JSON to Variant would require a form something like this: { "VarA":{"Variant type":"long","name":"TypedA","Value":123}, "VarB":{"Variant type":"long","name":"TypedB","Value":456} } But this is a rabbit hole I'm not going down. I'd rather ask "Why are you using Variants here instead of subJSON?" This gives you the behaviour you expect:

That is arguably not a bug, as Variants involves two names: the name of the Variant, and the name of the data contained in the Variant. In your case your empty Variants contain unnamed void data, and JSONtext flattens clusters of unnamed elements as JSON Arrays. It is not obvious if it is the best choice to use the data name rather than the Variant name. However, I am sort of tied to the behaviour of the Variant-to-Data node that I use internally to convert Clusters to Arrays of Variants. See this example: Note that Typed clusters and Clusters of Variants containing Typed Data both convert identically, while Variant elements of a cluster never retain the names of the Variants themselves, just the name on the Data in the Variant). The produced JSON matches these choices, made by the programmers of the Variant-to-Data node.

The Object thing is not where I would spend limited effort in performance improvements, as I would expect the User to actually use the item Values and thus require a copy at some point. I would rather improve the JSONpath search algorithm.

I hope Users can do whatever they want using the lower-level functions plus subJSON with the <JSON> tag.

There is support for Sets and Maps in the latest version; I wouldn't want such things require any kind of "hook".

Alternative (6): all attributes are returned as JSON values. Rather than get the attribute as the actual type, the User would get the attribute as a string, then use From JSON to convert to type. One could make VIMs that combine these two steps, and these VIMs might possibly be made to work with non-JSON attributes as well.

The To-JSON behaviour was copied from the previous LAVA-JSON library. That library had the reverse operation, but it only worked if one provided same-named attributes in the default value. As you point out, this is because we need to know what type to convert the JSON to. Personally, I found this kind of useless, as the whole point of attributes is to have unknown items of unknown type. I had also developed "subJSON" for exactly this use case, and never use Variant Attributes at all. So it kind of got stuck in limbo. I note that the newer Set and Map support doesn't run into this issue, as Sets and Maps have Type. Options: Leave as is, not really supporting Variant Attributes Deprecate the current To-JSON support and fully not support Attributes at all Save Type in the JSON somehow (I don't like this) Use limited JSON types when converting from JSON: String, Float, Boolean As in LAVA-JSON, but using (4) as a fall back if type not supplied Added later: see https://bitbucket.org/drjdpowell/jsontext/issues/39/support-json-to-variant-when-no-datatype where it was proposed to do (4), I think.

That is a case that needs (at least) a better error. Try the path $."" By using the quotes, the name is any JSON string, and can thus handle any name. The unquoted form is for convenience and can't handle all edge cases. BTW, what JSON are you feeding in to that node. It has to be an Object if you want to insert at $.""

Note: latest version supports comments. https://forums.ni.com/t5/JDP-Science-Tools/BETA-version-of-JSONtext-1-6/m-p/4146235#M39

Ah, this can be illustrated with this image: JSONtext does not follow the common error rule of returning default value on any error. Instead, it returns best-efforts, with only sub-elements that produce errors being returned as the supplied default. Here it is only the "B" element, requested as a Float but a String in the JSON, that is returned as default (as explained in the error message). Thus we are doing the Variant-to-Data even on error, in order to get this partial conversion of JSON to Data.

This was originally a method in the early prototype API of JSONtext (pre public release), which is why it has a "default" input. However, I used this (now private) method internally whenever a LabVIEW type is stored as a JSON string (should really have made a separate method). In such use, I found a problem of needing a better description of the error if conversion failed, and for that I needed the actual LVtype. This is not really how I would design it from scratch, but it happened incrementally.

"Git Branches aren't branches; they're just tags pointing to commits" is the first thing one needs to understand about Git.

The various Insert functions, like the subVI on the Right, don't support Pretty Print. I suggest you try Reformat, which can Pretty Print the resulting JSON. Or in the latest 1.6.5 version, just released, try the new "Pretty Print" function, which is faster and supports Comments.

Not sure I understand. The data type is just an array in a cluster; it's not actually protected in any way. It makes a copy if you want an ordered array, but not if you want to just access the circular buffer itself. That you can do by "unbundle".