Re: schema migration

[Alexandr S. Dubovikov]

8/14/2012 5:43 PM, Douglas Hubler wrote:

On Tuesday, August 14, 2012 6:47:57 AM UTC-4, Alexandr Dubovikov wrote:

these changes are only for multi tables solution (high load systems),
but you can still use the old SQL schema, it's back compatible.

 

I assume you mean "multi-database" not "multi-table".

sorry,  yes, the patches from Dragos (1&1)

but you are right, we need create a new development branch and do all
new features/changes there and use the master branch for bug fixes only.

On that note, you have a timeline for that?

branching helps reduce the db migration problem but is doesn't eliminate it.  How would someone update from one released version to the next release version?  If you solve the problem in general then you can solve the problem in the more general case : any dev release to any other dev release. Anyway, only real solution I've seen is to maintain sql migration scripts but project may not be ready for that.  

yes, i think the best way will create a version table like in kamailio/opensips and base on this information make migration with a script.

or maybe someone has better idea ? Wake up guys!

Wbr,
Alexandr