Re: Best non-networked front end for postgresql - Mailing list pgsql-general

From Adrian Klaver
Subject Re: Best non-networked front end for postgresql
Date
Msg-id ab866d27-a982-5fed-9db8-6a6a1c12f71f@aklaver.com
Whole thread Raw
In response to Best non-networked front end for postgresql  (Sherman Willden <operasopranos@gmail.com>)
List pgsql-general
On 01/21/2018 10:57 AM, Sherman Willden wrote:
> Name: Sherman
> 
> Single laptop: Compaq 6710b
> 
> Operating System: Ubuntu 17.10
> 
> Postgresql: 9.6
> 
> Used for: Just me and my home database
> 
> Seeking advice: Best non-networked front-end
> 
> Considerations: I am retired and want to create my own database and 
> database captures. I have experience with PERL

Can you explain more what you mean by database captures?

> 
> Basic question 1: Which non-networked front-end would work best for me?
> 
> Basic question 2: I am seriously considering HTML fields to capture and 
> process the information. So to connetct with postgresql what do I need to 
> know? Do I need to know javascript, python, and other languages? How is 
> PERL for something like this?

So does the above mean you want to use a Web based application to enter 
data into your database?

The way I see it you have two components to your question, managing the 
database e.g. creating the database and contained objects and 
manipulating the data within the created objects. For the management 
component Vincenzo's suggestion of pgAdmin or using the Postgres command 
line client psql would work. For the second component, building 
entry/reporting forms it comes down to how involved you want to get into 
coding.

> 
> I am entering the below values by hand into a functional database. I 
> thought that I would create some type of front-end to enter the values 
> and then have the front-end enter the values into the postgresql database.
> 01). visit_date
> 02). start_time
> 03). end_time
> 04). venue (This is the casino name)
> 05). city
> 06). state
> 07). limit (4/8 20/40 etc)
> 08). game (7-card-stud etc)
> 09). variant (fixed-limit no-limit etc)
> 10). high-low (mixed-high-low high-only etc)
> 11). buy_in
> 12). cash_out
> 
> Thank you;
> 
> Sherman


-- 
Adrian Klaver
adrian.klaver@aklaver.com


pgsql-general by date:

Previous
From: Tim Clarke
Date:
Subject: Re: Best non-networked front end for postgresql
Next
From: "Peter J. Holzer"
Date:
Subject: Re: How to measure query time - with warm up and cached data