From: | Dave Page <dpage(at)vale-housing(dot)co(dot)uk> |
---|---|
To: | "'Adam Lang'" <aalang(at)rutgersinsurance(dot)com>, pgsql-interfaces(at)postgresql(dot)org |
Subject: | RE: Connecting remotely. |
Date: | 2000-11-01 17:15:50 |
Message-ID: | 8568FC767B4AD311AC33006097BCD3D61A26FB@woody.vale-housing.co.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-interfaces |
> -----Original Message-----
> From: Adam Lang [mailto:aalang(at)rutgersinsurance(dot)com]
> Sent: 01 November 2000 16:40
> To: pgsql-interfaces(at)postgresql(dot)org
> Subject: Re: [INTERFACES] Connecting remotely.
>
>
> What's the difference between having the client use ADO to talk to the
> database as opposed to an interface using the postgresql
> client libraries?
>
Nothing, I would say. In my mind, Sergio is saying that any app written with
libpq or libpq++ or any other interface that doesn't include some kind of
middleware is broken. Surely that would include psql, pgAccess, pgAdmin,
anything using ODBC written in C or VB or C++?
Or have I missed the point completely?
Regards,
Dave.
>
> > "Adam Lang" <aalang(at)rutgersinsurance(dot)com> el día Wed, 1 Nov
> 2000 09:52:35
> > -0500, escribió:
> >
> > [...]
> > >
> > >What are people's thoughts?
> >
> > people's thoughts are that you really want to design a multi-thier
> > design (for example a 3 layer design), where
> >
> > / client1 (browser)
> > database <---> bussines rules - client2 (browser)
> > (ie. apache, php,...) \ .....
> >
> >
> > if your client has direct access to the database, you
> design is broken...
> >
> > sergio
>
From | Date | Subject | |
---|---|---|---|
Next Message | Adam Lang | 2000-11-01 18:24:30 | Re: Connecting remotely. |
Previous Message | Magnus Hagander | 2000-11-01 17:11:46 | RE: Connecting remotely. |