Hi,

i'm working on a new addon "Assessment" showing statistics of boss fights. I wrote some classes for the data model and a update_hook.php.
Well the amount of SQL querys i so hugh that the sql debug infos exceed the memory limit of the php default 32M. After doing a ini_set('memory_limit', '64M') everything was fine.

Now my two questions.

Does ini_set always work, or will there be problems if another value is set by php.ini?

As i can see the sql log data is kept always and just the output is done if sql debug is enabled.

Is it possible to change that in a way that sql log data is only kept if sql debug is enabled?

No, ini_set will most defiantly not work in all cases

I thought the sql only logs during debug but it logs all the time
I will change it so it only logs in debug mode

Be carefull here.

I checked in 'my country' with the 3 major web-suplliers.

Your ini_set('memory_limit', '64M') is a no go.
All of them (1&1, ovh.net and amen - 75 % market share in France) give you 32M max. You can change this only if you take a dedicated/virtual server - but is is a 10 € or more a month....
This is worth it, but for people running a WoW clan - and going mad when they have to rent their 75 € a half year TS server - it will be far tou much.

I can raise the mem limit easly, that is, on my home web server - but this means a dedicated PC - not many are will to pay that price tag neither.

And the situtaion that putting on "SQL logging" will crashed the server is rather dangerous - your addon can never be delivered in beta form :-)

Just my 2 cents

PS : note that a 120 guild sync with Armory Sync already shows CPU graphs in the red zone....

Hmm, all right. The problem only occurs on lua upload. Right now i don't have any output. But i think that there will be a lot smaller memory usage than the data import.

BTW: I think this problem will come up with every addon that depends on large lua files, like RaidTracker.

Will a "Don't turn on SQL Debug on data imports" mean that i can't publish it during roster beta or can we get some solution for that?

During the RC phase of 2.0, the debug will be on by default, but will be able to be turned off