Niveau 1
Niveau 2
Se connecter à la communauté
Connectez-vous pour voir tous les badges
Hi All,
I've integrated query service with DB visualizer client and querying dataset. But it gives me syntax error.
Query : Select * from my_dataset
Error : [Code: 0, SQL State: 42601] ERROR: line 1:28: mismatched input ',' expecting {<EOF>, '.', '[', 'AT', '+', '-', '*', '/', '%', '||', '::', '^'}
Query Service log :
To check this issue, I've integrated query service with HeidiSQL client and executed the same query successfully.
Thanks.
Résolu ! Accéder à la solution.
Vues
Réponses
Nombre de J’aime
I see, issue could be with path. Do you have any attribute/column which is a root node and doesn't require (.) operator. E.g: Select timestamp from xxxxx . Also please check log on AEP side in query service section.
Edit : Can you please also confirm, which version of DBV you're using ? I tried same stuffs and they're working fine with DBV 13.0.4.
I feel, this is something to do with DBV not AEP. Looking at your editor of DBV if you see column path 'name' is interpreted as keyword. It could be earlier version of DBV results into error but they might have fixed it in latest version ?
Hi @vikash4,
You may try listing actual column names that are required instead '*'.
Vues
Réponses
Nombre de J’aime
Hi @AtulChavan ,
thanks for your reply.
Tried with column name but facing same error. Same query running successfully in AEP query service but not in DB visualizer.
Vues
Réponses
Nombre de J’aime
I see, issue could be with path. Do you have any attribute/column which is a root node and doesn't require (.) operator. E.g: Select timestamp from xxxxx . Also please check log on AEP side in query service section.
Edit : Can you please also confirm, which version of DBV you're using ? I tried same stuffs and they're working fine with DBV 13.0.4.
I feel, this is something to do with DBV not AEP. Looking at your editor of DBV if you see column path 'name' is interpreted as keyword. It could be earlier version of DBV results into error but they might have fixed it in latest version ?