From: | Dmitry Igrishin <dmitigr(at)gmail(dot)com> |
---|---|
To: | Ravi Krishna <sravikrishna3(at)gmail(dot)com> |
Cc: | cjgunzel(at)gmail(dot)com, pgsql-general(at)lists(dot)postgresql(dot)org, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Do we need yet another IDE (SQL development assistant) for PostgreSQL? |
Date: | 2018-07-15 21:11:31 |
Message-ID: | CAAfz9KMNPJDKe=2TZ7q3coSGEg8U=8dj2SM=xLkE3KtvhKk3=A@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
вс, 15 июл. 2018 г. в 23:51, Ravi Krishna <sravikrishna3(at)gmail(dot)com>:
> 1. dbeaver covers many DBMS and even nosql. Many shops are not one
> product specific. That is definitely a plus.
>
On the other hand it is hard to support unique features of PostgreSQL in a
tool that attempts to cover all the world.
I can't say about DBeaver, but as a rule,
cool-abstracted-cross-DBMS-drivers are often limited and don't support many
unique features of a concrete DBMS.
> 2. Lightweight tool which can run even from command line will be a plus
> for the product you are thinking to develop.
>
Yes. In fact, I have a prototype of such a tool, and use it from command
line are useful. For example,
if I run it in *compilation* buffer of Emacs, I can easily navigate to the
place of error occured at the time of
database/schema deployment.
> 3. Who cares in what language it is developed?
>
Many people, in fact. The reasons are different.
From | Date | Subject | |
---|---|---|---|
Next Message | Martin Mueller | 2018-07-15 22:12:15 | Re: two instances of postgres on the same machine? |
Previous Message | Ravi Krishna | 2018-07-15 20:50:44 | Re: Do we need yet another IDE (SQL development assistant) for PostgreSQL? |