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

SQL syntax error, expected token is 'EQ', actual token is 'IDENTIFIER', literals is 'contractsm0_' #4016

Closed
ghost opened this issue Jan 19, 2020 · 8 comments

Comments

@ghost
Copy link

ghost commented Jan 19, 2020

No description provided.

@ghost
Copy link
Author

ghost commented Jan 19, 2020

select taker.createdAt as takerCreatedAt,
       taker.userId,
       maker.price as makerPrice,
       maker.quantity as makerQuantity,
       maker.fee + taker.fee as sysFee
from t_order taker left join t_order maker
                   on taker.orderId = maker.counterOrderId
                    and taker.counterOrderId = maker.orderId
where

      taker.type = 'TAKER'
      and taker.createdAt between 1579104000000 and 1579251131120
      and maker.createdAt between 1579104000000 and 1579251131120
order by taker.orderId asc,taker.counterOrderId asc limit 1000;

@ghost
Copy link
Author

ghost commented Jan 19, 2020

执行时会出现标题显示的问题,希望能帮忙处理一下

@terrymanu
Copy link
Member

执行时会出现标题显示的问题,希望能帮忙处理一下

Hi, for English only

@terrymanu
Copy link
Member

What is your version?

@ghost
Copy link
Author

ghost commented Jan 19, 2020

sharding- jdbc version 3.0.0

@kimmking
Copy link
Member

sharding- jdbc version 3.0.0

can you try it with sharding-jdbc 4.0.0 ?

@SteNicholas
Copy link
Member

@succeo Could you please the latest version of sharding-jdbc? Your version is too old to hardly validate the problem you mentioned.

@ghost
Copy link
Author

ghost commented Jan 19, 2020

The problem is solved,thank you

@ghost ghost closed this as completed Jan 19, 2020
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants