agora inbox for postgres@postgres.berkeley.edu  
help / color / mirror / Atom feed
Postgres and ODBC
4+ messages / 4 participants
[nested] [flat]

* Postgres and ODBC
@ 1995-10-25 16:15 John Landheer <JOHN@hoc.nl>
  1995-10-25 22:17 ` Interfacing postgres with WWW Alex Shum <shum@cs.und.nodak.edu>
  0 siblings, 1 reply; 4+ messages in thread

From: John Landheer @ 1995-10-25 16:15 UTC (permalink / raw)
  To: legacy

Is there a way to use postgres through an ODBC-driver.
I'm using Windows 3.11.

Thanks in advance

John Landheer
john@hoc.nl

==============================================================================
   To add/remove yourself to/from the POSTGRES mailing list: send mail with 
   the subject line ADD or DEL to "postgres-request@postgres.Berkeley.EDU".
   If this fails, send mail to "post_questions@postgres.Berkeley.EDU" and
   a human will deal with it.  DO NOT post to the "postgres" mailing list.
==============================================================================
              URL: http://s2k-ftp.CS.Berkeley.EDU:8000/postgres/



^ permalink  raw  reply  [nested|flat] 4+ messages in thread

* Interfacing postgres with WWW
  1995-10-25 16:15 Postgres and ODBC John Landheer <JOHN@hoc.nl>
@ 1995-10-25 22:17 ` Alex Shum <shum@cs.und.nodak.edu>
  1995-10-26 03:13   ` Re: Interfacing postgres with WWW Chris Phillips <phillipc@limestone.kosone.com>
  0 siblings, 1 reply; 4+ messages in thread

From: Alex Shum @ 1995-10-25 22:17 UTC (permalink / raw)
  To: legacy

Hi,

Just curious if anyone has successfully written a CGI program interfacing
postgres with the web. I tried both pgtclsh and libpq and both of them 
result in a server error while trying to connect to the backend. Also,
please let me know if you are able to  compile pgperl5 and have it work
with WDB. Any help in this area will be very appreciated. 

Thanks. 


Alex Shum                              | E-mail: shum@cs.und.nodak.edu    
Department of Computer Science         | H:(701)-777-7122 
University of North Dakota, Box 9015   | W:(701)-777-3637
Grand Forks, ND 58202-9015             |   (701)-777-2484


==============================================================================
   To add/remove yourself to/from the POSTGRES mailing list: send mail with 
   the subject line ADD or DEL to "postgres-request@postgres.Berkeley.EDU".
   If this fails, send mail to "post_questions@postgres.Berkeley.EDU" and
   a human will deal with it.  DO NOT post to the "postgres" mailing list.
==============================================================================
              URL: http://s2k-ftp.CS.Berkeley.EDU:8000/postgres/



^ permalink  raw  reply  [nested|flat] 4+ messages in thread

* Re: Interfacing postgres with WWW
  1995-10-25 16:15 Postgres and ODBC John Landheer <JOHN@hoc.nl>
  1995-10-25 22:17 ` Interfacing postgres with WWW Alex Shum <shum@cs.und.nodak.edu>
@ 1995-10-26 03:13   ` Chris Phillips <phillipc@limestone.kosone.com>
  1995-10-26 09:07     ` Re: Interfacing postgres with WWW Justin Ziegler <Justin.Ziegler@edelweb.fr>
  0 siblings, 1 reply; 4+ messages in thread

From: Chris Phillips @ 1995-10-26 03:13 UTC (permalink / raw)
  To: Alex Shum <shum@cs.und.nodak.edu>; +Cc: legacy

On Wed, 25 Oct 1995, Alex Shum wrote:

> Hi,
> 
> Just curious if anyone has successfully written a CGI program interfacing
> postgres with the web. I tried both pgtclsh and libpq and both of them 
> result in a server error while trying to connect to the backend. Also,
> please let me know if you are able to  compile pgperl5 and have it work
> with WDB. Any help in this area will be very appreciated. 
> 


I've succeeded with much heartache...

The pgperl stuff just didn't compile correctly (the .mus files were the 
problem) and other C things just didn't do it either.

What I ended up doing was manually compiling one of the libraries, so 
that the overall compile went ahead properly, and I installed (with even 
more heartache, g++), to compile c++ code that came with the source tree 
of postgresv4.2 (proper ver?).

In any case, I have a proper backend connection from the web, but am 
evaluating other servers that are available... IMHO, postgres is a 
powerful engine, but I can whack the heck out of it.  I am looking at 
postgres95 as a possible migration, but feel that it may not be fast 
enough for me ...anyone with experience with postrges95 and the web? 
 
Chris...

 
______________________________________________________________________
Chris Phillips			CanLink Interactive Services
B. Sc. Computing		V:+1(613)549-7883

