Project

General

Profile

Bug #1818

Incorrect upgrade sql logic

Added by Vasily Bezruchkin about 6 years ago. Updated almost 6 years ago.

Status:
Closed
Priority:
Normal
Category:
Installer
Target version:
Start date:
October 19, 2014
Due date:
% Done:

100%

Estimated time:

Description

Now when you write upgrade sql instructions in install.xml the system works a bit incorrect.
let's imagine you changed one field for personal blog table, you make some intermediate file changes

Your personal blog version released with the core was 3.1.0 but when you release a new core version, it might require one db change. I don't know what version is used now on a customer website BUT I do know I must run update for any versions from 3.1.0. We need to implement a way to run queries for the version you install now, not for a previous one.

Ask me.

History

#1

Updated by Vasily Bezruchkin about 6 years ago

  • Target version changed from 3.2.1 to 3.3.1
#2

Updated by Vasily Bezruchkin about 6 years ago

  • Target version changed from 3.3.1 to 3.2.2
#3

Updated by Vasily Bezruchkin about 6 years ago

  • Target version changed from 3.2.2 to 3.2.6
#4

Updated by Vasily Bezruchkin about 6 years ago

  • Target version changed from 3.2.6 to 3.2.3
#5

Updated by Vasily Bezruchkin almost 6 years ago

  • Status changed from New to Closed
  • % Done changed from 0 to 100

Also available in: Atom PDF