-
Notifications
You must be signed in to change notification settings - Fork 6.7k
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
Table or view 'undo_log' does not exist #33523
Comments
|
ok I will upload my project sooner. |
my docker images: nacos/nacos-server v2.4.2 325b84d58cf7 6 weeks ago 285MB
canal/canal-server v1.6.1 9bf4fbb74f65 7 weeks ago 1.69GB
seataio/seata-server latest 9ba033ad828e 2 months ago 633MB
apache/rocketmq v5.3.0 4802c0635d11 3 months ago 419MB
mysql 8.1.0 ae2502152260 15 months ago 574MB
redis 5.0.14 99ee9af2b6b1 23 months ago 110MB I upload my test project: |
@SilenceDevelopers I don't need all the relevant code, I just need a unit test execution process similar to https://github.com/linghengqian-scratches/code-repo/tree/re-test. The git you uploaded seems to contain multiple unit tests. Which unit test throws the error log you refer to? What are the steps to reproduce? |
oh,sorry,I misunderstood. I didn't do a unit test. just When I was integrating the project, I found that the whole project would not start. |
I found out from the logs that shardingjdbc references Hikari and Druid, but the database driver I configured did not reference Hikari. |
|
OK,Thank you for your answer. |
|
There hasn't been any activity on this issue recently, and in order to prioritize active issues, it will be marked as stale. |
shardingsphere-jdbc 5.5.0 org.apache.seata 2.2.0
my yaml:
my sharding.yaml:
my undo_logs:
when I start up, the error is :Error creating bean with name 'dataSource' defined in class path resource [org/springframework/boot/autoconfigure/jdbc/DataSourceConfiguration$Hikari.class]: Table or view 'undo_log' does not exist.
my datasource is com.alibaba.druid.pool.DruidDataSource
I don't know why
The text was updated successfully, but these errors were encountered: