Yep, but then someone came along and talked about millions of users ;)
----- Original Message -----
From: "Marek Posolda" <mposolda(a)redhat.com>
To: "Stian Thorgersen" <stian(a)redhat.com>, "keycloak dev"
Sent: Monday, 6 October, 2014 4:10:57 PM
Subject: Re: [keycloak-dev] Database migration
At some point we wanted to use export/import for that?
- export whole DB content to json file with KC 1.0.Final
- Transform JSON content from 1.0.Final format to "1.1.0.Beta1" format
(would likely need to be detyped due to possible changes in
- Import JSON back to DB
It required re-creating DB from scratch, but on the other hand it's very
generic and independent on model (not tightly coupled to SQL/JPA).
On 6.10.2014 13:32, Stian Thorgersen wrote:
> For 1.1.0.Beta1 the DB schema has changed (user and client sessions only).
> That means we'll have to provide a migration strategy. As part of testing
> a release we'll also have to start testing migrating a server.
> I found a couple tools to help migrating databases (http://flywaydb.org/
). It's probably worth looking at those as they
> let you have a single update script for all databases.
> With that in mind, and the adapter clustering issues, 1.1.0.Beta1 is
> probably not going to be until later this week or early next week.
> keycloak-dev mailing list