Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Linked Table issues #4050

Open
marat-ak opened this issue May 2, 2024 · 0 comments
Open

Linked Table issues #4050

marat-ak opened this issue May 2, 2024 · 0 comments

Comments

@marat-ak
Copy link

marat-ak commented May 2, 2024

Hello,
I have faced 2 issues with linked tables
1)
It looks like set autocommit on linked table has no affect on real connection and it's remain defaulted.
For insert 2-3K of rows to Oracle over linked table we can see partial results.
From code I can see that
It uses TableLinkConnection.setAutoCommit(boolean mode) {
this.autocommit= mode;

But conn property(which holds real connection) remain unaffected.
I'm not experienced java programmer , but for test I have added to
TableLinkConnection.setAutoCommit(boolean mode)
additional line of code
this.conn.setAutoCommit(mode);

The behavior was fixed , now but there is no possibility to commit the changes - COMMIT statement doesn't commit remote connection

  1. when insert to linked table is executed it runs
    LinkedIndex.add function , which builds TARGET sql string.
    In case when value is null it appends NULL string .
    So for table t1(c1 var,c2 var,c3 var) insert of rows if with null values in different columns will generate different sql and so multiple prepared statements. In our case tables has hundreds of columns and insert of 2-3K of rows generates hundreds of sqls/prepared statements

Thanks,

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant