I have been looking for migration method from flyway version 1.x to 3.x
(i.e. com.googlecode.flyway to org.flywaydb) everywhere it is mentioned to migrate first to version 2.3 but no where it is mentioned how? Is there a direct way to do it or do I have to do something from backend.
My database already has data and I cannot drop database.
Note: Flyway 1.X to 2.X has breaking changes for table schema_version.
EDIT
I have upgraded my maven dependency for flyway from 1.5 to 3.1. It now says schema_version does not have some column which is made by flyway itself for its own reference. I went through docs and all over stackoverflow and found flyway 3.1 and 1.5 are incompatible. It is mentioned on SO and docs that we need to first upgrade to 2.3 and then to 3.1. But no where it is mentioned how. Because just by adding pom dependency, it doesnot seem to solve the schema_version problem.
I also tried adding 2.3 to pom and started my spring based application but still Flyway fails throwing stacktrace saying it cannot find some column.
Exact error is Unknown column 'success' in 'where clause' for schema_version table made by flyway 1.5 itself.
Please suggest how to fix this up ?
As you can see at Release Notes:
Dropped compatibility with the Flyway 1.X metadata table format. If you are upgrading from 1.X, you must upgrade to 2.3 first, before upgrading to 3.0.
you have to upgrade to version 2.3. And as you could read in Release Notes:
Flyway 2.1 (2013-03-05)
This version fixes minor issues with the metadata table. Migration is transparent and automatic on first run.
[...]
Flyway 2.0.2 (2012-11-22)
This version performs minor fixes on the metadata table. Migration is transparent and automatic on first run.
[...]
Flyway 2.0 (2012-11-14)
This version comes with a new metadata table format. Migration is transparent and automatic on first run.
Flyway upgrades its schema by itself.
See also:
MetaDataTableTo20FormatUpgrader.java
MetaDataTableTo202FormatUpgrader.java
MetaDataTableTo21FormatUpgrader.java
Related
I am working on a project and the client is using freePBX version 2.0.X and they want to upgrade their version to 14.0.X. How should I do this keeping in mind that all the data and configurations needs to be migrated to the newer version?
edit: to those who are marking it negative, I am new to this and if I new the answer then, I wouldn't ask.
You have update 2.0->2.2. After that 2.2 -> 2.4, 2.4->2.5, 2.5->2.6
After that you have updat 2.6 to 13, 13 to 14.
Some of this upgrades not go without problem, huge experience required.
On upgrade from 2.6 to 13 you have also upgrade asterisk to version 13.
If you have no very complex config, in most cases faster will be backup extensions, dids, restore, put all other config items.
ps also you need have archive for thoose version,i think it will be complex to find something below 2.4
We are thinking of upgrading our Symfony app to Symfony 4.
The app is currently on Symfony 2.6 version (we can upgrade to php 7).
What are the benefits to upgrade through 2 stages from 2.6 to 3 then from 3 to 4 compared with upgrading directly from Symfony 2.6 to Symfony 4?
There are some differences between SF 3.4 and SF 4. So if you have an older Version you should first upgrade to SF 3.4. This is because SF 4 has another structure and use the flex framework. It's possible that you have to change a lot of things during the migration. If you have the time you can do that. If your have Unit-Tests it's much easier to find all the problems.
In general you should read the migration documents that describes the changes in every version and change your code in that way.
https://symfony.com/doc/2.7/setup/upgrade_major.html
So better you upgrade first to version 3.4. Then you have the compatibility to your older code and plugins but no new features that come up in SF 4. But all that depends on the size of your application.
You can upgrade, but it will be very painful because the development methodology has changed very much between symfony2 and symfony4. Will better to install separate Symfony 4 project and implement each component of application separate.
You should upgrade by this step:
1 -Symfony2.6 to Symfony2.7
2- Symfony2.7 to Symfony2.8
3 - Symfony2.8 to Symfony3.4
4- Symfony3.4 to Symfony4
I'm wondering if it makes sense to use the Symfony 4 file structure (as described in Fabian's post) for projects running Symfony 3.3 and 3.4?
The Architecture page in the documentation for 3.3, 3.4 and 4.0 all show the version 3.* directory structure so I'm not sure where the canonical information is and thus I'm not 100% sure it's either a good idea nor what the "final" decision is.
Yes, it is good idea – if you plan to start using Symfony Flex (the next big thing in Symfony world), the directory structure used Symfony 4 is required. Last version of Symfony Standard Edition will be 3.4, so if you want your application to keep up to date, it's better choice to start use that structure now, than moving and review tens (or hundreds) of files later.
Documentation is not yet updated – current master version (4.0) is just clone of 3.4.
So I updated to swift 3.0 and now my projects with realm 1.0.2 all give me an error.
RealmSwift compiled with older version of Swift language (2.0) than previous files (3.0)
I also tried to build a net new project and still get the build error, so I know it is not a conversion issue on the Swift side.
I found several Swift 3.0 beta users and tried to run the script to update my version to 3.0 and several other options. The last few posts appeared to use Cocoa Pods - which I don't currently use. Is that the supported fix path?
Any help or direction would be greatly appreciated.
I haven't tried it yet, but here is what should work.
Essentially, the compiler gives you a description of what went wrong. The framework was compiled with Swift 2.0, while your project or other files were compiled with Swift version 3.0 (which means you made the switch after upgrading to the new version of Xcode.
To fix this, you need to use the Realm framework compiled with a Swift 3.0 compiler. Since the Realm team doesn't yet provide a precompiled version compiled with Swift 3.0, you have to do so yourself. To do that, go to their Github repository, and follow the instructions in the README under "Building Realm":
Prerequisites:
Building Realm requires Xcode 7.3.
Building Realm documentation requires jazzy
Once you have all the necessary prerequisites, building
Realm.framework just takes a single command: sh build.sh build.
You'll need an internet connection the first time you build Realm to
download the core binary.
This should generate the Realm framework with the current compiler version, which you then just have to use to replace your current Realm framework with. After that, everything should compile as it used to.
As stated before, I don't know if this actually works, as I haven't tried it yet. I don't exactly know if Swift 3.0 is supported by Realm yet or if there are any other issues you could run into. So please let me know how this works out!
I want to upgrage Alfresco from 3.4 to 5.1 community Edition on linux
What should I do exactly ? ?
Actually you cannot upgrade directly to 5.1.
You will have to update to 4.x beforehand and as a next step upgrade from 4.x to 5.1.
This is described here in the documentation.
Briefly you will have to do following:
backup your database and alf_data folder
install 4.x
configure it to use your existing (3.4) database and alf_data folder (in alfresco-global.properties)
start it and wait till all upgrades scripts will execute successfully
install 5.1
configure it to use your existing database and alf_data folder (in alfresco-global.properties)
start it and wait till all upgrades scripts will execute successfully
Please note that 5.1 don't have an user interface in /alfresco (repo) webapp.
GUI was separated to /share webapp so all your customization should be rewritten/reconfigured to be used inside Share.
For more information on how to upgrade Alfresco please follow instructions from this official documentation page Upgrading Alfresco on a single instance.
If you have "default configuration"- I mean like there you dont have some custom things like certificates, etc..
You dont need to backup & restore complete "alf_data", but just alf_data contentStore & contentStore.deleted should be fine
Also one importatnt thing
database backup must be made firts, earlier than "data" backup- because of indexes saved in DB
(if there will be indexed some files, which will dont be in data, alfresco will dont start, if there will be some files without indexes, it will index them)
Btw also what is recommended is to make reindex (on new Alfresco)- steps has dependencies on the Alfresco version (eg. Alf 4 has solr1, alf 5.x has solr4 by default), but its usually something like this