SQL-scripts | SQL Scripts - PostgreSQL , MySQL , Google BigQuery | GCP library

I resolved this by reinstalling the Centos 8 from scratch

The whole point is to make sure that your tests are isolated and data required or generated by a test, won't affect the result of a different test.

Re-creating the schema gives you this guarantee because each tests will start with a clean database.

That said, the creation/drop of the schema is a pretty heavy operation, and the more tests you add to the test suite, the slower it will become. The drawback is that you need to make sure that the data is cleaned after each test. This might not be too complicated to achieve in practice (you might need to pay special attention about different entities in different tests mapping to table with the same name) but if you are working an a small project or your database is really quick updating the schema, it might not be worth the hassle.

It's up to you to decide what works for your project.

As a practical example, in Hibernate Reactive we need to run the same tests on several different databases. We started re-creating the factory for each unit test, but because running tests was becoming too slow (especially on some databases), we've switched to re-creating the factory once for each test class. It helped us to save a lot of time because tests in the same class became so much faster.

In the end, you need to decide how your test suite is organised and the benefits of one approach over the other. But as long as you are reasonably sure that the tests won't affect each other, you can use the solution you prefer.

In Cloud Build, a step is a stage of the processing. This stage is described by a container to load, containing the required binaries for the processing to perform in the stage.

To this container, you can define an entrypoint, the binary to run in side the container, and args to pass to it.

You have also several option that you can see here.

An important concept to understand is that ONLY the /workspace directory is kept from one step to another one. At the end of each step, the container is offloaded and you lost all the data in memory (like environment variable) and the data stored outside of the /workspace directory (such as system dependency installation). Keep this in mind, many of issues come from there.

EDIT 1:

In a step, you can, out of the box, run 1 command on one container. gsutil, gcloud, mvn, node,.... All depends on your container and your entrypoint.

But there is a useful advance capacity, when you need to run many commands on the same container. It can occur for many reason. You can do such like this

The basic way is just to split such tasks into sub-tasks.

The smaller, thus easier, sub-tasks here could be the following:

1. Get all rows (matching the criteria "Date" and "Country") which exist in table2, but are absent in table1.
2. Get all rows (matching the criteria "Date" and "Country") which exist in table1, but are absent in table2.
3. Get all rows (matching the criteria "Date" and "Country") which exist in both table2 and table1, but taking rows only from table2.
4. Put UNION ALL in between the parts you’ve previously created and tested (to make sure everything works properly).

Therefore, here is a possible strightforward solution:

The mysql image has the a volume mounted that stores the database. If the folder does not exists, it is created and your scripts are applied.

Instead of trying to write a script that destroys the way the base image is built, just change your base image and make it run scripts every times as it is suggested in this question : docker-compose: reinitializing MySQL db every time

Found a solution to this. Apparently it'S only with PDO where you can't run multiple commands. So something like pg_query() would suffice rather than prepare()

If you migrate to something like Flyway, you could build a controller that calls flyway's clean method like referenced here. Would be easy to migrate and maintain long term.

A few things to check:

1. Does the mysql container indicate that it started up correctly?
2. Is your mysql setup too complicated (see below)?
3. Have you tried connecting to your mysql instance with another application (e.g. datagrip, or some other mysql client?)
4. Have you ensured that mysql is actually done with it's startup process before you connect to it? depends_on may not really work properly here -- other application won't start up until after mysql starts, but mysql won't necessarily be configured yet -- i.e. your test.sql may not have actually run.

Your mysql setup seems somewhat complicated. Does it need to be? I've used a similar set of technologies and my docker compose for the database looked like this:

SQLCODE=7 is SQL0007N

The description of the error message is

SQL0007N The statement was not processed because a character that is not supported in SQL statements was included in the SQL statement.

The specified character is not a valid character in SQL statements. The "" runtime token indicates the 20 characters of the SQL statement that preceded the character that is not valid.

So your invalid character is (close to) this text \;E:

I suspect that you are trying to run two statements in one statement. As per e.g https://stackoverflow.com/a/2071724/9525344 you need to execute the statements one at a time