From: | Chuck Davis <cjgunzel(at)gmail(dot)com> |
---|---|
To: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: My 1st JDBC and PostgreSQL |
Date: | 2023-07-20 16:44:35 |
Message-ID: | CAHf=Y_ahnV9vyuNAZqRXnX5R4yW8F8xMB0J=utmVuSizVgek3A@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
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 <adrian(dot)klaver(at)aklaver(dot)com>
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(dot)klaver(at)aklaver(dot)com
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Ron | 2023-07-20 16:52:35 | Re: suggestion about time based partitioning and hibernate |
Previous Message | Anthony Apollis | 2023-07-20 15:47:08 | Re: TSQL To Postgres - Unpivot/Union All |