0.3.0 -> 0.3.1 Upgrade Script

[GoogleCodeExporter]

I am writing a script that will make the necessary changes (MySQL only,
because there are no 0.3.0 SQLite builds) to the database to upgrade an
existing 0.3.0 install to 0.3.1.

The following changes will be made:
1) Add password field to replies/threads tables
2) Add ban history and report tables.
3) Upgrade bans table

#1 is tied to post deletion.
#2 is tied to more robust banning and post reporting
#3 is also tied to more robust banning

Other DB changes will be added if necessary.

Original issue reported on code.google.com by all.sta...@gmail.com on 8 Dec 2008 at 6:44

[GoogleCodeExporter]

Mostly done now, it just needs testing.

Original comment by all.sta...@gmail.com on 8 Dec 2008 at 9:51

[GoogleCodeExporter]

Original comment by all.sta...@gmail.com on 13 Dec 2008 at 10:45

• Changed state: NeedsVerify

[GoogleCodeExporter]

>>510 And that script does not alter threads|posts id column to make it
auto_increment. Hell, that script can not even work correctly as the javascript 
that
it uses attempts to concatenate a string like "this is my string"$variable IN
JAVASCRIPT... which of course breaks. I would just like to see some control by 
the
group when committing. The upgrade script barfs horribly on upgrading the bans 
table
when it runs across single quotes. The templates also reference a plugin that 
causes
them to fall all over themselves as well, so that plugin has been tossed out 
for the
time being. There was probably another 5 or 6 things that were manually fixed 
on the
fly for the upgrade. All in all, it was not horrible to fix the issues as they 
were
quite minor annoyances, but figuring out what all was broken - and where - is a 
task.

Original comment by TaQS...@gmail.com on 1 Sep 2009 at 5:40

[GoogleCodeExporter]

I fixed the javascript error, and the fact that it was trying to alter the wrong
table in one instance.  I don't know why it would be barfing on quotes, as we're
cleaning it in the DBI.  

However, I don't know why we would need to alter the threads/posts id column to 
make
it auto_increment- it should be doing that by default (check configure.php in 
trunk,
it does it)

Original comment by all.sta...@gmail.com on 13 Nov 2009 at 6:44

[GoogleCodeExporter]

Well anoncp isn't known for having the best administrative team, so it's 
possible
they had something configured wrong, or altered their db by hand (they did this
because they were hacking away at stuff in the trunk before they ever got the 
031
branch) that broke something.  But then again, worse things have happened 
because of
the omission of a single character than this, so shrug.

I'm going to set up a test environment on my new Snow Leopard install this 
weekend
(with XAMPP probably, because I don't think Snow Leopard's apache is up to 
date) and
I'll install 030 and try patching to 031.

Original comment by TaQS...@gmail.com on 13 Nov 2009 at 7:09

[GoogleCodeExporter]

Okay, it LOOKS like it's done, so marking as such.

Original comment by TaQS...@gmail.com on 16 Nov 2009 at 6:23

• Changed state: Fixed