Using MySQL var in Pocket Query Macro

I have the below SQL Script which is running fine in MySQL:

=============================================

set @Sunday1WeekAgo = subdate(curdate(),date_format(curdate(),'%w')+7);

select COUNT(DISTINCT TITLE) PagesCreated

from CONTENT

where CONTENTTYPE='PAGE' AND SPACEID is not null

AND creationdate>=@Sunday1WeekAgo

=============================================

But when I put it in Pocket Query SQL statement, it can be executed well.

the page has this error information:

There were errors executing this statement.

There were errors executing this statement. Please check whether the following parameters are given: []. If the parameters are correct or no parameters are required, something must be wrong with the query or the database connection. Use the debug mode for a error trace and/or contact your administrator.

Is it beacuse PocketQuery macro cannot identify mySQL var - @Sunday1WeekAgo ?

Anyone can help?

4 answers

Hi Kai,

can you please activate debug mode by checking the debug checkbox in the PocketQuery macro? You will then see the stack trace of the error. Please provide that error message here and I will analyse your problem further.

Regards,
Felix

(error_message.txt)

Sorry for the late, Felix.

I attached the error message and stack trace: (error_message.txt)

Maybe this marco does not support SET command?

Sorry for the late, Felix.

I attached the error message and stack trace.

Maybe this marco does not support SET command?

Probably the Spring JDBC Query is having problems with the SET command before the SELECT statement. Why not using this statement?

Just an idea,

Christian

select COUNT(DISTINCT TITLE) PagesCreated
from CONTENT
where CONTENTTYPE='PAGE' AND SPACEID is not null
having creationdate>=subdate(curdate(),date_format(curdate(),'%w')+7);

I've made a short test with a starting SET command and got an org.springframework.jdbc.BadSqlGrammarException exception

Thanks for the help.

I think may this marco cannot support SET command well.

Actually, this has nothing to do with the PocketQuery macro itself but with the underlying Spring-JDBC implementation. Have you tried the workaround provided by Christian?

Actually, this has nothing to do with the PocketQuery macro itself but with the underlying Spring-JDBC implementation. Have you tried the workaround provided by Christian?

Suggest an answer

Log in or Sign up to answer
Community showcase

Scrum Roles Explained: the Do's and the Don'ts

Hello Community,  Today we are going to talk about the three Scrum Roles. There is the Development Team, the Scrum Master and the Product Owner. In my opinion these three are all really impo...

144 views 2 6
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you