Tom Keffer schrieb am Samstag, 2. März 2024 um 13:02:03 UTC+1:
2. I am not aware of a case where it's necessary to insert an xtype
between the others. Let me know if I missed something.
I see 2 cases.
("you" means the XType developer in the following sentences. I am not sure
with my English.)
First is the ArchiveTable class. It calls the general get_aggregate
function and thus also your XType. If you want ArchiveTable handle
get_series aggregations for your XType, you have to insert your XType after
ArchiveTable. But if you implemented aggregations and do not want
XTypeTable handle those aggregations, then you need to insert your XTypes
before XTypeTable. That is, between ArchiveTable and XTypeTable.
If your users want to speed up something and include your XTypes into the
database, they surely want the DailySummaries class handle aggregations.
But that does not mean that you want XTypeTable handle the aggegations of
your XType in the other case. You may have provided your own implementation
of the aggregations. That means you have to insert your XType after
DailySummaries but before XTypeTable.
So I guess if you want your XType to behave in an intuitive way and you
have implemented the aggregations, then you will have to insert it after
ArchiveTable and DailySummaries, but before XTypeTable.
--
You received this message because you are subscribed to the Google Groups
"weewx-development" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to weewx-development+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/weewx-development/7a1cb758-15d8-45ec-af66-7680f4d28dfen%40googlegroups.com.
