From: | Allan Kamau <kamauallan(at)gmail(dot)com> |
---|---|
To: | Reg Me Please <regmeplease(at)gmail(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org, pgsql-interfaces(at)postgresql(dot)org |
Subject: | Re: PGSQL and Javascript |
Date: | 2009-01-30 11:53:05 |
Message-ID: | ab1ea6540901300353w71bb5991j392795006ffb3ad3@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-interfaces |
May be Javascript + JDBC not sure.
But the question is why would you want to do so?
Javascript can be read easily by the user having the javascript
running on their browser. JDBC or any other database connecting client
will want to some how authenticate the user in most cases the
username, password and maybe remote IP is used. This mean that your
javascript will probably contain username and password in order to use
JDBC to connect to the DB, is this favourable?
Allan.
On Fri, Jan 30, 2009 at 1:40 PM, Reg Me Please <regmeplease(at)gmail(dot)com> wrote:
> Hello all.
>
> Is there a way to directly access PGSQL from a Javascript application?
> With no application server intervention, I mean.
> Just like libq allows access from C/C++.
>
> --
> Fahrbahn ist ein graues Band
> weisse Streifen, grüner Rand
>
> --
> Sent via pgsql-general mailing list (pgsql-general(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general
>
From | Date | Subject | |
---|---|---|---|
Next Message | Hannu Krosing | 2009-01-30 11:56:09 | Re: [Plproxy-users] Plproxy functions inside transactions and Pl/pgsql exception handling |
Previous Message | Reg Me Please | 2009-01-30 11:40:36 | PGSQL and Javascript |
From | Date | Subject | |
---|---|---|---|
Next Message | Sean Davis | 2009-01-30 11:56:42 | Re: [INTERFACES] PGSQL and Javascript |
Previous Message | Reg Me Please | 2009-01-30 11:40:36 | PGSQL and Javascript |