pg.ddx.io  pgsql-interfaces@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Byron Nikolaidis <byronn@insightdist.com>
To: pgsql-interfaces@postgreSQL.org <pgsql-interfaces@postgreSQL.org>
Subject: [Fwd: errors in psqlodbc]
Date: Mon, 19 Oct 1998 11:26:31 -0400
Message-ID: <362B5A27.F620F64B@insightdist.com> (raw)


     I'm not sure you are the person to recieve these.  If not, could you 
     pass them along.
     
     These problems were found when installing postodbc on sun solaris 
     2.5.1.  It could be that some of these would not be errors on some 
     other OS.
     
     connection.c.  A seg fault occurs when writing to one of the log 
     files.  The problem is a null pointer.
     
     misc.c.  If log files are written by one user, then the next user 
     cannot reopen or replace the files since they are owned by the first.  
     There the fopen returns a null pointer and causes a segmentation 
     error.
     
     gpps.c.  There were several errors in the implementation of 
     GetPrivateProfileString and WritePrivateProfileString.  The principle 
     problem was that iodbc and psqlodbc ended up pointing to different ini 
     files.  I used this code in another application and implemented all 
     the features of the Window's APIs.  
     
     I think the code to read the ini files should be in iodbc not each 
     client.  I have received three different iodbc's from postgres, mysql, 
     and openlink distributions.  All three slightly different.  And most 
     of the differences are in the handling of ini files.
     
     I am sending my implementation of GetPrivateProfileString and 
     WriteProfileString in files: profile.h, profile.c, and a test 
     application testpro.c.
     
     One problem with the distribution of psqlodbc is that the linker 
     switch -B symbolic causes 4 linker errors to be listed.  I did not 
     know this was really OK, that the linker errors would be resolved by 
     the dynamic loading.  Therefore, I wasted a lot of time trying to 
     solve this problem that wasn't really a problem.  Perhaps, there 
     should be some warning in the install documentation to expect these 
     linker errors.
     
     John Sharp
     jsharp@cfipro.com
     sharp@cs.pdx.edu

Attachments:

  testpro.c (application/octet-stream, 2.6K) download

  profile.c (application/octet-stream, 14.1K) download

  profile.h (application/octet-stream, 1.1K) download

  misc.dif (application/octet-stream, 2.1K) download

  conntion.dif (application/octet-stream, 1.6K) download

view thread (4+ messages)  latest in thread

Message-ID: <362B5A27.F620F64B@insightdist.com>
Permalink:  ../362B5A27.F620F64B@insightdist.com/
Also on:    postgresql.org/message-id/362B5A27.F620F64B@insightdist.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-interfaces@postgresql.org
  Cc: byronn@insightdist.com
  Subject: Re: [Fwd: errors in psqlodbc]
  In-Reply-To: <362B5A27.F620F64B@insightdist.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

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