Google Code skipped issue 35 about flyway HOT 5 CLOSED

From [email protected] on March 29, 2011 00:45:16
I've made a change on my repo clone regarding Spring context scanning. However, I think that I've got somewhere into the chicken-egg problem, because I was trying to use my application's DAO objects inside a migration, but they depend on the EntityManager, which must be build against the updated schema.

from flyway.

From [email protected] on March 29, 2011 07:27:31
Yes, this definitely makes sense. The context usually contains many beans which depend on Flyway having performed the DB migrations.

This feature was originally intended for cases where one would like to reuse some logic available through some other beans.

However, I must say that part of the reason why no work has been done towards this so far, is that it's a need that hasn't materialized on the projects I work on.

from flyway.

From [email protected] on March 30, 2011 21:38:07
Anyway, it's commited on my clone.

from flyway.

From [email protected] on April 03, 2011 21:52:37
What is your use case for this?

from flyway.

From [email protected] on September 28, 2011 05:05:01
Closing due to lack of interest/need. Workaround: access beans of spring context through singleton context reference.

from flyway.