phillipc@canlink.kosone.com	Your professionals in Internet and 
				related Interactive technology.


==============================================================================
   To add/remove yourself to/from the POSTGRES mailing list: send mail with 
   the subject line ADD or DEL to "postgres-request@postgres.Berkeley.EDU".
   If this fails, send mail to "post_questions@postgres.Berkeley.EDU" and
   a human will deal with it.  DO NOT post to the "postgres" mailing list.
==============================================================================
              URL: http://s2k-ftp.CS.Berkeley.EDU:8000/postgres/



^ permalink  raw  reply  [nested|flat] 4+ messages in thread

* Re: Interfacing postgres with WWW
  1995-10-25 16:15 Postgres and ODBC John Landheer <JOHN@hoc.nl>
  1995-10-25 22:17 ` Interfacing postgres with WWW Alex Shum <shum@cs.und.nodak.edu>
  1995-10-26 03:13   ` Re: Interfacing postgres with WWW Chris Phillips <phillipc@limestone.kosone.com>
@ 1995-10-26 09:07     ` Justin Ziegler <Justin.Ziegler@edelweb.fr>
  0 siblings, 0 replies; 4+ messages in thread

From: Justin Ziegler @ 1995-10-26 09:07 UTC (permalink / raw)
  To: Chris Phillips <phillipc@limestone.kosone.com>; +Cc: Alex Shum <shum@cs.und.nodak.edu>; legacy


Hi,

We have managed to interface Postgres95 with a perl5 frontend launch
by a web server. We used the three put together to create a prototype
payement system. All our e-wallets are stored in pg95, and all
commercial transactions also.

Obviously at the beginning we had a few problems to get every thing
compiled, but it is possible if your a bit used to that sort of thing.
Especially at the time, we did not have enough disk space, and could
not install gcc so we used acc on sunos 4.1.3.
Also at the beginning pg95 gave us a few cores here and there, but we
discuvered that only happens when we do things it doesn't like.

Right now, we've had it going for over a month without any problem at
all !!! One regret: to my mind, the db seems to grow quite fast.

In doing our system, we gave ourselves a challenge: only use real SQL
92 requests as long as possible. Thus we did not use the inherits that
pg95 supports. Instead we designed a language to describe our db and
produce loads of perl5 code to interface with the backend. From then
on the whole thing became quite trivial:

require quite,q,few,files,here ;

dbms::openConnection() ;

my $thePerson= new person ;
$thePerson->{attribs}->{name}="someName" ;
$thePerson->store() ;

dbms::closeConnection() ;

And there ! youve got it in the db.

The language (SDL) when interpreted or compiled also produces some
code to initialise and reconstruct the db. I actual fact the language
is now some sort of OMT schema description language.

While experimenting many commercial transactions ot once, we found
that pg95's locking did behave the way we wanted... So I launched it
under debugging mode and found a few of the functions concerned with
looking. I transformed all the read locks into write locks. I know
this is not a very nice hack, but man it works cool ;-) and we had
gone to far to discuver that pg95 was not able to do what we wanted.

The final result works well ! but it is not very nervous ...
If I had time I would try and modify the main function of the db in
order to pre-fork it a little like it is done in the Apache, netsite,
NCSA1.4 Web servers. I reckon this could gain a bit of time on each
simple request. When attacking a db from the Web, you must keep in
mind that for every request you are going to have to open and close
the connection to the backend, and that is quite expensive (~1second
with pg95).

We also found that pg95 was a littl slow on joins. So whenever it was
possible, we avoided them like hell e.i. we made big tables with empty
collums instead of two or three tables. (this concerns our home made
inherits).

All in all pg95 is great for what it costs.

Justin.

PS: We did all this on Version Beta 0.02.

==============================================================================
   To add/remove yourself to/from the POSTGRES mailing list: send mail with 
   the subject line ADD or DEL to "postgres-request@postgres.Berkeley.EDU".
   If this fails, send mail to "post_questions@postgres.Berkeley.EDU" and
   a human will deal with it.  DO NOT post to the "postgres" mailing list.
==============================================================================
              URL: http://s2k-ftp.CS.Berkeley.EDU:8000/postgres/



^ permalink  raw  reply  [nested|flat] 4+ messages in thread


end of thread, other threads:[~1995-10-26 09:07 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
1995-10-25 16:15 Postgres and ODBC John Landheer <JOHN@hoc.nl>
1995-10-25 22:17 ` Interfacing postgres with WWW Alex Shum <shum@cs.und.nodak.edu>
1995-10-26 03:13   ` Re: Interfacing postgres with WWW Chris Phillips <phillipc@limestone.kosone.com>
1995-10-26 09:07     ` Re: Interfacing postgres with WWW Justin Ziegler <Justin.Ziegler@edelweb.fr>

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox