On Monday, November 13, 2023, Anthony Apollis
wrote:
>
> Please advice.
>
The subset of data you’ve chosen to show does not allow one to draw any
conclusions. Look for the things that are different in the joined result -
the things that are identical are mostly uninteresting when trying to
figur
Please advice. I brought in data from SAP and assigned unique primary key
to the table:
[image: unique]
CREATE TABLE IF NOT EXISTS fact."IMETA_ZTRB_MP$F_ZTBR_TA_BW"
(
"ZTBR_TransactionCode" integer NOT NULL,
"Company_Code" character varying COLLATE pg_catalog."default",
"Posting_Perio
Thanks for pointing out. The only use case of conditional compilation, I
can think of, is, that one can have arbitrary logging code in some
environments without performance penalty in others, e.g. log as hell in
dev, no logging at all in prod without the "function" having to execute
checks for
Ron writes:
> On 11/12/23 09:32, Thiemo Kellner wrote:
>> Does PostgreSQL have something like Oracle's conditional compilation? This
>> is sort of an if then statement that gets evaluated on
>> compilation/installation time of PL/SQL code. If the condition is met, the
>> code until the $END get
On 11/12/23 09:32, Thiemo Kellner wrote:
Hi
Does PostgreSQL have something like Oracle's conditional compilation? This
is sort of an if then statement that gets evaluated on
compilation/installation time of PL/SQL code. If the condition is met, the
code until the $END gets compiled. It is eve
Hi
Does PostgreSQL have something like Oracle's conditional compilation?
This is sort of an if then statement that gets evaluated on
compilation/installation time of PL/SQL code. If the condition is met,
the code until the $END gets compiled. It is even possible to switch
on/off parts of sing
