[BAILOPAN]

Yes, that will indeed still happen because it is not multithreading.

Maybe in the future I can make a multithreading version of it

[Geesu]

Someone started a multithreading version of it. I got the source from him a while back. I think it was Scott Beaman (thats in the source files..) I can send it to you if you like and you can take a peak.

[BAILOPAN]

sure... bailopan [at] amxmodx [dot] org

[Geesu]

lol, just PMed it to ya.. i'll email it

[_KaszpiR_]

Bailopan - i know enough the mysql an oracle and i can say the differences (as you probably know) are not only in the functuion calls - i would also recommend the adding var /define statement to determine what sql system is used, so that different sql queries could be used on specifiled platforms

also i imagine there will be a big welcome from mssql

[Bionic]

i remember trying a plugin called mthread by DJeyl. it could execute a command in a separate thread f.i sql-queries, thus not freezing up the server

[_KaszpiR_]

yes, but it was buggy, the dev team says they may rewrite it (afair)

[DopeFish]

yeah, certain problems arose when heavily multithreading stuff in a non multithreading enviroment (hlds)

[BAILOPAN]

Sometime in the future I will write mthreading versions of each database driver we put out, that way the problems will be contained in the module and won't be suspectible to the problems of global multithreading which plugin authors do not know how to handle well.

As for other database driver properties, yes, I am planning an Ms-SQL driver (as I happen to like MS-SQL). However, beyond the basic dbi_connect and dbi_query, I don't have anything planned unless someone contributes code. I don't think anything else is really necessary unless you are planning TRANSACT support (which should be already there with dbi_query).

[_KaszpiR_]

i guess the same functions as are implemented in mysql version are enough