Граф коммитов

12 Коммитов

Автор SHA1 Сообщение Дата
Vitor Mattos c07251f0c6
Use PHP7.4 property typehinting where possible
Signed-off-by: Vitor Mattos <vitor@php.rio>
2022-04-06 12:43:03 -03:00
Vitor Mattos dc518c46a7
replace execute by executeQuery of QueryBuilder
Signed-off-by: Vitor Mattos <vitor@php.rio>
2021-10-19 08:54:14 -03:00
Joas Schilling 84d42604e6
Run cs:fix
Signed-off-by: Joas Schilling <coding@schilljs.com>
2020-05-12 15:04:42 +02:00
Joas Schilling d4fc586f1a
Bye Spreed, hello Talk!
Signed-off-by: Joas Schilling <coding@schilljs.com>
2019-09-05 14:29:09 +02:00
Joas Schilling 56460baaf2
Strict controllers and migration
Signed-off-by: Joas Schilling <coding@schilljs.com>
2019-02-13 13:38:55 +01:00
Joas Schilling 9374a6ca2f
Also set a token when it is null
Appearantly some rooms had null as a token in the past

Signed-off-by: Joas Schilling <coding@schilljs.com>
2018-01-26 12:20:49 +01:00
Joas Schilling c572bad105
Fix migration type hints
Signed-off-by: Joas Schilling <coding@schilljs.com>
2018-01-26 12:20:48 +01:00
Joas Schilling c10e399d33
Doh
Signed-off-by: Joas Schilling <coding@schilljs.com>
2018-01-12 16:15:01 +01:00
Joas Schilling c2f2cbf838
Allow postgres for update but not < 2.0.0
Actually it's not postgres having the problem, but migrations.
Postgres allows camelCased columns, but they need to be quoted.
They were quoted from the old database.xml file but this does
not work anymore in migrations. But that means it worked on
postgres in the past, it just didn't work in 2.9~ to install
since migrations where merged. So we are reverting the check
for postgres and only allow updating from 2.0.0 or later.

This makes sure that when newly installing the migration code
is not run.

Signed-off-by: Joas Schilling <coding@schilljs.com>
2018-01-12 15:17:45 +01:00
Joas Schilling ce3b4952ea
Fix postgres issue when updating
Postgres could not be used in 12. It installed the tables with wrong names
so we need to ignore it on the update steps. The wrong tables will be
dropped and new tables will be created with further migrations.
But we shouldn't try to migrate data from the old and broken layout.

Signed-off-by: Joas Schilling <coding@schilljs.com>
2018-01-12 13:30:05 +01:00
Joas Schilling 1b13e47672
Fix migration docs and empty methods
Signed-off-by: Joas Schilling <coding@schilljs.com>
2018-01-03 16:39:41 +01:00
Joas Schilling 5f11a47da0
Move old repair steps to migrations
Signed-off-by: Joas Schilling <coding@schilljs.com>
2017-11-02 11:48:30 +01:00