Skip to content

Conversation

@redfish-zly
Copy link

Check List:

  • Unit tests: YES / NO / NA
  • Documentation: YES / NO / NA

Copy link
Contributor

@filiphr filiphr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What are you trying to fix here @redfish-zly? I am not sure that we should be using the connection on this level. The connectionMetadataDefaultCatalog is eventually used only in AbstractSqlScriptBasedDbSchemaManager, so if something needs changing we can maybe do it directly there.

Would also be good to have a bit more insight in what problem you are trying to solve

@redfish-zly
Copy link
Author

image image

@filiphr
Hello senior, I am not sure if my solution is correct. Here are the problems I have encountered.
Preconditions:
There are two database instances on the MySQL server, flowableTest1,
flowableTest2。
Among them, flowableTest1 has already initialized the process related tables (Act_ *), but flowableTest2 does not.
At this point, when my springboot project connects to flowableTest2 and says' flowable. database schema update=create ', the initialization of the flowableTest2 table fails due to the null catalog.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants