My bad as always. Having the refresh after the filling of the tables
does the trick. Thanks for your help.
On 3/24/24 14:27, Thiemo Kellner wrote:
Feeling quite dumb now. But then, there neither is data visible in
the install session.
insert data into TASK_DEPENDENCY⠒V
INSERT 0 34
The above says the data was inserted.
But not into the MV but into TASK_DEPENDENCY⠒V.
Where and when was the coun
Am 24.03.2024 um 22:06 schrieb Adrian Klaver:
The view session is on auto commit. (It's sole purpose to query stuff
and not to have explicitly terminate transactions do to syntax errors
and so on.)
Autocommit will only affect actions in that session, it will not make
the other sessions action
On 3/24/24 13:58, Thiemo Kellner wrote:
Am 24.03.2024 um 21:50 schrieb Adrian Klaver:
On 3/24/24 13:36, Thiemo Kellner wrote:
It does depending on the order of viewing. Namely if you viewed the
'old' empty MV in the outside session before you dropped/created the
'new' MV and committed the chan
Am 24.03.2024 um 21:50 schrieb Adrian Klaver:
On 3/24/24 13:36, Thiemo Kellner wrote:
It does depending on the order of viewing. Namely if you viewed the
'old' empty MV in the outside session before you dropped/created the
'new' MV and committed the changes.
Something like the viewing session
On 3/24/24 13:36, Thiemo Kellner wrote:
Am 24.03.2024 um 21:30 schrieb Adrian Klaver:
On 3/24/24 13:11, Thiemo Kellner wrote:
Confirmed in the same session that created it or in a different session?
Different session, not knowing what that mattered
It does depending on the order of viewing.
Am 24.03.2024 um 21:30 schrieb Adrian Klaver:
On 3/24/24 13:11, Thiemo Kellner wrote:
Confirmed in the same session that created it or in a different session?
Different session, not knowing what that mattered.
Excerpt of the installation protocol:
…
## tenth level ##
Set materialised view QUER
On 3/24/24 13:11, Thiemo Kellner wrote:
Am 24.03.2024 um 20:56 schrieb Erik Wienhold:
Maybe you executed REFRESH in a transaction but did not commit it?
While I can see the point for the refresh (but there actually is a
commit), I cannot hold it valid for a create with data when the mv
act
Am 24.03.2024 um 20:56 schrieb Erik Wienhold:
Maybe you executed REFRESH in a transaction but did not commit it?
While I can see the point for the refresh (but there actually is a
commit), I cannot hold it valid for a create with data when the mv
actually is created (confirmed by being empt
On 3/24/24 11:12, Thiemo Kellner wrote:
Hi
I have created a materialized view with "with data". And I refreshed it
with "with data". The query of the mv returns records when executed
outside the mv. I would appreciate help with respect to what I miss that
my mv is empty. You might want to hav
On 2024-03-24 19:12 +0100, Thiemo Kellner wrote:
> I have created a materialized view with "with data". And I refreshed it with
> "with data". The query of the mv returns records when executed outside the
> mv. I would appreciate help with respect to what I miss that my mv is empty.
Maybe you exec
Hi
I have created a materialized view with "with data". And I refreshed it
with "with data". The query of the mv returns records when executed
outside the mv. I would appreciate help with respect to what I miss that
my mv is empty. You might want to have a look at the code attached.
Kind reg
12 matches
Mail list logo
