quest_globals table - id field

[thepoetwarrior]

I agree that create / delete global is probably bad idea, but would edit on a perminate global be less bad?

For example, I would make 10 perminate globals per char, and just change the value to reflect if its in use, and of course by using date/time stamps to check how much time has passed instead of a global that expires after x seconds.

My big question is, if I re-index the quest_globals table, those primary id that auto increment, would that hurt the server? Or does the server need those ids to not change? If the id really doesn't matter then a re-index might be good thing for every GM to do.

Thanks in advance.

[cavedude]

Originally Posted by thepoetwarrior

I agree that create / delete global is probably bad idea, but would edit on a perminate global be less bad?

For example, I would make 10 perminate globals per char, and just change the value to reflect if its in use, and of course by using date/time stamps to check how much time has passed instead of a global that expires after x seconds.

No, you're still performing a database write every second or however long you have it set. Globals aren't designed to be used the way you are. It's too much strain on the database. You are better off using a function that accesses memory, and doesn't need to hit the hard drive.

Originally Posted by thepoetwarrior

My big question is, if I re-index the quest_globals table, those primary id that auto increment, would that hurt the server? Or does the server need those ids to not change? If the id really doesn't matter then a re-index might be good thing for every GM to do.

Thanks in advance.

Re-indexing the IDs has no affect on server functionality, so it's safe to do. I do it on PEQ every couple of months or so.