DB issue with lowercase in SQL statement: Unable to fetch and process metadata
See original GitHub issueThis is a…
[ ] Feature request
[ ] Regression (a behavior that used to work and stopped working in a new release)
[x] Bug report
[ ] Documentation issue or request
The problem
Unable to fetch and process metadata, see steps to reproduce. Errors are seen in steps 5 and 6. Error on web console:
ERROR TypeError: t.lineMachine is undefined
Stack trace:
4dAV/ui</t.prototype.updateFromConfig/<@https://syndesis.192.168.99.100.nip.io/main.29a32246d29c20888f96.bundle.js:1:398436
eFQL/</</</c</t.prototype.invokeTask@https://syndesis.192.168.99.100.nip.io/polyfills.00b2490f9e8f9b4c7b5e.bundle.js:1:50302
onInvokeTask@https://syndesis.192.168.99.100.nip.io/main.29a32246d29c20888f96.bundle.js:1:1087546
eFQL/</</</c</t.prototype.invokeTask@https://syndesis.192.168.99.100.nip.io/polyfills.00b2490f9e8f9b4c7b5e.bundle.js:1:50215
eFQL/</</</o</e.prototype.runTask@https://syndesis.192.168.99.100.nip.io/polyfills.00b2490f9e8f9b4c7b5e.bundle.js:1:45472
eFQL/</</</a</e.invokeTask@https://syndesis.192.168.99.100.nip.io/polyfills.00b2490f9e8f9b4c7b5e.bundle.js:1:51396
e/this.invoke<@https://syndesis.192.168.99.100.nip.io/polyfills.00b2490f9e8f9b4c7b5e.bundle.js:1:51281
c/n.args[0]@https://syndesis.192.168.99.100.nip.io/polyfills.00b2490f9e8f9b4c7b5e.bundle.js:1:66337
main.29a32246d29c20888f96.bundle.js:1:1070550
and following errors in meta.log (oc logs syndesis-meta-… > meta.log) meta.log
server.log and db.log looks OK.
This problem is somehow related only to CONTACT db table in the FINISH connection. (not with TODO table. e.g. if in step 5 we specify eg.
INSERT INTO TODO(task, completed) VALUES(:#task, 0),
this misbehavior is not seen.)
Expected behavior
Screenshot
API Endpoints and Schemas
POST https://syndesis.192.168.99.100.nip.io/api/v1/connections/5/actions/sql-connector Request Body: {“query”:“INSERT INTO CONTACT (first_name) values (:#fn)”}
response: sql-connector.json.txt
Tasks involved / Steps to Reproduce
- Select Create Integration.
- Select start connection PostgresDB.
- Select action “Periodic SQL invocation” and specify query “SELECT * FROM TODO”
- Select finish connection PostgresDB.
- Select action “Ivoke SQL”. and specify query related to CONTACT table “INSERT INTO CONTACT (first_name) values (:#fn)”
- add datamapper step
Issue Analytics
- State:
- Created 6 years ago
- Comments:6 (5 by maintainers)
Top Results From Across the Web
H2 in-memory database. Table not found - Stack Overflow
I have tried the above solution,but in my case as suggested in the console added the property DB_CLOSE_ON_EXIT=FALSE, it fixed the issue. spring.datasource.url= ......
Read more >How to do case-insensitive and accent-insensitive search in ...
Oracle Database 12.2 added the collate operator. ... Lowercase comes after uppercase in a binary collation and all the names in the table ......
Read more >2 Server Error Message Reference - MySQL :: Developer Zone
Possible causes: Permissions problem for source file; destination file already exists but is not writeable. Error number: 1005 ; Symbol: ER_CANT_CREATE_TABLE ; ...
Read more >Troubleshoot connector and format issues in mapping data flows
When you want to fetch data from Azure Cosmos DB through Serverless pool by query/from view, you face the following error: Job failed...
Read more >Overview of SQL LOWER and SQL UPPER functions
This article gives an overview of SQL UPPER function and SQL LOWER function to convert the character case as uppercase and lowercase ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
It looks like it’s related to ‘values’ being lowercase in:
INSERT INTO CONTACT (first_name) values (:#fn)
I will add a unit-test and fix for it.
Thanks @Stefan365 for double checking I’ll have a look.