Обсуждение: fn TIMESTAMPADD

Поиск
Список
Период
Сортировка

fn TIMESTAMPADD

От
Matthias Coene
Дата:

Hi,

 

I am using Postgres for my data warehouse. I am using Oracle BI as my reporting tool, using the Postgres ODBC driver to connect.
I seem to have a problem with the TIMESTAMPADD function:

 

]]

[2020-03-12T15:32:53.182+01:00] [OBIS] [TRACE:2] [] [] [ecid: ] [sik: ssi] [tid: 27dc] [messageid: USER-18] [requestid: 66350030] [sessionid: 66350000] [username: weblogic] -------------------- Sending query to database named IDEWE_DWH (id: <<430532>>), connection pool named Connection_Pool, logical request hash 4bcf4b69, physical request hash 496312e3: [[

WITH

SAWITH0 AS (select distinct T54148.GEBOREN as c1,

     {fn TimestampAdd(SQL_TSI_YEAR, 18, T54148.GEBOREN)} as c2

from

     DIM_WERKNEMERS T54148)

select 0 as c1,

     D1.c1 as c2,

     D1.c2 as c3

from

     SAWITH0 D1

order by 2

 

]]

[2020-03-12T15:32:53.188+01:00] [OBIS] [TRACE:2] [] [] [ecid: ] [sik: ssi] [tid: 27dc] [messageid: USER-34] [requestid: 66350030] [sessionid: 66350000] [username: weblogic] -------------------- Query Status: [nQSError: 16002] Cannot obtain number of columns for the query result. [[

[nQSError: 16001] ODBC error state: 42703 code: 1 message: ERROR: column "sql_tsi_year" does not exist;

No query has been executed with that handle.

[nQSError: 43119] Query Failed:

 

]]

 

 

Can you please check if this is a problem in Oracle BI ODBC interface, or the driver itself?

 

Kind regards,

Matthias

Matthias Coene
ICT business intelligence engineer
+32 16 39 04 98
Matthias.Coene@idewe.be
Groep IDEWE | Interleuvenlaan 58 | 3001 Heverlee


<      (e-mail disclaimer NL  / FR  )

 

Вложения

Re: fn TIMESTAMPADD

От
Clemens Ladisch
Дата:
Matthias Coene wrote:
> I seem to have a problem with the TIMESTAMPADD function:
>
>      {fn TimestampAdd(SQL_TSI_YEAR, 18, T54148.GEBOREN)} as c2
>
> [nQSError: 16001] ODBC error state: 42703 code: 1 message: *ERROR: column "sql_tsi_year" does not exist;*

psqlODBC supports neither the TIMESTAMPADD function nor the SQL_TSI_YEAR
keyword, and it correctly reports this lack of support through the
SQLGetInfo function.

Apparently, Oracle BI does not check whether this is supported.
(But it wouldn't be easy for it to work around this even if it checked.)


Regards,
Clemens