Default datasource for configuration with schema-name and table prefix

Camunda 7 Topics Discussion & Questions
1

Hello, everyone!
We are using camunda-bpm-spring-boot-starter version 3.4.2
Our database in Postgres. We moved camunda tables to specific schema and changed camunda configuration:

camunda:
    bpm:
        database:
            schema-name: camunda
            table-prefix: camunda.
            schema-update: false

we have a single datasource configured

spring:
    datasource:
        url: ${DB_URL:jdbc:postgresql://localhost:5432/om}
        username: ${DB_USER:postgres}
        password: ${DB_PASSWORD:postgres}
        driverClassName: org.postgresql.Driver
        hikari:
            maximum-pool-size: 20

As I understand camunda uses this exactly datasource in embeded mode, or am I missing something?

2

Hi @spiderpigspy
Welcome!
What exactly is going wrong?
The table prefix is only really needed if you have more than one schema per data-source so unless that is the case you can remove it.

3

Sorry for my bad English and misunderstanding.
Nothing is going wrong, I just wanted to be sure that camunda does not create new datasource for my configuration.
We only moved camunda tables to another schema for our convenience, and we worry that we can encounter problems later.

4

Right, i understand. It looks like you’re set things up just fine.
Camunda wont create it’s own datasource

5