PocketQuery - Cached Result Reverses Column Order

Using Pocket Query v2.0.7, once a query has been cached, the next time it is run (i.e. the results are pulled from the cache) the column order in the result set is reversed.

e.g.

- Query run first time results contain columns: Name, Total.

- Query run second time (results pulled from cache) and results contain columns: Total, Name

When displaying data in a simple table, this is not ideal as once cached the data is no longer presented as originally intended.

Is this a bug? or something wrong with my particular implementation?

Once caching is disabled all works as normal and the column order reflects what is defined in the SQL query.

2 answers

1 accepted

0 votes
Accepted answer

Hi Isaac,

I fixed this issue and it will be a part of PocketQuery 2.1 which will be released soon. Could you test if this early access version fixes your issue?

Regards, Felix (Scandio)

Hi Felix

This appears to have fixed the issue.

Thanks for the quick response and resolution!

Zak.

Hi Isaac - just for your info: PQ 2.1 is officially released now smile

Hi Isaac! I can confirm this. Seems like a bug. I'm investigating...

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted Oct 24, 2018 in Confluence

Atlassian Research opportunity with Confluence templates

Do you use templates with Confluence? Take part in a remote 1-hr workshop. You'll receive USD $100 for your time!   We're looking for people to participate in a   remote 1-hr workshop...

1,134 views 18 14
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you