Open aviav opened 3 months ago
This should be easy. org-element stores all node property values as strings (even timestamps), so they will need to be parsed using org-ml-from-string or similar. Other than that org-element does care and shouldn't be affected by the caveats in the reddit thread so long as the property drawer is valid
Thanks for the info! I'll look into it as soon as I encounter this as an obstacle again. I think for the use case that I had in the beginning of the week, I made into sub-headlines what I had first set out to describe using timestamp properties, which is already well-supported by org-sql
Another day, another feature I'd like to have: Timestamps can be used in/as property values, like in
If I implement this, my first idea would be to, in addition to parsing the timestamp and adding it to the timestamps table, add a
property_timestamps
table, inspired byheadline_properties
, since this is howorg-sql
tracks one-to-many relationships from what I can tell.As always, I'd appreciate thoughts on this.
As an aside, I found a Reddit post where somebody started to catalogue places where one can use timestamps in Org Mode, and what difference the place makes to how the timestamp is interpreted.