[ psqlodbc-Bugs-1000522 ] Enabling logging breaks ODBC for non administrators - Mailing list pgsql-odbc

From
Subject [ psqlodbc-Bugs-1000522 ] Enabling logging breaks ODBC for non administrators
Date
Msg-id 20060107175203.DF5231033E17@pgfoundry.org
Whole thread Raw
List 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

Category: None
Group: None
Status: Open
Resolution: None
Priority: 3
Submitted By: Magnus Hagander  (mha)
Assigned to: Nobody (None)
Summary: Enabling logging breaks ODBC for non administrators

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),
notto c:\. This is true even if my assumption that this permissions issue is what causes the problem specified. 

----------------------------------------------------------------------

You can respond by visiting:
http://pgfoundry.org/tracker/?func=detail&atid=538&aid=1000522&group_id=1000125

pgsql-odbc by date:

Previous
From:
Date:
Subject: [ psqlodbc-Bugs-1000519 ] Does not pick up default username
Next
From: Dave Page
Date:
Subject: Re: VBA 6 crashes with WIN2K, Postgres 8.1, why ?