Skip to content

Default ready to use SELECT TOP query #331

Open

Description

@enricobenedos

Is your feature request related to a problem?

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.

Describe alternatives you've considered.

No response

Full Name:

Enrico Benedos

Affiliation:

Deimos

Additional context

No response

Activity

  1. nwoolmer commented on Sep 17, 2024

    @nwoolmer
    Contributor

    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 * 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!

  2. transferred this issue fromquestdb/questdbon Sep 17, 2024
  3. enricobenedos commented on Sep 19, 2024

    @enricobenedos
    Author

    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 🥲

  4. TSP06 commented on Oct 22, 2024

    @TSP06

    hey @enricobenedos i would like to work on this

  5. enricobenedos commented on Oct 22, 2024

    @enricobenedos
    Author

    Hello @TSP06, your PR is welcome 👍🏻

  6. HVbajoria commented on Oct 1, 2025

    @HVbajoria

    Hey @enricobenedos ,

    I would like to work on this!

  7. HVbajoria commented on Oct 1, 2025

    @HVbajoria

    Hi @enricobenedos,
    Tried resolving it: #477

    Could you please check once?

  8. PriyanshuRj commented on Oct 2, 2025

    @PriyanshuRj

    Hi @enricobenedos @emrberk, if this issue is still open, I’d love to take it on and work on a solution.

  9. HVbajoria commented on Oct 3, 2025

    @HVbajoria

    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!

  10. enricobenedos commented on Oct 3, 2025

    @enricobenedos
    Author

    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.

  11. HVbajoria commented on Oct 3, 2025

    @HVbajoria

    Thanks a lot @enricobenedos

    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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions