Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1qGdOq-000824-KJ for pgsql-odbc@arkaria.postgresql.org; Tue, 04 Jul 2023 10:36:48 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1qGdOo-0002p4-NC for pgsql-odbc@arkaria.postgresql.org; Tue, 04 Jul 2023 10:36:46 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1qGc2a-0007p2-Ka for pgsql-odbc@lists.postgresql.org; Tue, 04 Jul 2023 09:09:44 +0000 Received: from mail-lj1-x233.google.com ([2a00:1450:4864:20::233]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1qGc2U-0027Ih-0Y for pgsql-odbc@postgresql.org; Tue, 04 Jul 2023 09:09:44 +0000 Received: by mail-lj1-x233.google.com with SMTP id 38308e7fff4ca-2b69dcf45faso86788261fa.0 for ; Tue, 04 Jul 2023 02:09:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1688461775; x=1691053775; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=6QSnQmU6Asyo2ayFTV71HoBLXhJrbNbsVZHXAAR7Juo=; b=d3V7cPQH2+D0Hd0fTCK2hfXM884o/NO2z7njIHsAawr+5xARLwHmbmYhPpHN3VYpGO em7gvf2zsDcE/IyHFFCuINIbFPf9iSfTr4Of3WK/aqfqteHkobbLagZq2sJYY9K8X3+0 OLoMbXQk+8HubQpWjeD0XmBJW2Yjrqx3boXC92hux9g9rz3qWCrX6TNa1JJYpfFff0R4 WH/KFCoTTqa/wp2i43iIlHi4c91IKB2rDcyj0lq4fWBgshByMhcPlc73nqWHLKNdVo5q y8Z3FSQIp3Ft+Odq/FGuwz6oWE752VHCtgYbNwCGrFXVEWlNX9ZW3ToNIN0TTWEOvplZ m8dw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1688461775; x=1691053775; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=6QSnQmU6Asyo2ayFTV71HoBLXhJrbNbsVZHXAAR7Juo=; b=ltrOwjgAF17Sx4rLM4fQo5dgW1QnV/E8Bsr52uk1KyaQDRA0IJp+HFz87ORJzsk1YL PgwzH1rutWhvBSNLVyxXlOuxZThgyihTDY+VUTXUIdP3dI0peFcTMbb5FjvAYuQA8HgX g/bqaiFWEcXvFJ2aL++C0MWcz6aeGl3ejYKcXox5PBb7tM7EP0UXzwSdt39jMfnxVyOt IByars6f0RbkS/wF2+gJvOmAcpyUohTcs2hcqxV6fbOBuX0FJqcvTqzGMask6c4XBjqu qO+Gli7TnTA0qd2ayYZmKWeE1NUb0GmF0qcsGsQJrkueHpzqjv+EJ8isbscPKlBBZwRQ G0uw== X-Gm-Message-State: ABy/qLaTyetYCfi3gJGStytCSv7vJK3o883GMUKTd3XQlkJr5evBcDNF vuI/kZp7BpENEV87i5Dp6zuaNos1iX9ahns5QaxfGyzTmcg= X-Google-Smtp-Source: APBJJlGsvnhK2d+9o/uKyJPIVLXIAfb1Or3Xio78wqqV9FHjIVLpjfkHOSOmMJ/KF3CdpfEquwwyPtLhKoFLH4bhmcA= X-Received: by 2002:a2e:9947:0:b0:2b6:efa0:7c36 with SMTP id r7-20020a2e9947000000b002b6efa07c36mr2331053ljj.21.1688461775086; Tue, 04 Jul 2023 02:09:35 -0700 (PDT) MIME-Version: 1.0 From: Karl Aschbacher Date: Tue, 4 Jul 2023 11:09:24 +0200 Message-ID: Subject: Change the name of a function in the odbc-driver To: pgsql-odbc@postgresql.org Content-Type: multipart/alternative; boundary="00000000000052274e05ffa5a43e" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --00000000000052274e05ffa5a43e Content-Type: text/plain; charset="UTF-8" Dear all, we are using the Oracle Analytics Server to connect to a PostgreSql Database. While this is generally working, the OAS sends some wrong function names. (for example grouping_id instead of grouping). We tried creating an "alias function", named grouping_id that would simply call grouping, but we failed as the number (and type) of arguments is just not predictable. I then came up with the idea to change the method name in the ODBC Driver, like for some scalar functions. So far I have added another mapping in convert.c, recompiled the driver, but (of course ?) this is not working yet. " {"GROUPING_ID", "grouping" }," So my questions are: Is this an approach that is worth following? (Knowing Oracle support, a fix might be taking quite some time) If yes, is there any advice you could give what else need to be changed? If no - any other idea how to address this issue? Any help or ideas will be very much appreciated. many thanks best regards Karl --00000000000052274e05ffa5a43e Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Dear all,

we are using the Oracle Analy= tics Server to connect to a PostgreSql Database.
While this is ge= nerally working, the OAS sends some wrong function names.
(for ex= ample grouping_id instead of grouping).
We tried creating an &quo= t;alias function", named grouping_id that would simply call grouping, = but we failed as the number (and type) of arguments is just not predictable= .

I then came up with the idea to change the metho= d name in the ODBC Driver, like for some scalar functions. So far I have ad= ded another mapping in convert.c, recompiled the driver, but (of course ?) = this is not working yet.

"=C2=A0{"GROUPI= NG_ID", =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0"grouping" =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 },"

So my questions are:
Is this an approach that is worth following= ?
(Knowing Oracle support, a fix might be taking quite some time)=
If yes, is there any advice you could give what else need to be = changed?

If no - any other idea how to address= this issue?
Any help or ideas will be very much appreciated.

many thanks
best regards
Karl









--00000000000052274e05ffa5a43e--