DevServices : quarkus.datasource.devservices.container-properties

[adarshahd]

I would like to know what are the available properties for the container-properties.

I have a migration sql inside resources/db/migration, which specifies the database name (ex: CREATE SCHEMA IF NOT EXISTS posts). It results in error during migration because Flyway assumes database name to be 'default' (From DevServices).

I guessed several different options for the container-properties so that I could change the database name, but doesn't work. I would like to know the options. Thanks in advance.

As a workaround if I remove the database name in the migration sql, then everything works fine.

[quarkus-bot[bot]]

/cc @stuartwdouglas

[pcaceresf]

Devservices is a really problem, by default always FAILS, i spendt a lot of time with this fucking problem.

[gsmet]

@pcaceresf please be polite. Also did you create GitHub issues explaining your problems? It works for a lot of people.

[adarshahd]

@pcaceresf hey, calm down! not sure what exactly is your problem, but I feel generally Quarkus is really good framework. You could specify your issues and community can take a look.

[gsmet]

@adarshahd could you create an issue with a small Maven reproducer explaining exactly what your problem is? We will have a look.

[gsmet]

Maybe it wasn't clear but I totally agree on that. I added something on my TODO list.

[adarshahd]

Thank you very much!

[ghost]

@gsmet I'm not sure if the issue described by @adarshahd is the same one I experienced earlier today, but it sure seems like it. Earlier today, I discovered that DevServices will attempt to use the name of the declared datasource as the default schema when performing queries. For example, a MySQL datasource declared like this:

quarkus.datasource.test.reactive=false
quarkus.datasource.test.db-kind=mysql
quarkus.datasource.test.username=root
quarkus.datasource.test.password=taco

And injected into code like this:

@ApplicationScoped
class PotatoTypeReadOnlyRepository : IPotatoTypeReadRepository {
	// Dependencies
	private val testDataSource: AgroalDataSourcel

	// Constructors
	@Inject
	constructor(@DataSource("test") testDataSource: AgroalDataSource) {
		this.testDataSource = testDataSource
	}
}

Will attempt to use test as the database schema. Which means when I submit a query like this:

val sqlQuery = "select * from PotatoTypes where NAME = ? order by NAME limit 2"

It attempts to query the test.PotatoTypes table. And if that table exists on the POTATO_DB schema, and not a schema named test, the query fails.

I was kinda expecting there to be a configuration class property that let me set the name of the schema that's associated with a datasource. Something like this:

quarkus.datasource.test.schema=POTATO_DB

If it's worth writing up the behavior I experienced as a separate discussion, say the word & I'll get that done on Tuesday. I already have most of the sample repository code ready -- I just need to make a few changes & then get that code up into a new GitHub repo.

[gsmet]

@adarshahd what I did in the last commit of this PR should make it easier for you: #25288 . It's going to be automatically documented in the configuration reference.

[adarshahd]

@gsmet I can see these changes will make it easy to modify username/password/schema names. Thank you very much again!