From: | Tim Clarke <tim(dot)clarke(at)manifest(dot)co(dot)uk> |
---|---|
To: | <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Best non-networked front end for postgresql |
Date: | 2018-01-21 20:45:55 |
Message-ID: | 5ed13567-f30a-1b1e-6b7a-6bc73899d12c@manifest.co.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 21/01/18 19:05, Vincenzo Romano wrote:
> 2018-01-21 19:57 GMT+01:00 Sherman Willden <operasopranos(at)gmail(dot)com>:
>> 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
>>
>> 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 connect 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?
>>
>> 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
> PGAdmin is among the best tools to manage Postgres.
>
> https://www.pgadmin.org/
>
> As far as a front-end program, perl can be used.
> As well as a number of other languages ranging from C, C++, Java, PHP.
> Almost all languages have a "module" to interact with Postgres databases.
> The best one is IMHO the one you know the best.
>
> P.S.
> The differences between a local Unix socket and a TCP one are rather
> subtle from your point of view.
>
+1 for pgadmin - indeed why bother with anything else for one flat
table? How many rows of data do you envisage?
--
Tim Clarke
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2018-01-21 20:47:36 | Re: Best non-networked front end for postgresql |
Previous Message | Neto pr | 2018-01-21 20:45:54 | How to measure query time - with warm up and cached data |