Skip to content
← Customer Feedback for Devart

dbForge Studio for PostgreSQL

dbForge Studio for PostgreSQL is a GUI tool for managing and developing databases and objects. The IDE for PostgreSQL allows users to create, develop, and execute queries, edit and adjust the code to your requirements in a convenient and user-friendly interface. The tool provides a data editing tool to customize your queries and property window so that users can view all the required information of PostgreSQL database objects they are interested in.

https://www.devart.com/dbforge/postgresql/studio/

dbForge Studio for PostgreSQL

Categories

JUMP TO ANOTHER FORUM

(thinking…)

I suggest you...

(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

3 results found

  1. Show panel with result set if it was previosly hidden

    If panel with result set was hidden it should be unhidden on the next query execution.
    Otherwise it is unclear whether the query has been executed or not.
    For comparison, SSMS behaves this way.

    See a gif: https://i.imgur.com/pN6rvXW.gif

    Steps to reproduce:
    - execute a query
    - hide panel with result set by mouse click to its horizontal border
    - execute a query again

    Expected: the panel with result set is shown.
    Actual: the panel with result set remains hidden.

    If user executes any select-statement he usually wants to see a result set, doesn't he?
    So I don't see any reason…

    3 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    under review  ·  1 comment  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  2. Transaction controls and settings

    BEGIN / COMMIT / ROLLBACK is ignored when pressing "Execute Current Statement". Button / menu item for transaction control do not exists.
    Changing auto-commit mode are helpful, too:
    - auto-commit on
    - auto-commit off => preserve error state
    - auto-commit off with auto rollback
    - auto-commit off with auto save point and rollback (emulates other dbs)

    2 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    under review  ·  0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  3. LIVE RAISE NOTICE MESSAGES

    I see that the RAISE NOTICE in postgresql does print out, but you can't see them until after the query has completed. Most other IDEs print out the notices while the query is running. This is actually quite useful when debugging long running queries. I, like most developers, will add RAISE NOTICE to print out running times, and if a query takes a long time I may cancel the query half way through but already have several messages printed for what I have changed and can see if I have made any progress without having to wait for the entire…

    1 vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    under review  ·  2 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
  • Don't see your idea?