Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qnnJ3-00C2R5-0L for pgsql-odbc@arkaria.postgresql.org; Tue, 03 Oct 2023 21:51:53 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1qnnJ1-0097ie-FG for pgsql-odbc@arkaria.postgresql.org; Tue, 03 Oct 2023 21:51:51 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qnnJ1-0097i6-7c for pgsql-odbc@lists.postgresql.org; Tue, 03 Oct 2023 21:51:51 +0000 Received: from mail-yw1-x112d.google.com ([2607:f8b0:4864:20::112d]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1qnnIz-008vJp-1J for pgsql-odbc@lists.postgresql.org; Tue, 03 Oct 2023 21:51:50 +0000 Received: by mail-yw1-x112d.google.com with SMTP id 00721157ae682-5a1ec43870cso17850887b3.0 for ; Tue, 03 Oct 2023 14:51:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1696369906; x=1696974706; darn=lists.postgresql.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=BUBXbQI3t/eS5OXvkrtzshDStoDBNusLnoeqzgHl0vg=; b=MjaL9xII9zShZHFf/PVmw4gARj7Nvdaqwms4wZ7i1mhq69rpE9eRC8BV3ONYooHRll au8CUZgUoGmUEj5uw2G+JkAnm7cx9UpKjVEIT+OmfQuty8e7D/TjI7VMiNqGklry4lUM Q0sqN+NNl86rT6UazUQtfIE/LgluCshWgLgo+AD2SuFAYQljpA3peQ5FKbNJ6u3nbKEy bsqwkAOjU9rKCkQnjnecNvkzmwQm/Bicq6kyw3KADusZrRp2+9Re2gdd8B4guYcf/5xF ewMHHxzXsoKlPUUvXYe8THI59nwY9PzP9gDs/t93q1zFxH4lm6yIUQST0fTYuxZrR/P6 g/eA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1696369906; x=1696974706; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=BUBXbQI3t/eS5OXvkrtzshDStoDBNusLnoeqzgHl0vg=; b=e9Qalj4jWtqzdBDWBVmst8sGSykGwOEwePhhjjenOL0SIo7S5VFGdtkVvClJKz0LRH 0rl3AnUiUT6eZ9mrN4lx8pG8L4AE30sjfpv809Vb6P5Ckg+87luc86J6qPd+fB5eVx3A CqF70IuQH/q8I+GmFwtRBHJ16xATPAs1Sj1hldPPjKFX06Mu7HWWyQAE9cNZodLcEjnl SNh5A9OvT1+35kQH/7ClUI/dDjdqWFMAqYpLhrWsNuu5O9lboFdO075BURUS/K2hTdMv 0Sc7HDSuH4tGAbY4dcZg4wustBf5bfru86+J7DyY+XhhEUdb5ctZtDe4ku2b3oD9fgH3 YaWA== X-Gm-Message-State: AOJu0YxHHAbBIx7bgRzCjwBbOSapzn5ot+wEC6SVK3Ml85tTtm1fEOUt 0tEcZae7vBuXXj+ps3ElzUFtDlC+4FVp3y1rv+e7z/R8HJA= X-Google-Smtp-Source: AGHT+IFNHM2bpapiacJt9WRUwWRSG46CEWRXQH+MepUzBlEXOoxLOuZB8J8ghiaGbWeAxrm+Ld2R8lEhoZfpaemfNKs= X-Received: by 2002:a81:ab42:0:b0:5a1:e4bf:ee5a with SMTP id d2-20020a81ab42000000b005a1e4bfee5amr697595ywk.41.1696369906242; Tue, 03 Oct 2023 14:51:46 -0700 (PDT) MIME-Version: 1.0 From: Brad White Date: Tue, 3 Oct 2023 16:51:34 -0500 Message-ID: Subject: ODBC options To: pgsql-odbc@lists.postgresql.org Content-Type: multipart/alternative; boundary="000000000000ab5b190606d6e57a" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000ab5b190606d6e57a Content-Type: text/plain; charset="UTF-8" I was trying to figure how to set the log directory using a parameter in the connection string. Short answer is that you can't. But you can using the DSN settings. I was under the impression that going DSN-less and using the parameters on the connection string, we were free from the effects of the DSN settings. That's not true. The DSN settings become the default values, overridden by anything in the connection string. So you can set default values in the DSN dialog, or you can set them in the registry. ----- ODBCLoggingOn.reg ------ [HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\ODBC\ODBCINST.INI\PostgreSQL Unicode] "Debug"="1" "Logdir"="c:\\temp" ------------------------------------------ In the process I documented all the settings and their abbreviations in a spreadsheet. I'll post that to the docs mailing list. --000000000000ab5b190606d6e57a Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
I was trying to figure how to set the log directory using = a parameter in the connection string. Short answer is that you can't.
But you can using the DSN settings.
I was under the impres= sion that going DSN-less and using the parameters=C2=A0on the connection st= ring, we were free from the effects of the DSN settings.
That'= ;s not true.
The DSN settings become the default values, overridd= en by anything in the connection string.
So you can set default v= alues in the DSN dialog, or you can set them in the registry.
-----=C2=A0=C2=A0ODBCLoggingOn.reg ------
[HKEY_LOCAL= _MACHINE\SOFTWARE\WOW6432Node\ODBC\ODBCINST.INI\PostgreSQL Unicode]

= "Debug"=3D"1"
"Logdir"=3D"c:\\temp&qu= ot;
------------------------------------------

=
In the process I documented all the settings and their abbreviat= ions=C2=A0in a spreadsheet.=C2=A0 I'll post that to the docs mailing li= st.

--000000000000ab5b190606d6e57a--