Re: Do we need yet another IDE (SQL development assistant) for PostgreSQL?
I use Linux exclusively in my business and for development. There is no room in the world these days for a Windows-only product. If people choose to use Microsoft platforms they should expect to purchase Microsoft licenses for their needs. That said, a good, cross-platform tool for Postgresql would be a welcome addition. Pgadmin4 doesn't seem to be doing the trick. At least it is not yet in my distribution's repositories. On July 15, 2018 12:59:08 PM EDT, Dmitry Igrishin wrote: >> >> Hello all, >> >> Colleagues. There is an idea to develop a commercial IDE for PostgreSQL >> under Windows. >> At the initial stage, not so much an IDE, as an assistant for the server >> side development. >> What features would you like to see in such an instrument? Thanks. >> > > -- > Sent from my Android device with K-9 Mail. Please excuse my brevity. >
Re: Do we need yet another IDE (SQL development assistant) for PostgreSQL?
If you decide to proceed on this project there's no need to reinvent the wheel. I use Netbeans for my development. it has quite a good facility for working with databases and I use it regularly with Postgres. Since Netbeans is now licensed under Apache 2 you might find useful code there. Be assured it uses JDBC for access but JDBC is universally available and the folks at Postgresql have done quite a nice job with JDBC drivers. Of course, this already works on all platforms. The implementation is basic but very useful: i.e. a good starting point. On Sun, Jul 15, 2018 at 12:08 PM, Dmitry Igrishin wrote: > Thank you all for your responses! > > Okay, if I decide to start this project, the Linux platform will be > supported. > > As I see it, pgspa (PostgreSQL Server Programming Assistant) should have > both the command line interface, > and the GUI for visualizing some aspects of the work. The tool should be > friendly for your favorite editors (Emacs, > VSCode etc) for easy integration to the daily workflow. (There is no plans > to write feature rich text editor inside > the IDE. It's more rational to provide the integration with the existing > text editors for professional programmers.) > What do you think?
Re: My 1st JDBC and PostgreSQL
Postgresql is a sophisticated database server. You can do what you're
attempting with something like Derby at the connection. But with
Postgresql "you get what you pay for".
1) Insall Postgresql
2) start the database
3) use the interface app psql to create a database;
4) load the JDBC driver in your client and connect.
5) manipulate the database via the JDBC driver.
All these steps are explained quite nicely in the Postgresql documentation
you can find at the web site. The JDBC site is separate but a Google
search will find it for you.
On Wed, Jul 19, 2023 at 5:37 PM Amn Ojee Uw wrote:
> Following the example in :
> https://www.tutorialspoint.com/postgresql/postgresql_java.htm
> I wrote the bellow method :
>
> public void connectToDatabase() throws ClassNotFoundException,
> SQLException {
> try {
> this.perr(this.getDatabaseClass()); //
> org.postgresql.Driver = Class
> this.perr(this.getDatabaseUrl()); //
> jdbc:postgresql://localhost:5432/sara.pgdb = url
> this.perr(this.getUserID());// chispa = user
> this.perr(this.getUserPassword()); // 8UUKZW = password
>
> Class.forName(this.getDatabaseClass().toString());
> conn =
> DriverManager.getConnection(this.getDatabaseUrl().toString(),
> this.getUserID().toString(),
> this.getUserPassword().toString() );
> } catch (final SQLException | ClassNotFoundException e) {
> throw e;
> }
> }
>
> However, it throws an exception that reads :
> Exception in thread "main" org.postgresql.util.PSQLException: FATAL:
> database "sara.pgdb" does not exist
>
> In reference to the above web page, it reads :
> The following Java code shows how to connect to an existing database. If
> the database does not exist, then it will be created and finally a
> database object will be returned.
>
> True, the database file does not exist, but isn't JDBC supposed to
> create it?
>
>
> Any help would be much appreciated.
>
>
>
>
Re: My 1st JDBC and PostgreSQL
You get the value you're willing to work for as a general rule. It takes more effort to admin a real SQL server than an easy embedded DB. Your interpretation is spot on. On Thu, Jul 20, 2023 at 8:18 AM Adrian Klaver wrote: > On 7/19/23 18:11, Chuck Davis wrote: > > Postgresql is a sophisticated database server. You can do what you're > > attempting with something like Derby at the connection. But with > > Postgresql "you get what you pay for". > > Not sure what "you get what you pay for" means in this context? > > My take is you are differentiating between embedded databases such as > Derby and SQLite which are tied to a specific client and client/server > databases like Postgres and MySQL which stand alone and are connected to > by any number of clients. > > > 1) Insall Postgresql > > 2) start the database > > 3) use the interface app psql to create a database; > > 4) load the JDBC driver in your client and connect. > > 5) manipulate the database via the JDBC driver. > > > > All these steps are explained quite nicely in the Postgresql > > documentation you can find at the web site. The JDBC site is separate > > but a Google search will find it for you. > > > > > -- > Adrian Klaver > adrian.kla...@aklaver.com > >
Re: Packaging pgAdmin 4
Have you checked your distro repositories? The distro I use ships pgAdmin together with the latest and previous versions of postgresql. On Sat, Nov 27, 2021 at 10:52 AM Blake McBride wrote: > Greetings, > > I've had ongoing difficulties installing pgAdmin 4. These difficulties > have to do with the way pgAdmin is packaged and distributed. > > For example, I use LinuxMint and Manjaro. The pgAdmin distributions > support neither. Although Mint is a derivative of Ubuntu, lsb_release -cs > returns a value not usable by pgAdmin's distribution system. I had to > tweak internal files to get it to work. > > I'd like to suggest using snap, flatpack, or AppImage. Using one of > these, pgAdmin would be trivial to install on nearly any distro and on > nearly any version of those distros. Secondly, you'd have to maintain far > fewer builds. > > The only negative to using one of these is that the installations would be > a bit larger. This is a very small penalty to get the portable and > convenience these package managers provide. > > Thanks. > > Blake McBride > >
