MYSQL, saving players data.
#5

Thanks for the answer RealCop!

I made the changes to my gm like you said, and hourly saving of player data is alot less now.

I am using threaded queries (BlueG R20).
But what im worried about is this;
pawn Code:
Run time error 3: "Stack/heap collision (insufficient stack size)"
It happends sometimes, it dosent have any noticable effect in the server thought.
I am using crashdetect plugin, so is it possible to avoid this?

I compile with "-d2 -O1", and get this; Stack/heap size: 16384 bytes; estimated max. usage: unknown, due to recursion

On compile without -d2 it compiles without that message.
Reply


Messages In This Thread
MYSQL, saving players data. - by Richie© - 18.06.2013, 11:55
Re: MYSQL, saving players data. - by Richie© - 19.06.2013, 04:13
Re: MYSQL, saving players data. - by Kindred - 19.06.2013, 04:32
Re: MYSQL, saving players data. - by Scenario - 19.06.2013, 05:06
Re: MYSQL, saving players data. - by Richie© - 19.06.2013, 19:07

Forum Jump:


Users browsing this thread: 1 Guest(s)