patch for [ psqlodbc-Bugs-1000522 ] Enabling logging breaks ODBC for non administrators

From: Ludek Finstrle <luf(at)pzkagis(dot)cz>
To: pgsql-odbc(at)postgresql(dot)org
Subject: patch for [ psqlodbc-Bugs-1000522 ] Enabling logging breaks ODBC for non administrators
Date: 2006-01-10 22:19:33
Message-ID: 20060110221933.GA8448@soptik.pzkagis.cz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-odbc

> Bugs item #1000522, was opened at 2006-01-07 18:52
> You can respond by visiting:
> http://pgfoundry.org/tracker/?func=detail&atid=538&aid=1000522&group_id=1000125
> Initial Comment:
> Steps to reproduce (tested on windows 2003)
>
> 1. Create a user DSN logged in as a non-admin user
> 2. Create another user DSN logged in as admin user. As this user, enable logging ("mylog")
> 3. Try to configure the DSN logged in as a non admin user. The ODBC driver crashes with error 998.
>
> This is probably because it can't write to the logfile? Which brings up two points:
>
> 1) There should be error checking for that :-) If that's exactly what it is.
>
> 2) The logfiles are completely usless for non-administrative users, since they are hardcoded to c:\. This should be configurable, or if it's hardcode dit should at least be hardcoded to the temp directory (as set in the environment), not to c:\. This is true even if my assumption that this permissions issue is what causes the problem specified.
>
> ----------------------------------------------------------------------

Here is the patch for mail archive. It use the easiest way. It isn't
possible for user without write permission to C:\ to enable logs.
I think we need time for developing new version more then better solution
for this.

Please review and comment

Luf

Attachment Content-Type Size
psqlodbc-log_check.diff text/plain 1.4 KB

Browse pgsql-odbc by date

  From Date Subject
Next Message Ludek Finstrle 2006-01-11 08:32:56 Re: PsqlODBC slow on UNION queries
Previous Message noreply 2006-01-10 22:12:49 [ psqlodbc-Bugs-1000510 ] Access the rdoResultsets column is NULL in the second access