Datatype and querymode

What are the possible values for these columns in the sqlth_te table?
And what do they mean?
:scratch:

I was hoping that this SQLTags Custom Driver Guide would help, but it was written prior to SQLTags History. So I guess I’m not much help with your question. Hopefully this guide is useful to someone, though.

Thanks Nathan,

I have that on my desk :slight_smile: Perhaps it could be expanded for tag history?

DataType - the “type class” of the tag, used to tell which column the data comes from.
0 - Int
1 - Float
2 - String
3 - Date/Time

QueryMode - another name for “interpolation” mode, or the “category” of data.
0 - Discrete/Digital
3 - Analog

How’d it go from 0 to 3? 1 used to be analog, but with 7.3 we had to change what analog meant (with compression), so 1=Old style analog, while 3=new compressed analog. 2 means the same as 1, but as a selectable option, which isn’t actually selectable right now (it was used for testing/dev, but we didn’t think it made sense in the release).

For what it’s worth, I’ll throw in a bonus note about what the different analog modes mean:
1 or 2, old style - simple deadband. With 2 values stored, the system only interpolates from V2.timestamp-SC_Exec_Rate.
3, new style - SLIM compression. With 2 values, the system interpolates across the full range from V1.timstamp->V2.timestamp.

The repercussions for this are that graphing the raw data looks more correct with the new system, but discrete values incorrectly classified look worse.

Ok, way more than you asked for.

Yes, I suppose we should update it. I also need to update it for the new option of writing to properties through the write queue table, instead of through config change. (Note: the write queue changes are backwards compatible, so don’t worry if this is the first time you’ve heard of the change).

And of course, soon we’ll have to add in better support for property value changes and custom properties…

Regards,

Oooo, you big tease. How long do I have to wait for this?

I really hope we can work it in to the changes we’re making for 7.4. Can’t say for sure yet, but we’ll see.

Regards,

I’ve lost track of this,

do we have the ability to directly reference custom tag properties? Do I have to wait for 7.5?

Sorry, no, still no custom properties. The properties on UDTs can’t be accessed from outside, and they don’t exist yet in external tags either. We really looked at doing this, but ultimately couldn’t work it in to the very limited schedule (5 weeks) we had for 7.5.

Regards,

Oh well, at least your still thinking about it.