It's actually creating the DATABASECHANGELOG table in the database rather than adding to the SQL export. That's indeed a bug.

On 22 September 2016 at 09:55, Stian Thorgersen <sthorger@redhat.com> wrote:
I assume you mean initializeEmpty=false and migrationStrategy=manual?

You shouldn't need to create anything manually outside the SQL so this would indeed be a bug. Strange thing is that we've had the opposite reported: https://issues.jboss.org/browse/KEYCLOAK-3588

On 21 September 2016 at 21:11, Harold Campbell <hcamp@muerte.net> wrote:
Bringing up KC against an empty database with initializeEmpty=manual
generates a sql file which does not include creating
the DATABASECHANGELOG table. Is this intentional? Am I missing a step
somewhere? Or is creating the table by hand based on http://www.liquiba
se.org/documentation/databasechangelog_table.html the way forward?

--
Harold Campbell <hcamp@muerte.net>

The algorithm for finding the longest path in a graph is NP-complete.
For you systems people, that means it's *real slow*.
                -- Bart Miller
_______________________________________________
keycloak-user mailing list
keycloak-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-user