Marcin Cieslak sa...@saper.info wrote:
Daniel Kinzler dan...@brightbyte.de wrote:
I'll try to look into this today, but I need to find help from someone
knowledgable about postrtges (and especially about the postgres
updater. it's... different).
Thank you everyone - the working fix is now in
Hello,
I updated one of my wikis today from f2138b1 to
9299bab032a85c1a421436da04a595b79f2b9d6c (git master as I write this) and after
running update.php
I get this:
A database error has occurred. Did you forget to run maintenance/update.php
after upgrading? See:
On 10/10/12 09:02, Marcin Cieslak wrote:
Hello,
I updated one of my wikis today from f2138b1 to
9299bab032a85c1a421436da04a595b79f2b9d6c (git master as I write this) and
after running update.php
I get this:
A database error has occurred. Did you forget to run maintenance/update.php
Platonides platoni...@gmail.com wrote:
On 10/10/12 09:02, Marcin Cieslak wrote:
Hello,
I updated one of my wikis today from f2138b1 to
9299bab032a85c1a421436da04a595b79f2b9d6c (git master as I write this) and
after running update.php
I get this:
A database error has occurred. Did you
On 10.10.2012 11:03, Marcin Cieslak wrote:
Seems the files of maintenance/archives/patch-*content* could need to be
copied to maintenance/postgres/archives
It works for me on mysql, but it is inconsistent in that the db is still
used a varbinary but the description uses an integer.
Yes,
Daniel Kinzler dan...@brightbyte.de wrote:
I'll try to look into this today, but I need to find help from someone
knowledgable about postrtges (and especially about the postgres
updater. it's... different).
Sure, feel free to ask, I will be travelling starting tomorrow
but today we can try to
