From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
---|---|
To: | Sherman Willden <operasopranos(at)gmail(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Best non-networked front end for postgresql |
Date: | 2018-01-22 01:07:44 |
Message-ID: | 20180122010744.GC22690@paquier.xyz |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Sun, Jan 21, 2018 at 11:57:39AM -0700, Sherman Willden wrote:
> 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?
PostgreSQL supports a wide range of drivers:
https://wiki.postgresql.org/wiki/List_of_drivers
If you are fluent with perl, with not playing with DBD::Pg then? Here is
its documentation:
https://metacpan.org/pod/DBD::Pg
> 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
This is the kind of area where pgadmin can help I think:
https://www.pgadmin.org/
Still, the most interesting portion in hacking is by doing things
yourself, so why not giving a shot to perl and write your own set of
scripts?
--
Michael
From | Date | Subject | |
---|---|---|---|
Next Message | Rhys A.D. Stewart | 2018-01-22 02:21:39 | Re: array_agg and/or =ANY doesn't appear to be functioning as I expect |
Previous Message | Neto pr | 2018-01-22 00:54:18 | Re: How to measure query time - with warm up and cached data |