Since the branch cut has happened, we can bump and get rid of legacy
cruft. According to the policy we can go up to 1.31 but let's keep it
that way to avoid major distruptions.
Change-Id: I9d697445a3bb5047726c8b2a7f808edb8403cdda
Also added token and flags fields. The token field can
be used as a tie-breaker for modtime and also for faster
cas() operations. The flags field makes serialization and
compression format changes easier in the future.
Bug: T274174
Change-Id: I45731a877b21835652993c2d285165a76eeae3e9
This patch was introduced in r1030 (2002) and was never
wired to update.php and any mention of it was removed from documentation
in r23242 (2007). Since then, you can't find any mention of this file.
It clearly won't run on any modern mediawiki database.
Change-Id: I49a7a0bd53d5fb1b97f9c7016bb72d29e50211f7
Split off to make the migration patch smaller
Postgres:
- Make user_touched not nullable
MySQL/SQlite
- Change user_name from varchar to varbinary
- Change user_name from varchar to varbinary
- Drop empty string default from user_touched (Timestamp field)
Bug: T230428
Bug: T164898
Change-Id: I8fe0b1fb2af3149a2e2fdae7bb056ac6f863b09c
This patch was introduced in r1161 (February 2003) but it wasn't
mentioned in the patch-list.txt and checking git history since initial
version (phase3) didn't return any mention of it since then.
It clearly can't be ran on any modern mediawiki setup.
Change-Id: Ic5a8f0699dd31a181c31582be4958522ce3483b3
There's no reason to keep schema change that's no longer useful.
History is already tracked by git.
Change-Id: Ia8aa0d21ae5f2d799d9a641ebe7b924f56e07ab1
Postgres:
- Change page_namespace from smallint to int
- Change page_random from numeric with arbitrary precision to float
- Make page_touched not nullable
MySQL/SQLite:
- Change datatype of page_title from varchar (with binary collation)
to varbinary(255)
- Drop default empty string from timestamp field of page_touched
Bug: T230428
Bug: T164898
Change-Id: Ibdaf332ea1da309d31d35a6ebbc1b8fefced335e
It was introduced in 1.25 which we don't support direct upgrade from
anymore. Also it has been removed from update.php list and it's not
mentioned anymore.
Bug: T272199
Change-Id: I6daf211baa688ad749a8c37ddd776736e598d316
It was introduced in 1.22 which we don't support direct upgrade from
anymore. Also it has been removed from update.php list and it's not
mentioned anymore.
Bug: T272199
Change-Id: I6cdedf33a9b94931e188177b3975b195ebd32111
It was introduced in 1.18 which we don't support direct upgrade from
anymore. Also it has been removed from update.php list and it's not
mentioned anymore.
Bug: T272199
Change-Id: Ib66e9b7c197727bd87552486d7a8f8619ebb5b30
It was introduced in 1.17 which we don't support direct upgrade from
anymore. Also it has been removed from update.php list and it's not
mentioned anymore.
Bug: T272199
Change-Id: Ia81fc68334c5c63d06d22cfea58eab644e12248d
It was introduced in 1.16 which we don't support direct upgrade from
anymore. Also it has been removed from update.php list and it's not
mentioned anymore.
Bug: T272199
Change-Id: I11083df7f6399b44615f1b4e0b7815680cbc4ff1
One of the last ones left.
For MySQL/Sqlite:
- Dropping default of ar_timestamp, empty string is not a valid
timestamp.
- Changing ar_title from "varchar() binary" to varbinary
for Postgres:
- Set default for ar_namespace and ar_title
- Change datatype of ar_comment_id, ar_actor, ar_namespace
The indexes were fixed separately.
Bug: T230428
Bug: T164898
Bug: T42626
Depends-On: I83cf1cd51ac9cf933c9175cefd6e38a6914f3494
Change-Id: Ic1d13a82b27f7fa39a0f0ea9c5b7b193b007e4ab
It was introduced in 1.13 which we don't support direct upgrade from
anymore. Also it has been removed from update.php list and it's not
mentioned anymore.
Bug: T272199
Change-Id: Ieff17b99c881c2906fb71ebb7b9eac226c399b45
It was introduced in 1.11 which we don't support direct upgrade from
anymore. Also it has been removed from update.php list and it's not
mentioned anymore.
Bug: T272199
Change-Id: I9ca3430fc0b20a4c275d1a2c6e8560baf75daac9
- This script should not be in archives directory, that directory
is for sql patches.
- It fixes upgrading from pre 1.10 to 1.10 while making sure
replication works fine. We don't support upgrading from that version
anymore.
Change-Id: I4ecd7d825be721331d3686ae8ff9190357c4e34f
This patch was introduced in r1151 (2003, No kidding) and was never
wired to update.php and any mention of it was removed from documentation
in r23242 (2007). Since then, you can't find any mention of this file.
It clearly won't run on any modern mediawiki database.
Change-Id: Idb4feec3850e4303e6980ef15888e3c5a61c3484
It was introduced in 1.10 which we don't support direct upgrade from
anymore. Also it has been removed from update.php list and it's not
mentioned anymore.
The other sql file has been removed in I982f9a7018069.
Bug: T272199
Change-Id: Ice40c6962dc558b8370fdbce04e51c0e1ece76ce
It was introduced in 1.9 which we don't support direct upgrade from
anymore. Also it has been removed from update.php list and it's not
mentioned anymore.
Bug: T272199
Change-Id: Ib8a480cb570f16ae65e52912591e1d3f0c44aaf0
It was introduced in 1.6 which we don't support direct upgrade from
anymore. Also it has been removed from update.php list and it's not
mentioned anymore.
Bug: T272199
Change-Id: I71aaa4f282271cc9254257e2f2c7f892121870ad
It was introduced in 1.6 which we don't support direct upgrade from
anymore. Also it has been removed from update.php list and it's not
mentioned anymore.
Bug: T272199
Change-Id: I8d9565fe035faf96033dc207515b8ec21bca9fe6
This was introduced in 1.5 which we don't support direct upgrading
from anymore and it's already removed from wiring of the update.php.
Also removing related sql files as they are not used anywhere anymore.
Bug: T272199
Change-Id: Iffc8d2694113d56c3a97a4b72b29e5a30c6d43d1
This was introduced in r6057 (2004) and got removed from update in r9367
(2005) as it wasn't needed anymore. There's no mention of this file
since then.
Change-Id: I8498291b5ca61578074e3fc1706ab9ce526b3d87
This was introduced in version 1.5 which we don't support upgrading from
anymore and it's already removed from update.php checks.
Also dropping its related maintenance script which is not needed
anymore.
Bug: T272199
Change-Id: I5a755fd04f0e69880f27628fd805f865f4bc86bf
This was introduced in 2005 (1.5) and we don't support upgrade from that
version anymore (also it got removed from update.php runs as well). It's
good to go.
Bug: T272199
Change-Id: I5f7c08fce26ffa1e7b989528b0f450ce610ba744
This file isn't mentioned anywhere in current code nor in the history
of commits (git log -S 'parsercache.sql' didn't bring anything) so I'm
sure it's not wired to any update.php and I'm also sure our ParserCache
table structure is different than what it is outlined in this schema.
Change-Id: Icba19f5e39e08ebbbba9bd7836d3386db081b390
This file was never wired to update.php and it was added as something
you should run when you hit an error and even that check got removed in
r21785 (2007) and since then, there's no mention of this file anywhere.
Change-Id: I63ecadf4196621b5204aa7f14a7ec56d139903b5
This patch was introduced in r1015 (2002, I'm not joking) and was never
wired to update.php and any mention of it was removed from documentation
in r69187 (2010). Since then, you can't find any mention of this file.
It clearly won't run on any modern mediawiki database.
Change-Id: Ib13cbd632599666c769830b4f07d61ead14e6af2
This is a follow up to I237af3558 where datatype of img_timestamp for
MySQL was changed from varbinary(14) to binary(14) as part of
standardizing timestamp fields in MySQL (T42626).
This change does not affect Postgres or Sqlite.
Bug: T42626
Bug: T230428
Change-Id: Ic4bd59736ff82d8bdb60fbac46a89f18257b8292
This patch was marked as obsolete and removed from updater in r9367
(2005) and any mention of it was removed from documentation in r69187
(2010). Since then, you can't find any mention of this file.
Change-Id: I3a45f4661434737fa977c721ba6cf74864984d6a
