Modifying database = potential upgrade problems later?

[horrordvds.com]

If I install a hack that changes the database - either by adding a new table, changing an existing one, or whatever - will that cause problems when upgrading to VB3? I mean, what's going to happen to the new tables that VB3 isn't aware of?

I want to install the Thread Preview Hack on my web site. But I would need to run a php file that changes tables in my database. I don't want to do that if it's going to cause problem with VB3 upgrade later on.

I have no problems implementing the hacks - I've played with scripts for years, but I don't know a lot about the MySQL databases and the upgrade processes. Thanks for any help!

[Erwin]

A few points to remember:

1) 99% of hacks for vB2 will not work for vB3 - different way of coding, different names for variables.

2) Most of the time, additional tables or columns in the db will not matter, unless vB3 uses the SAME name - then there will be conflict.

3) When you upgrade vB2 to vB3, new tables and columns will be used - like I said in (2), unless they have the same name, having those extra tables or columns won't make a difference. Since the hacks won't work straight off, you either redo tha hacks, or remove the unwanted tables or columns.

[NTLDR]

Also make a note of the database changes you make, that way you can allways do the oposite to restore you database to the vB2 default later on.