You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We think that one of the common operations users/developers want to execute on the database during developing phases, but also on production, is a fast view of table records. At the moment we need to rewrite always the same base query that is always: SELECT * FROM my_beautiful_table. And then add something like "ORDER BY timestamp DESC".
This is a little bit annoying compared to other databases GUI clients.
Describe the solution you'd like.
We would like to have a new item in every table context menu like "Select TOP 1000 rows" (like Microsoft MSSQL) or "View Data" (like DBeaver). That can simply generate the query and add it to the text editor.
The additional feature could be having two more options when a table have a timestamp index that permits to select first top n items in ascending or descending order.
You can get a similiar effect with table_name LIMIT -1000. This will give you the last 1000 rows, but sorted in ascending order.
In general, any query which is just a simple SELECT * FROM can have that part of the clause omitted. The table_name implicitly represents the table with SELECT * FROM in front.
In the meantime, I'll shift this to the UI repo since it is solely a UI change!
Mine is only a suggestion because during the week, me and my colleagues, rewrite always the same stuff that we don't need to do with other clients . The most common thing to do before write the real query is always the same stupid select to take a look at the data 🥲
Activity
nwoolmer commentedon Sep 17, 2024
Hi @enricobenedos ,
You can get a similiar effect with
table_name LIMIT -1000. This will give you the last 1000 rows, but sorted in ascending order.In general, any query which is just a simple
SELECT * FROMcan have that part of the clause omitted. Thetable_nameimplicitly represents the table withSELECT * FROMin front.In the meantime, I'll shift this to the UI repo since it is solely a UI change!
enricobenedos commentedon Sep 19, 2024
Thank you @nwoolmer
Mine is only a suggestion because during the week, me and my colleagues, rewrite always the same stuff that we don't need to do with other clients . The most common thing to do before write the real query is always the same stupid select to take a look at the data 🥲
TSP06 commentedon Oct 22, 2024
hey @enricobenedos i would like to work on this
enricobenedos commentedon Oct 22, 2024
Hello @TSP06, your PR is welcome 👍🏻
HVbajoria commentedon Oct 1, 2025
Hey @enricobenedos ,
I would like to work on this!
HVbajoria commentedon Oct 1, 2025
Hi @enricobenedos,
Tried resolving it: #477
Could you please check once?
PriyanshuRj commentedon Oct 2, 2025
Hi @enricobenedos @emrberk, if this issue is still open, I’d love to take it on and work on a solution.
HVbajoria commentedon Oct 3, 2025
Hi @enricobenedos,
Sorry for the issue with the last PR.
Trying to learn from my mistakes.
Could you please check once and assist me if it is correct this time so that I can update things if required: #480
Thanks a lot!
enricobenedos commentedon Oct 3, 2025
Hi @HVbajoria,
it is nice for me. It is exactly what I mean.
Hope @nwoolmer team / questdb team can validate and approve this PR.
@PriyanshuRj think that it has been solved by @HVbajoria PR.
HVbajoria commentedon Oct 3, 2025
Thanks a lot @enricobenedos