pg.ddx.io pgsql-interfaces@postgresql.org mailing list archive
help / color / mirror / Atom feedConnecting remotely.
18+ messages / 7 participants
[nested] [flat]
* Connecting remotely.
@ 2000-11-01 14:29 Adam Lang <aalang@rutgersinsurance.com>
2000-11-01 14:50 ` Re: Connecting remotely. Marko Kreen <marko@l-t.ee>
0 siblings, 1 reply; 18+ messages in thread
From: Adam Lang @ 2000-11-01 14:29 UTC (permalink / raw)
To: pgsql-interfaces
This may be a silly question, but how does *nix systems speak to a remote
database without ODBC, like Windows?
As an example, PHP... I have Apache/PHP on one server, and the database on
another. How does it do remote calls?
Adam Lang
Systems Engineer
Rutgers Casualty Insurance Company
^ permalink raw reply [nested|flat] 18+ messages in thread
* Re: Connecting remotely.
2000-11-01 14:29 Connecting remotely. Adam Lang <aalang@rutgersinsurance.com>
@ 2000-11-01 14:50 ` Marko Kreen <marko@l-t.ee>
2000-11-01 14:52 ` Re: Connecting remotely. Adam Lang <aalang@rutgersinsurance.com>
0 siblings, 1 reply; 18+ messages in thread
From: Marko Kreen @ 2000-11-01 14:50 UTC (permalink / raw)
To: Adam Lang <aalang@rutgersinsurance.com>; +Cc: pgsql-interfaces
On Wed, Nov 01, 2000 at 09:29:47AM -0500, Adam Lang wrote:
> This may be a silly question, but how does *nix systems speak to a remote
> database without ODBC, like Windows?
Database's client side libraries take care of that. But that
means linking your app with some particular database library.
e.g. PHP has php_pgsql, php_sybase... if you want your
app to be database-agnostic, you can link it with e.g. UnixODBC,
which should do the database-specific work.
> As an example, PHP... I have Apache/PHP on one server, and the database on
> another. How does it do remote calls?
$db = pg_connect("host=another.net port=5432 ... ");
--
marko
^ permalink raw reply [nested|flat] 18+ messages in thread
* Re: Connecting remotely.
2000-11-01 14:29 Connecting remotely. Adam Lang <aalang@rutgersinsurance.com>
2000-11-01 14:50 ` Re: Connecting remotely. Marko Kreen <marko@l-t.ee>
@ 2000-11-01 14:52 ` Adam Lang <aalang@rutgersinsurance.com>
2000-11-01 16:18 ` Re: Connecting remotely. Sergio A. Kessler <sak@tribctas.gba.gov.ar>
0 siblings, 1 reply; 18+ messages in thread
From: Adam Lang @ 2000-11-01 14:52 UTC (permalink / raw)
To: ; +Cc: pgsql-interfaces
That's what I was figuring... so... is it possible to take those files,
compile them into a dll and make a postgresql-specific remote connection
library? So, say instead of referencing ADO in Visual Basic and using the
ODBC driver, merely wrap up necessary functionality of the client side
libraries? Would that be hard? (Never made a DLL before, so unsure).
Granted it breaks the idea of writing code to use on any database, but if
you are making an in-house application and have control over the database...
Also, it wouldn't help Access oriented people, but this would be used for a
bit more hard core integration, something that if you want, you shouldn't be
using Access for a front end anyway.
What are people's thoughts?
Adam Lang
Systems Engineer
Rutgers Casualty Insurance Company
----- Original Message -----
From: "Marko Kreen" <marko@l-t.ee>
To: "Adam Lang" <aalang@rutgersinsurance.com>
Cc: "pgsql-interfaces" <pgsql-interfaces@postgresql.org>
Sent: Wednesday, November 01, 2000 9:50 AM
Subject: Re: [INTERFACES] Connecting remotely.
> On Wed, Nov 01, 2000 at 09:29:47AM -0500, Adam Lang wrote:
> > This may be a silly question, but how does *nix systems speak to a
remote
> > database without ODBC, like Windows?
>
> Database's client side libraries take care of that. But that
> means linking your app with some particular database library.
> e.g. PHP has php_pgsql, php_sybase... if you want your
> app to be database-agnostic, you can link it with e.g. UnixODBC,
> which should do the database-specific work.
>
> > As an example, PHP... I have Apache/PHP on one server, and the database
on
> > another. How does it do remote calls?
>
> $db = pg_connect("host=another.net port=5432 ... ");
>
> --
> marko
^ permalink raw reply [nested|flat] 18+ messages in thread
* Re: Connecting remotely.
2000-11-01 14:29 Connecting remotely. Adam Lang <aalang@rutgersinsurance.com>
2000-11-01 14:50 ` Re: Connecting remotely. Marko Kreen <marko@l-t.ee>
2000-11-01 14:52 ` Re: Connecting remotely. Adam Lang <aalang@rutgersinsurance.com>
@ 2000-11-01 16:18 ` Sergio A. Kessler <sak@tribctas.gba.gov.ar>
2000-11-01 16:40 ` Re: Connecting remotely. Adam Lang <aalang@rutgersinsurance.com>
0 siblings, 1 reply; 18+ messages in thread
From: Sergio A. Kessler @ 2000-11-01 16:18 UTC (permalink / raw)
To: aalang@rutgersinsurance.com; pgsql-interfaces
"Adam Lang" <aalang@rutgersinsurance.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
^ permalink raw reply [nested|flat] 18+ messages in thread
* Re: Connecting remotely.
2000-11-01 14:29 Connecting remotely. Adam Lang <aalang@rutgersinsurance.com>
2000-11-01 14:50 ` Re: Connecting remotely. Marko Kreen <marko@l-t.ee>
2000-11-01 14:52 ` Re: Connecting remotely. Adam Lang <aalang@rutgersinsurance.com>
2000-11-01 16:18 ` Re: Connecting remotely. Sergio A. Kessler <sak@tribctas.gba.gov.ar>
@ 2000-11-01 16:40 ` Adam Lang <aalang@rutgersinsurance.com>
0 siblings, 0 replies; 18+ messages in thread
From: Adam Lang @ 2000-11-01 16:40 UTC (permalink / raw)
To: pgsql-interfaces
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?
Adam Lang
Systems Engineer
Rutgers Casualty Insurance Company
----- Original Message -----
From: "Sergio A. Kessler" <sak@tribctas.gba.gov.ar>
To: <aalang@rutgersinsurance.com>; <pgsql-interfaces@postgresql.org>
Sent: Wednesday, November 01, 2000 11:18 AM
Subject: Re: [INTERFACES] Connecting remotely.
> "Adam Lang" <aalang@rutgersinsurance.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
^ permalink raw reply [nested|flat] 18+ messages in thread
* RE: Connecting remotely.
@ 2000-11-01 15:32 Dave Page <dpage@vale-housing.co.uk>
2000-11-01 16:36 ` Re: Connecting remotely. Adam Lang <aalang@rutgersinsurance.com>
0 siblings, 1 reply; 18+ messages in thread
From: Dave Page @ 2000-11-01 15:32 UTC (permalink / raw)
To: 'Adam Lang' <aalang@rutgersinsurance.com>; pgsql-interfaces
> -----Original Message-----
> From: Adam Lang [mailto:aalang@rutgersinsurance.com]
> Sent: 01 November 2000 14:53
> Cc: pgsql-interfaces
> Subject: Re: [INTERFACES] Connecting remotely.
>
>
> That's what I was figuring... so... is it possible to take
> those files,
> compile them into a dll and make a postgresql-specific remote
> connection
> library? So, say instead of referencing ADO in Visual Basic
> and using the
> ODBC driver, merely wrap up necessary functionality of the client side
> libraries? Would that be hard? (Never made a DLL before, so unsure).
Many before you have tried this and failed miserably!! :-)
Seriously though, I think you would be creating a horrendous amount of work
for yourself (having considered the idea for 18 months or so myself). IMHO
time would be far better spent writing an OLEDB provider for PostgreSQL (a
native one, not one using the Simple Provider interface). At least then you
can still manipulate data in recordset objects which aren't really that bad
to work with and are very useful when you attach them to a hidden data
control so you can bind other controls to them.
Regards,
Dave.
^ permalink raw reply [nested|flat] 18+ messages in thread
* Re: Connecting remotely.
2000-11-01 15:32 RE: Connecting remotely. Dave Page <dpage@vale-housing.co.uk>
@ 2000-11-01 16:36 ` Adam Lang <aalang@rutgersinsurance.com>
0 siblings, 0 replies; 18+ messages in thread
From: Adam Lang @ 2000-11-01 16:36 UTC (permalink / raw)
To: pgsql-interfaces
Well, I was mostly feeling out ideas... mainly because I don't know how to
write com objects or an OLE DB provider. :P
The 6th through the 10th I have a training course for VB and it gets into
Active X DLLs and Com objects, so naturally I was thinking of what I would
use my new found power for and I thought of that as a possibility.
As for the ole db... does anyone have an idea where to start looking for
that info? Would it have to be written in C? I found a company that sells
software that creates ole dbs...
Adam Lang
Systems Engineer
Rutgers Casualty Insurance Company
----- Original Message -----
From: "Dave Page" <dpage@vale-housing.co.uk>
To: "'Adam Lang'" <aalang@rutgersinsurance.com>;
<pgsql-interfaces@postgresql.org>
Sent: Wednesday, November 01, 2000 10:32 AM
Subject: RE: [INTERFACES] Connecting remotely.
>
>
> > -----Original Message-----
> > From: Adam Lang [mailto:aalang@rutgersinsurance.com]
> > Sent: 01 November 2000 14:53
> > Cc: pgsql-interfaces
> > Subject: Re: [INTERFACES] Connecting remotely.
> >
> >
> > That's what I was figuring... so... is it possible to take
> > those files,
> > compile them into a dll and make a postgresql-specific remote
> > connection
> > library? So, say instead of referencing ADO in Visual Basic
> > and using the
> > ODBC driver, merely wrap up necessary functionality of the client side
> > libraries? Would that be hard? (Never made a DLL before, so unsure).
>
> Many before you have tried this and failed miserably!! :-)
>
> Seriously though, I think you would be creating a horrendous amount of
work
> for yourself (having considered the idea for 18 months or so myself). IMHO
> time would be far better spent writing an OLEDB provider for PostgreSQL (a
> native one, not one using the Simple Provider interface). At least then
you
> can still manipulate data in recordset objects which aren't really that
bad
> to work with and are very useful when you attach them to a hidden data
> control so you can bind other controls to them.
>
> Regards,
> Dave.
^ permalink raw reply [nested|flat] 18+ messages in thread
* RE: Connecting remotely.
@ 2000-11-01 15:35 Clark, Joel <jclark@lendingtree.com>
2000-11-01 16:36 ` Re: Connecting remotely. Adam Lang <aalang@rutgersinsurance.com>
0 siblings, 1 reply; 18+ messages in thread
From: Clark, Joel @ 2000-11-01 15:35 UTC (permalink / raw)
To: 'Adam Lang' <aalang@rutgersinsurance.com>; +Cc: pgsql-interfaces
Yes, you can build libpq into libpq.dll. You can then add the function
declarations at the top, much like you would for an API call. Alternatively
you could wrap a COM object around the DLL and use it that way.
Joel
-----Original Message-----
From: Adam Lang [mailto:aalang@rutgersinsurance.com]
Sent: Wednesday, November 01, 2000 9:53 AM
Cc: pgsql-interfaces
Subject: Re: [INTERFACES] Connecting remotely.
That's what I was figuring... so... is it possible to take those files,
compile them into a dll and make a postgresql-specific remote connection
library? So, say instead of referencing ADO in Visual Basic and using the
ODBC driver, merely wrap up necessary functionality of the client side
libraries? Would that be hard? (Never made a DLL before, so unsure).
Granted it breaks the idea of writing code to use on any database, but if
you are making an in-house application and have control over the database...
Also, it wouldn't help Access oriented people, but this would be used for a
bit more hard core integration, something that if you want, you shouldn't be
using Access for a front end anyway.
What are people's thoughts?
Adam Lang
Systems Engineer
Rutgers Casualty Insurance Company
----- Original Message -----
From: "Marko Kreen" <marko@l-t.ee>
To: "Adam Lang" <aalang@rutgersinsurance.com>
Cc: "pgsql-interfaces" <pgsql-interfaces@postgresql.org>
Sent: Wednesday, November 01, 2000 9:50 AM
Subject: Re: [INTERFACES] Connecting remotely.
> On Wed, Nov 01, 2000 at 09:29:47AM -0500, Adam Lang wrote:
> > This may be a silly question, but how does *nix systems speak to a
remote
> > database without ODBC, like Windows?
>
> Database's client side libraries take care of that. But that
> means linking your app with some particular database library.
> e.g. PHP has php_pgsql, php_sybase... if you want your
> app to be database-agnostic, you can link it with e.g. UnixODBC,
> which should do the database-specific work.
>
> > As an example, PHP... I have Apache/PHP on one server, and the database
on
> > another. How does it do remote calls?
>
> $db = pg_connect("host=another.net port=5432 ... ");
>
> --
> marko
^ permalink raw reply [nested|flat] 18+ messages in thread
* Re: Connecting remotely.
2000-11-01 15:35 RE: Connecting remotely. Clark, Joel <jclark@lendingtree.com>
@ 2000-11-01 16:36 ` Adam Lang <aalang@rutgersinsurance.com>
0 siblings, 0 replies; 18+ messages in thread
From: Adam Lang @ 2000-11-01 16:36 UTC (permalink / raw)
To: Clark, Joel <jclark@lendingtree.com>; +Cc: pgsql-interfaces
That's sort of what I was thinking... Make a reference to it and use it much
like regobj.dll for modifying Registry in windows...
Adam Lang
Systems Engineer
Rutgers Casualty Insurance Company
----- Original Message -----
From: "Clark, Joel" <jclark@lendingtree.com>
To: "'Adam Lang'" <aalang@rutgersinsurance.com>
Cc: "pgsql-interfaces" <pgsql-interfaces@postgresql.org>
Sent: Wednesday, November 01, 2000 10:35 AM
Subject: RE: [INTERFACES] Connecting remotely.
> Yes, you can build libpq into libpq.dll. You can then add the function
> declarations at the top, much like you would for an API call.
Alternatively
> you could wrap a COM object around the DLL and use it that way.
>
> Joel
>
> -----Original Message-----
> From: Adam Lang [mailto:aalang@rutgersinsurance.com]
> Sent: Wednesday, November 01, 2000 9:53 AM
> Cc: pgsql-interfaces
> Subject: Re: [INTERFACES] Connecting remotely.
>
>
> That's what I was figuring... so... is it possible to take those files,
> compile them into a dll and make a postgresql-specific remote connection
> library? So, say instead of referencing ADO in Visual Basic and using the
> ODBC driver, merely wrap up necessary functionality of the client side
> libraries? Would that be hard? (Never made a DLL before, so unsure).
> Granted it breaks the idea of writing code to use on any database, but if
> you are making an in-house application and have control over the
database...
> Also, it wouldn't help Access oriented people, but this would be used for
a
> bit more hard core integration, something that if you want, you shouldn't
be
> using Access for a front end anyway.
>
> What are people's thoughts?
>
> Adam Lang
> Systems Engineer
> Rutgers Casualty Insurance Company
> ----- Original Message -----
> From: "Marko Kreen" <marko@l-t.ee>
> To: "Adam Lang" <aalang@rutgersinsurance.com>
> Cc: "pgsql-interfaces" <pgsql-interfaces@postgresql.org>
> Sent: Wednesday, November 01, 2000 9:50 AM
> Subject: Re: [INTERFACES] Connecting remotely.
>
>
> > On Wed, Nov 01, 2000 at 09:29:47AM -0500, Adam Lang wrote:
> > > This may be a silly question, but how does *nix systems speak to a
> remote
> > > database without ODBC, like Windows?
> >
> > Database's client side libraries take care of that. But that
> > means linking your app with some particular database library.
> > e.g. PHP has php_pgsql, php_sybase... if you want your
> > app to be database-agnostic, you can link it with e.g. UnixODBC,
> > which should do the database-specific work.
> >
> > > As an example, PHP... I have Apache/PHP on one server, and the
database
> on
> > > another. How does it do remote calls?
> >
> > $db = pg_connect("host=another.net port=5432 ... ");
> >
> > --
> > marko
^ permalink raw reply [nested|flat] 18+ messages in thread
* RE: Connecting remotely.
@ 2000-11-01 17:11 Magnus Hagander <mha@sollentuna.net>
0 siblings, 0 replies; 18+ messages in thread
From: Magnus Hagander @ 2000-11-01 17:11 UTC (permalink / raw)
To: 'Adam Lang' <aalang@rutgersinsurance.com>; pgsql-interfaces
> As for the ole db... does anyone have an idea where to start
> looking for that info?
http://msdn.microsoft.com/library/default.asp?URL=/library/psdk/dasdk/oled0c
s7.htm
> Would it have to be written in C? I found a
> company that sells
> software that creates ole dbs...
It shuold be possible to write it in any language that can produce COM
objects which support the OLE-DB interfaces (there are lots of them). C++ is
probably the most common langauge used, but there are examples in Java and
Visual Basic as well (samples available at
http://msdn.microsoft.com/library/default.asp?URL=/library/psdk/dasdk/osp298
xb.htm).
//Magnus
^ permalink raw reply [nested|flat] 18+ messages in thread
* RE: Connecting remotely.
@ 2000-11-01 17:15 Dave Page <dpage@vale-housing.co.uk>
2000-11-01 18:24 ` Re: Connecting remotely. Adam Lang <aalang@rutgersinsurance.com>
2000-11-01 18:55 ` Re: Connecting remotely. ken@ori-ind.com
0 siblings, 2 replies; 18+ messages in thread
From: Dave Page @ 2000-11-01 17:15 UTC (permalink / raw)
To: 'Adam Lang' <aalang@rutgersinsurance.com>; pgsql-interfaces
> -----Original Message-----
> From: Adam Lang [mailto:aalang@rutgersinsurance.com]
> Sent: 01 November 2000 16:40
> To: pgsql-interfaces@postgresql.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@rutgersinsurance.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
>
^ permalink raw reply [nested|flat] 18+ messages in thread
* Re: Connecting remotely.
2000-11-01 17:15 RE: Connecting remotely. Dave Page <dpage@vale-housing.co.uk>
@ 2000-11-01 18:24 ` Adam Lang <aalang@rutgersinsurance.com>
1 sibling, 0 replies; 18+ messages in thread
From: Adam Lang @ 2000-11-01 18:24 UTC (permalink / raw)
To: pgsql-interfaces
So in other words I should have a client that talks to a server application,
which in turn talks to the database?
Again, this n-tier stuff is nice if the person writing the app has to do it
independent of a back end, but when you are writing for a specific
instances, all it seems to do is make things harder...
Adam Lang
Systems Engineer
Rutgers Casualty Insurance Company
----- Original Message -----
From: "Dave Page" <dpage@vale-housing.co.uk>
To: "'Adam Lang'" <aalang@rutgersinsurance.com>;
<pgsql-interfaces@postgresql.org>
Sent: Wednesday, November 01, 2000 12:15 PM
Subject: RE: [INTERFACES] Connecting remotely.
>
>
> > -----Original Message-----
> > From: Adam Lang [mailto:aalang@rutgersinsurance.com]
> > Sent: 01 November 2000 16:40
> > To: pgsql-interfaces@postgresql.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@rutgersinsurance.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
> >
^ permalink raw reply [nested|flat] 18+ messages in thread
* Re: Connecting remotely.
2000-11-01 17:15 RE: Connecting remotely. Dave Page <dpage@vale-housing.co.uk>
@ 2000-11-01 18:55 ` ken@ori-ind.com
1 sibling, 0 replies; 18+ messages in thread
From: ken@ori-ind.com @ 2000-11-01 18:55 UTC (permalink / raw)
To: Adam Lang <aalang@rutgersinsurance.com>; pgsql-interfaces
For single tier access to pg via libpq.dll check out the following:
http://www.zeos.dn.ua/eng/zeos_zdo_main.html
Ken
At 13:24 11/01/2000 -0500, Adam Lang wrote:
>So in other words I should have a client that talks to a server application,
>which in turn talks to the database?
>
>Again, this n-tier stuff is nice if the person writing the app has to do it
>independent of a back end, but when you are writing for a specific
>instances, all it seems to do is make things harder...
>
>Adam Lang
>Systems Engineer
>Rutgers Casualty Insurance Company
>----- Original Message -----
>From: "Dave Page" <dpage@vale-housing.co.uk>
>To: "'Adam Lang'" <aalang@rutgersinsurance.com>;
><pgsql-interfaces@postgresql.org>
>Sent: Wednesday, November 01, 2000 12:15 PM
>Subject: RE: [INTERFACES] Connecting remotely.
>
>
>>
>>
>> > -----Original Message-----
>> > From: Adam Lang [mailto:aalang@rutgersinsurance.com]
>> > Sent: 01 November 2000 16:40
>> > To: pgsql-interfaces@postgresql.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@rutgersinsurance.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
>> >
>
^ permalink raw reply [nested|flat] 18+ messages in thread
* RE: Connecting remotely.
@ 2000-11-01 20:14 Clark, Joel <jclark@lendingtree.com>
2000-11-01 20:24 ` Re: Connecting remotely. Adam Lang <aalang@rutgersinsurance.com>
0 siblings, 1 reply; 18+ messages in thread
From: Clark, Joel @ 2000-11-01 20:14 UTC (permalink / raw)
To: 'Adam Lang' <aalang@rutgersinsurance.com>; pgsql-interfaces
One layer of abstraction...
If you use ADO you gain some portability across backends (limited, but still
enough to warrant its investigation). If you code to libpq.dll, then not
only is the SQL PG specific, but the connection libraries as well.
Joel
-----Original Message-----
From: Adam Lang [mailto:aalang@rutgersinsurance.com]
Sent: Wednesday, November 01, 2000 11:40 AM
To: pgsql-interfaces@postgresql.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?
Adam Lang
Systems Engineer
Rutgers Casualty Insurance Company
----- Original Message -----
From: "Sergio A. Kessler" <sak@tribctas.gba.gov.ar>
To: <aalang@rutgersinsurance.com>; <pgsql-interfaces@postgresql.org>
Sent: Wednesday, November 01, 2000 11:18 AM
Subject: Re: [INTERFACES] Connecting remotely.
> "Adam Lang" <aalang@rutgersinsurance.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
^ permalink raw reply [nested|flat] 18+ messages in thread
* Re: Connecting remotely.
2000-11-01 20:14 RE: Connecting remotely. Clark, Joel <jclark@lendingtree.com>
@ 2000-11-01 20:24 ` Adam Lang <aalang@rutgersinsurance.com>
0 siblings, 0 replies; 18+ messages in thread
From: Adam Lang @ 2000-11-01 20:24 UTC (permalink / raw)
To: pgsql-interfaces
That I am aware of. But my point is that if I am not concerned with the
application interfacing on other than postgres, it isn't an issue, correct?
Adam Lang
Systems Engineer
Rutgers Casualty Insurance Company
----- Original Message -----
From: "Clark, Joel" <jclark@lendingtree.com>
To: "'Adam Lang'" <aalang@rutgersinsurance.com>;
<pgsql-interfaces@postgresql.org>
Sent: Wednesday, November 01, 2000 3:14 PM
Subject: RE: [INTERFACES] Connecting remotely.
> One layer of abstraction...
>
> If you use ADO you gain some portability across backends (limited, but
still
> enough to warrant its investigation). If you code to libpq.dll, then not
> only is the SQL PG specific, but the connection libraries as well.
>
> Joel
>
> -----Original Message-----
> From: Adam Lang [mailto:aalang@rutgersinsurance.com]
> Sent: Wednesday, November 01, 2000 11:40 AM
> To: pgsql-interfaces@postgresql.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?
>
> Adam Lang
> Systems Engineer
> Rutgers Casualty Insurance Company
> ----- Original Message -----
> From: "Sergio A. Kessler" <sak@tribctas.gba.gov.ar>
> To: <aalang@rutgersinsurance.com>; <pgsql-interfaces@postgresql.org>
> Sent: Wednesday, November 01, 2000 11:18 AM
> Subject: Re: [INTERFACES] Connecting remotely.
>
>
> > "Adam Lang" <aalang@rutgersinsurance.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
^ permalink raw reply [nested|flat] 18+ messages in thread
* RE: Connecting remotely.
@ 2000-11-01 20:31 Clark, Joel <jclark@lendingtree.com>
2000-11-01 20:52 ` Re: Connecting remotely. Adam Lang <aalang@rutgersinsurance.com>
0 siblings, 1 reply; 18+ messages in thread
From: Clark, Joel @ 2000-11-01 20:31 UTC (permalink / raw)
To: 'Magnus Hagander' <mha@sollentuna.net>; 'Adam Lang' <aalang@rutgersinsurance.com>; pgsql-interfaces
I have created a project on greatbridge's site (www.greatbridge.org) to do
just that (assuming life doesn't get in the way). I have not started yet,
so I can't really give specifics. It will be written C++ (MS Visual C++ 6
to be exact, since that is what I have) using MS's SDK (downloadable from
MSDN).
Joel
-----Original Message-----
From: Magnus Hagander [mailto:mha@sollentuna.net]
Sent: Wednesday, November 01, 2000 12:12 PM
To: 'Adam Lang'; pgsql-interfaces
Subject: RE: [INTERFACES] Connecting remotely.
> As for the ole db... does anyone have an idea where to start
> looking for that info?
http://msdn.microsoft.com/library/default.asp?URL=/library/psdk/dasdk/oled0c
s7.htm
> Would it have to be written in C? I found a
> company that sells
> software that creates ole dbs...
It shuold be possible to write it in any language that can produce COM
objects which support the OLE-DB interfaces (there are lots of them). C++ is
probably the most common langauge used, but there are examples in Java and
Visual Basic as well (samples available at
http://msdn.microsoft.com/library/default.asp?URL=/library/psdk/dasdk/osp298
xb.htm).
//Magnus
^ permalink raw reply [nested|flat] 18+ messages in thread
* Re: Connecting remotely.
2000-11-01 20:31 RE: Connecting remotely. Clark, Joel <jclark@lendingtree.com>
@ 2000-11-01 20:52 ` Adam Lang <aalang@rutgersinsurance.com>
0 siblings, 0 replies; 18+ messages in thread
From: Adam Lang @ 2000-11-01 20:52 UTC (permalink / raw)
To: pgsql-interfaces
So you are writing an OLE DB provider? I'm going to have to set up an altar
to you at my house... ;)
I know it may be a stupid question, but are they overly hard? I mean, if
you have a lot of connectivity code already existent in the ODBC and libpq,
does it make the job a lot easier?
Adam Lang
Systems Engineer
Rutgers Casualty Insurance Company
----- Original Message -----
From: "Clark, Joel" <jclark@lendingtree.com>
To: "'Magnus Hagander'" <mha@sollentuna.net>; "'Adam Lang'"
<aalang@rutgersinsurance.com>; "pgsql-interfaces"
<pgsql-interfaces@postgresql.org>
Sent: Wednesday, November 01, 2000 3:31 PM
Subject: RE: [INTERFACES] Connecting remotely.
> I have created a project on greatbridge's site (www.greatbridge.org) to do
> just that (assuming life doesn't get in the way). I have not started yet,
> so I can't really give specifics. It will be written C++ (MS Visual C++ 6
> to be exact, since that is what I have) using MS's SDK (downloadable from
> MSDN).
>
> Joel
>
> -----Original Message-----
> From: Magnus Hagander [mailto:mha@sollentuna.net]
> Sent: Wednesday, November 01, 2000 12:12 PM
> To: 'Adam Lang'; pgsql-interfaces
> Subject: RE: [INTERFACES] Connecting remotely.
>
>
> > As for the ole db... does anyone have an idea where to start
> > looking for that info?
>
http://msdn.microsoft.com/library/default.asp?URL=/library/psdk/dasdk/oled0c
> s7.htm
>
> > Would it have to be written in C? I found a
> > company that sells
> > software that creates ole dbs...
> It shuold be possible to write it in any language that can produce COM
> objects which support the OLE-DB interfaces (there are lots of them). C++
is
> probably the most common langauge used, but there are examples in Java and
> Visual Basic as well (samples available at
>
http://msdn.microsoft.com/library/default.asp?URL=/library/psdk/dasdk/osp298
> xb.htm).
>
> //Magnus
^ permalink raw reply [nested|flat] 18+ messages in thread
* RE: Connecting remotely.
@ 2000-11-01 21:41 Clark, Joel <jclark@lendingtree.com>
0 siblings, 0 replies; 18+ messages in thread
From: Clark, Joel @ 2000-11-01 21:41 UTC (permalink / raw)
To: 'Adam Lang' <aalang@rutgersinsurance.com>; pgsql-interfaces
After consulting MSDN, I am pretty sure that I will be able to wrap the
provider around libpq. If not, I won't be completing the provider. *g*
The only task I have listed for my project so far is building a
strategy...included in this is a feasability check.
No need for altars, but testers/documenters might come in handy if I ever
get something up and running. :)
Joel
-----Original Message-----
From: Adam Lang [mailto:aalang@rutgersinsurance.com]
Sent: Wednesday, November 01, 2000 3:52 PM
To: pgsql-interfaces
Subject: Re: [INTERFACES] Connecting remotely.
So you are writing an OLE DB provider? I'm going to have to set up an altar
to you at my house... ;)
I know it may be a stupid question, but are they overly hard? I mean, if
you have a lot of connectivity code already existent in the ODBC and libpq,
does it make the job a lot easier?
Adam Lang
Systems Engineer
Rutgers Casualty Insurance Company
----- Original Message -----
From: "Clark, Joel" <jclark@lendingtree.com>
To: "'Magnus Hagander'" <mha@sollentuna.net>; "'Adam Lang'"
<aalang@rutgersinsurance.com>; "pgsql-interfaces"
<pgsql-interfaces@postgresql.org>
Sent: Wednesday, November 01, 2000 3:31 PM
Subject: RE: [INTERFACES] Connecting remotely.
> I have created a project on greatbridge's site (www.greatbridge.org) to do
> just that (assuming life doesn't get in the way). I have not started yet,
> so I can't really give specifics. It will be written C++ (MS Visual C++ 6
> to be exact, since that is what I have) using MS's SDK (downloadable from
> MSDN).
>
> Joel
>
> -----Original Message-----
> From: Magnus Hagander [mailto:mha@sollentuna.net]
> Sent: Wednesday, November 01, 2000 12:12 PM
> To: 'Adam Lang'; pgsql-interfaces
> Subject: RE: [INTERFACES] Connecting remotely.
>
>
> > As for the ole db... does anyone have an idea where to start
> > looking for that info?
>
http://msdn.microsoft.com/library/default.asp?URL=/library/psdk/dasdk/oled0c
> s7.htm
>
> > Would it have to be written in C? I found a
> > company that sells
> > software that creates ole dbs...
> It shuold be possible to write it in any language that can produce COM
> objects which support the OLE-DB interfaces (there are lots of them). C++
is
> probably the most common langauge used, but there are examples in Java and
> Visual Basic as well (samples available at
>
http://msdn.microsoft.com/library/default.asp?URL=/library/psdk/dasdk/osp298
> xb.htm).
>
> //Magnus
^ permalink raw reply [nested|flat] 18+ messages in thread
end of thread, other threads:[~2000-11-01 21:41 UTC | newest]
Thread overview: 18+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2000-11-01 14:29 Connecting remotely. Adam Lang <aalang@rutgersinsurance.com>
2000-11-01 14:50 ` Marko Kreen <marko@l-t.ee>
2000-11-01 14:52 ` Adam Lang <aalang@rutgersinsurance.com>
2000-11-01 16:18 ` Sergio A. Kessler <sak@tribctas.gba.gov.ar>
2000-11-01 16:40 ` Adam Lang <aalang@rutgersinsurance.com>
2000-11-01 15:32 RE: Connecting remotely. Dave Page <dpage@vale-housing.co.uk>
2000-11-01 16:36 ` Adam Lang <aalang@rutgersinsurance.com>
2000-11-01 15:35 RE: Connecting remotely. Clark, Joel <jclark@lendingtree.com>
2000-11-01 16:36 ` Adam Lang <aalang@rutgersinsurance.com>
2000-11-01 17:11 RE: Connecting remotely. Magnus Hagander <mha@sollentuna.net>
2000-11-01 17:15 RE: Connecting remotely. Dave Page <dpage@vale-housing.co.uk>
2000-11-01 18:24 ` Adam Lang <aalang@rutgersinsurance.com>
2000-11-01 18:55 ` ken@ori-ind.com
2000-11-01 20:14 RE: Connecting remotely. Clark, Joel <jclark@lendingtree.com>
2000-11-01 20:24 ` Adam Lang <aalang@rutgersinsurance.com>
2000-11-01 20:31 RE: Connecting remotely. Clark, Joel <jclark@lendingtree.com>
2000-11-01 20:52 ` Adam Lang <aalang@rutgersinsurance.com>
2000-11-01 21:41 RE: Connecting remotely. Clark, Joel <jclark@lendingtree.com>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox