[DarthNinja]

No, I mean that there is nothing on the code that would do/have done that. And I know I didn't remove it.

[Lob (UK]

All i can tell you is that i have used the Plugin and the same Database for over 2 years and up until after version 5.0, i never once had to query the database and there were no problems or errors with the existing clients.

I have actually pointed this out previously.

http://forums.alliedmods.net/showpos...&postcount=253

And Sobuno came up with a possible fix a couple of posts later although im not sure if it was ever tested or implimented.

http://forums.alliedmods.net/showpos...&postcount=255


- Lob (UK)

[jameless]

@galadril: Finally got around to installing latest version of site. Just 2 quick things I noticed:

1) On the main page (index.php) I like the new chart, but longer names are overlapping. You can see this on Pulp Fortress Stats

2) When using the pagination you added where you can type in a page number and click go, can you expand that to be 3 characters wide? When you have over 100 pages you can't see exactly what page you are typing in because it gets cut off.

Everything else looks fantastic! Thanks for the hard work guys!

[halbblah]

please integrate multiple Server Support! or: one database for one server. Maybe it's enough to make possible to specify the table names.

[jameless]

This does have multiple server support. Pulp uses 1 database for 2 servers and I am sure others use it for more.

[halbblah]

yes I use 1 database for 6 servers, but I want to seperate them. each server with its own database, respectively table

[jameless]

O i'm sorry you meant for the website portion to support multiple servers. I apologize I read your post wrong.

[Sobuno]

Originally Posted by Lob (UK And Sobuno came up with a possible fix a couple of posts later although im not sure if it was ever tested or implimented.

And like that, I reappear.

Looking at the source code, I do not think my fix was ever implemented. There are probably better ways to fix it too.

The following should fix updating from any version to the newest version when using SQLite (Users who have already updated to version 7.1.2 are out of luck though); users of mySQL do not need to read any further, nothing in this file has changed for them.

The fixes made in here are quite similar to the ones mentioned in the posts you linked, Lob, and as such, they may not be optimal, but they have worked in the past.

As always, my code is untested (Even more so than usual this time, I do not play TF2 any more).

My code is based on the latest version available as of this time (7.1.2). Those who trust me can download the TF2_Stats.smx file and place it in the correct file. Those who do not trust me or who want to check what I changed can download the TF2_Stats.sp file. The changes were all made in the T_CheckDBUptodate2 method.

I'll check back once or twice within the next week and then I'll be gone again

[Sobuno]

I decided to do a search on Google and believe I have now found the cause of the issue.

For the developers:
When altering the tables in SQLite and adding new columns, remember to set their default value.
Example from the latest version:

PHP Code:

ALTER table Player add KW_headtaker INTEGER; 


should be:

PHP Code:

ALTER table Player add KW_headtaker INTEGER DEFAULT 0; 


New files attached, should work for updating from all versions to 7.1.2

[Lob (UK]

Originally Posted by Sobuno I decided to do a search on Google and believe I have now found the cause of the issue. For the developers: When altering the tables in SQLite and adding new columns, remember to set their default value. Example from the latest version: PHP Code: ALTER table Player add KW_headtaker INTEGER;  should be: PHP Code: ALTER table Player add KW_headtaker INTEGER DEFAULT 0;  New files attached, should work for updating from all versions to 7.1.2

Thanks very much Sobuno and very nice of you to Pop back again.

I will test this tomorrow on my test server with my Admins and report back how it went.

- Lob (UK)