The goal is not to create a table inside an execute native
But rather create a table in container1 after execute native a statement in data container2.
Sorry if this wasn’t clear.
Add possibility to create or replace a table from a execute native statement that would allow server side filtering to circumvent client (Invantive) side filtering, generating unmatched performance when for exemple a join is made between million record table tables.
create or replace table mytable@container1
as
execute native 'select ML.Id, ML.Debit, ML.credit, ML.Balance, ML.Account_id, ML.Payment_id, ML.Journal_id, ML.Partner_id, ML.Move_id, ML.Date, ML.Invoice_id, ML.Quantity, ML.Name
from account_move_line ML
left join account_move M ON ML.Move_id = M.Id
where M.state LIKE ''posted''
LIMIT 10000' DATACONTAINER 'container2'
Add possibility to Bulk insert from a execute native statement. That would allow to insert in bulk values and leveraging server-side filtering to circumvent client (Invantive) side filtering when for exemple a join is made between million record table tables, instead of using a loop stmt as described Faster loading from execute native
Bulk Insert mytable@container1
execute native 'select ML.Id, ML.Debit, ML.credit, ML.Balance, ML.Account_id, ML.Payment_id, ML.Journal_id, ML.Partner_id, ML.Move_id, ML.Date, ML.Invoice_id, ML.Quantity, ML.Name
from account_move_line ML
LEFT JOIN account_move M ON ML.Move_id = M.Id
where M.state LIKE ''posted''
LIMIT 10000' DATACONTAINER 'container2'