dbscript | php4-compatible meta-object fun

I wouldn't expect two different Zip algorithms/libraries to yield the same output. For one, in the programmatic way, the file metadata (name, modification date, attributes) are not set, while the command line version will include all that information for unzipping purposes.

Plus libraries update at different cadence than standalones, and you might not have the fixes synchronized to reliably match the outputs.

You are building your project here with the 4.7.2 framework, but in the yml you are referencing the .Net Core Framework. Could this be the problem?

initdb scripts are only executed when your data directory (/var/lib/mysql) is empty.

Your data are not cached, but persisted to your host using your volume. So if this is a development work, you can simply delete the contents of db_data volume (or deleting and creating it again):

The mysql image does not initialize the database if the volume is not clean.

When you are stopping and starting the database from the same compose file, the volume is always the same, hence you want the data to be persisted even after an app restart.

To force the re-initialization of the data, you can delete that docker volume(only if you no longer need that database! this cannot be undone):

First, stop and delete the containers.

Then list and delete the volume that persists the database:

The service name resolves to the IP of DB container.
The port exposed by the container is 3306.

Use mysql (the name of the DB service).
Use 3306(the port on which the DB container is listening instead of the port on which you are publishing on the host)

You are creating 4 nearly identical resources all named execute[Create_scripts] and when the notification fires from the first cookbook_file resource being updated it finds the last one of them to be notified and runs against test4 (no matter which cookbook_file resource updates).

The fix is to use string interpolation to change the name of the execute resources to be unique and to notify based on that unique name:

Check these 2 things:

The init scripts are triggered only on the first deploy. On the subsequent docker-compose ups you probably see as well on the logs the following message:

After submitting the form you have to use event.preventDefault()

1. As I have not used MultiTenantConnectionProvider so not sure at what point the datasource is chosen by the framework.

2. But I have a great suspicion it is done by the interceptor auto created by @Transactional, and the framework never reads the TenantContext inside the method. I.e one datasource for one transactional method. So may be worth identifying if my suspicion is true.

   • You can put a breakpoint at the following :