jdbc `initialize-schema` creates table with default name, not the one from `table-name` property

Spring Session JDBC when requested to always initialize schema, creates tables named with default name (SPRING_SESSION) even when table-name param is overriding this name. Later at runtime, tables defined in table-name are missing, because not created by Spring Session.

Full config of SpringSession:

spring.session:
    store-type: jdbc
    jdbc:
      table-name: SPRING_SESSION_V2
      initialize-schema: always

version: 2.1.0.RELEASE

[jm-ck]

ok, If you say so.

It was pretty intuitive for me that when I can set the table-name and force to initialize-schema which works with the default names, it should also work with custom names.

so maybe your explanations could be included in docs? An this issue is more like a feature request.

[vpavic]

Closing as I believe I’ve provided you with pointers to relevant info which explains how things are implemented.

so maybe your explanations could be included in docs? An this issue is more like a feature request.

As noted in the previous comment, that request should be opened against Spring Boot.