Query sort by journal date with nlp-date would broken when clicking label for sort

[danilofaria]

What happened?

Let's say I have a [[Journal]] page I always use as a header in journal entries. If I do a query {{query [[Journal]]}} it will show the blocks in the order of journal dates. But if I switch Table view, then the order is completely random.

Reproduce the Bug

1. Go to Journals

Add

- [[Journal]]
    - my note

On multiple dates.

2. Go to some page and insert the query {{query [[Journal]]}}
3. turn on Table view

Expected Behavior

I would expect the rows in the table to be in the same order as when shown as blocks, i.e sorted by appearance in journals by date. However the order in table mode is totally random.

Screenshots

No response

Desktop Platform Information

No response

Mobile Platform Information

No response

Additional Context

No response

[guypursey]

Possibly related to more fundamental sorting issue in query table view?

#7679

(I also had an issue with dates in query table view, but did some more testing to find there was an issue with sorting in general.)

[danilofaria]

I am currently using the following :result-transform to get around the issue:

 :result-transform (fn [result] 
  (reverse (sort-by (fn [h] (get-in h [:block/page :block/journal-day])) 
           (map (fn [m] 
                  (update m :block/properties (fn [u] 
                                                (assoc u :date 
                                                       (hash-set (get-in m [:block/page :block/original-name])))))) result)
           )))

This will reverse sort results by journal date (such that more recent ones are on top) and will add a property to the table showing the journal page.

Of course it would be nice if this was built-in, but this will do it for now.

[guypursey]

Thanks @danilofaria

Do you use that code within an advanced query within the Logseq Markdown file itself? Or is it a piece of external script?

Would be great to see how this looks too (assuming it looks different to a normal table) if you have time to take a screenshot.

[danilofaria]

@guypursey :result-transform is part of advanced queries.
See an example query:

#+BEGIN_QUERY
{ :query [:find (pull ?b [*])
       :where
          (block-content ?b "[[Journal]]")
       ]
 :result-transform (fn [result] 
  (reverse (sort-by (fn [h] (get-in h [:block/page :block/journal-day])) 
           (map (fn [m] 
                  (update m :block/properties (fn [u] 
                                                (assoc u :date 
                                                       (hash-set (get-in m [:block/page :block/original-name])))))) result)
           )))
}
#+END_QUERY

[guypursey]

@danilofaria Thanks for taking the time to add the further explanation and screenshot. Really appreciated. Hoping to look at this at fixing the underlying issue at some point, unless someone gets there before I do.

[stdword]

Hi, guys! I want to up this bug. It was created at November 2022 and today in Logseq v0.9.1 it is still actual, unfortunately =(
Details:

In demo I've used this instruction from Query Table section.

@Bad3r, does Backlog project on issue mean it won't be fixed in next release?

[cnrpman]

@stdword Sorry for the late reply. I just redo a pass on this ticket today.

Does enabling nlp-date help the sorting?
https://docs.logseq.com/#/page/query%20table?anchor=ls-block-646c1baf-cc3c-444d-bd6a-f394ccb41e56

[stdword]

@cnrpman It works now!! 🚀 for v0.9.8 and my iso-date formats (can't recognize is it sorted by dates or by strings)

But, I still can't use logseq.query/nlp-date:: true because the namespace is omitting by editor:

[cnrpman]

Seems clicking the label for sort would break the namespace. It's not that cool.

Also need some E2E coverage following #7708

[lef-est]

it's also not consistent with tables v2 which is using . instead of namespace for property hierarchy.