From: Tony Simopoulos <karkalis@earthling.net>
To: pgsql-interfaces@postgresql.org
Subject: Re: ReadOnly
Date: Wed, 10 Jan 2001 14:19:08 -0500
Message-ID: <070001c07b3a$34e582f0$0382a8c0@metavera.com> (raw)
References: <063601c07a55$83e7a8a0$0382a8c0@metavera.com>
well, after no help, i managed to fix my own problem.
i am extremely bitter about this whole experience, i have half a mind not to share my solution.
the long and short of the problem, is that my odbc.ini file contained a tab character as white space, after the ReadOnly key, just
before the '=' sign.
i only found this problem looking through the code, trying to figure out why the ReadOnly key was consistently being missed.
i would classify this as a BUG, and i'm highly surprised that nobody else has come across it. should this behaviour be intentional,
why is it not documented in the manual??
i did some more checking and found an email posting from september 1999, where someone provided a HACK to use libiodbc's version of
SQLGetPrivateProfile functions, claiming that postgresql's native version was 'buggy' particularly wrt to tabs. some follow up
postings did not include a plan to merge these efforts with the source tree, nor to correct the apparent *bugs*.
in short the code that implements SQLGetPrivateProfile in the odbc driver code provided with the postgresql package is terrible. i
checked both mysql and libiodbc implementations of the same set of functions .. the code was far cleaner. also, that code treated
tabs following the key name as whitespace as should be expected.
1 1/2 years later, i hope these bugs finally get fixed, or the *special* behaviour finally documented.
thanks,
tonys.
> my problem persists .. anybody?!?!?!?!?!?
>
> > ok,
> >
> > i have finally broken down and decided to ask for some help. i have looked for relevant sections in the manual, scanned previous
> > posts, and searched the entire web for help .. all to no avail.
> >
> > i CANNOT get non-readonly access to pgsql through iODBC on my FreeBSD box. (from my windows box, this is not a challenge).
when
> i
> > try an update from odbctest i get the following:
> > [SQLPrepare] Connection is readonly, only select statements are allowed.
> >
> > i have tried almost every permutation i can think of .. here is my current state.
> >
> > /usr/local/pgsql/odbcinst.ini
> > [PostgreSQL]
> > ReadOnly = 0
> > Debug = 0
> > CommLog = 1
> >
> > /usr/local/etc/odbcinst.ini is identical to this file
> > /etc/odbcinst.ini is identical to this file
> >
> > /usr/local/etc/odbc.ini
> > [ODBC Data Sources]
> > loathe = PostgreSQL
> > cars = PostgreSQL
> > foo = MySQL
> >
> > [Default]
> > Driver = /usr/local/pgsql/lib/libpsqlodbc.so
> > ReadOnly = 0
> >
> > [loathe]
> > DSN = loathe
> > ReadOnly = 0
> > Driver = /usr/local/pgsql/lib/libpsqlodbc.so
> > Description = PGSQL-ODBC
> > Database = metav
> > Servername = localhost
> > Port = 5432
> >
> > $HOME/.odbc.ini is identical to this
> >
> > Most of my resouce problems have to do with contradictions in the descriptions of behaviour of the odbc.ini and odbcinst.ini
> files.
> > there is no clarity that i can find w.r.t. where they should go, when they are accessed, what drivers utilize them (pgsql or
iodbc
> > or both??), and what exactly should be in them.
> >
> > someone please help me, before i pull the rest of hair out.
> >
> > thanks,
> >
> > tonys.
> >
> >
>
>
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: karkalis@earthling.net
Subject: Re: ReadOnly
In-Reply-To: <070001c07b3a$34e582f0$0382a8c0@metavera.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