-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Model discovery not working with Oracle connector & CDB instance #3296
Model discovery not working with Oracle connector & CDB instance #3296
Comments
@bigal-cloud thank you for reporting the issue. What is the version of
Please be more specific, what is the last version where this worked and what is the first version where it stopped to work? |
@raymondfeng you are most familiar with the Oracle connector, PTAL. |
Hello @bajtos , thanks for replying. I am using: For the other questions I need a little more time. |
The last working version was: The first non working version was: |
Getting the exact same results over here. I'm using those versions:
|
I think this is something we should take a look and try to reproduce from our end in Q4, if not sooner. |
Can you try to install https://github.com/oracle/node-oracledb and see if https://github.com/oracle/node-oracledb/blob/master/examples/example.js is working for you? We use |
@bigal-cloud @Tavisco , please see @raymondfeng 's comment. :) |
Hi @emonddr sorry for the late reply. I don't have access write to the database I'm testing with, so i've ran only the last part of the example.js file that selects the current date from dual, and it worked as expected. |
I'm able to reproduce the problem now. Will take a look tomorrow. |
Please try [email protected] |
Using |
Steps to reproduce
npm run build
lb4 discover
- select a model and hit enterCurrent Behavior
Expected Behavior
To create a model
Link to reproduction sanbox
Additional information
It was working fine in previous versions
Related Issues
See Reporting Issues for more tips on writing good issues
The text was updated successfully, but these errors were encountered: