Either spawn a bot on initialise or cache bans from the last time they were loaded.
Either spawn a bot on initialise or cache bans from the last time they were loaded.
And i am pretty sure atm the player is connecting the module will allready start behaving normally again.
Does this module keep database connections over map restarts? I mean, if I restart the map frequently will I end up with 500 open MySQL connections?
Well it's working perfectly now, thanks for your help. :3:
Well, after testing a few things for the past hour, I've come to the conclusion that it's not onConnected causing the crash. It's something else causing it. I was led to believe so because of the way I load a few modules of my own. Whoops
I have a problem,
It doesn't call my callbacks. It executes the query but doesn't call my callbacks.
They always worked and now I moved then to seperate files and they stopped working.
It shoudn't be a problem that the callbacks and main function are in a huge table right? (like the Ulib way)
Which is why when the Gamemode is shutting down, you want to set the connections to nil to terminate them. Some hosters have a limit as to how many connections can be used at any one time.
I'm getting an error when trying to load the module
What can i do? I copied the dir to addons and when that didn't work i copied the contents of the dir to gmod/gmodCode:error loading module 'mysqloo' from file 'f:\games\steam2\steamapps\steamname\garrysmod\garrysmod\lua\includes\modules\gmsv_mysqloo.dll': The specified module could not be found.
require("mysqloo") gives the error above :(
The file garrysmod\garrysmod\lua\includes\modules\gmsv_mysq loo.dll does exist
Screenshot of where they're installed to with the directory please.
atCode:1>------ Build started: Project: LuaOO, Configuration: Release Win32 ------ 1>Build started 03.04.2011 10:20:25. 1>InitializeBuildStatus: 1> Creating "output\Release\Win32\obj\LuaOO.unsuccessfulbuild" because "AlwaysCreate" was specified. 1>ClCompile: 1> All outputs are up-to-date. 1>Lib: 1> All outputs are up-to-date. 1> LuaOO.vcxproj -> F:\Dev\VC++\GMod\LuaOO\output\Release\Win32\LuaOO.lib 1>FinalizeBuildStatus: 1> Deleting file "output\Release\Win32\obj\LuaOO.unsuccessfulbuild". 1> Touching "output\Release\Win32\obj\LuaOO.lastbuildstate". 1> 1>Build succeeded. 1> 1>Time Elapsed 00:00:00.03 2>------ Build started: Project: MySqlOO, Configuration: Release Win32 ------ 2>Build started 03.04.2011 10:20:25. 2>InitializeBuildStatus: 2> Touching "output\Release\Win32\obj\MySqlOO.unsuccessfulbuild". 2>ClCompile: 2> All outputs are up-to-date. 2>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\Microsoft.CppBuild.targets(990,5): warning MSB8012: TargetPath(F:\Dev\VC++\GMod\MySqlOO\output\Release\Win32\MySqlOO.dll) does not match the Linker's OutputFile property value (F:\Dev\VC++\GMod\MySqlOO\output\Release\Win32\gm_mysqloo.dll). This may cause your project to build incorrectly. To correct this, please make sure that $(OutDir), $(TargetName) and $(TargetExt) property values match the value specified in %(Link.OutputFile). 2>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\Microsoft.CppBuild.targets(992,5): warning MSB8012: TargetName(MySqlOO) does not match the Linker's OutputFile property value (gm_mysqloo). This may cause your project to build incorrectly. To correct this, please make sure that $(OutDir), $(TargetName) and $(TargetExt) property values match the value specified in %(Link.OutputFile). 2>Link: 2> LuaOO.lib(CLASS_LuaObjectBase.obj) : MSIL .netmodule or module compiled with /GL found; restarting link with /LTCG; add /LTCG to the link command line to improve linker performance 2> Creating library output\Release\Win32\gm_oomysql.lib and object output\Release\Win32\gm_oomysql.exp 2> Generating code 2> Finished generating code 2> MySqlOO.vcxproj -> F:\Dev\VC++\GMod\MySqlOO\output\Release\Win32\MySqlOO.dll 2>FinalizeBuildStatus: 2> Deleting file "output\Release\Win32\obj\MySqlOO.unsuccessfulbuild". 2> Touching "output\Release\Win32\obj\MySqlOO.lastbuildstate". 2> 2>Build succeeded. 2> 2>Time Elapsed 00:00:01.22 ========== Build: 2 succeeded, 0 failed, 1 up-to-date, 0 skipped ==========
there is gm_mysqloo.dll
there is the libmysql.dll that came with the connector i linked against
the same file is also at garrysmod/garrysmod/bin
Code:] lua_run require("mysqloo") > require("mysqloo")... error loading module 'mysqloo' from file 'f:\games\steam2\steamapps\steamname\garrysmod\garrysmod\addons\mysqloo\lua\includes\modules\gm_mysqloo.dll': The specified module could not be found.
You also have to extract the sv_ and cl_ mysqloo modules and put them directly into the lua/includes/modules folders.
The module itself can stay in the addon format, it was just the libmysql that didn't work in the addon
Thanks for the help :)
I'm now having a very different problem, when i insert data, the data is saved but it takes ages until the onSuccess callback of the query is called
Edit: ages = sometimes more than a minute, when using query:wait( ) the callbacks get called almost instantly. Is anyone else experiencing this?
Hmm this is odd..
Also see .. : http://www.facepunch.com/threads/1077170-Mysqloo-Error
Resolved - a person or a bot must be in the server for queries to run.
If you don't have anything useful to contribute, don't post. There are several advantages of using either module, and I haven't seen you give one reason why someone should use tmysql instead of mysqloo. You only ever say this one sucks and not to use it.
If you have any factual reason why they should, then I'm sure we would all love to hear it. Otherwise, no one cares about your opinon, so kindly stop trolling/baiting/being-a-retard or whatever you care to call it.
I understand with mysqloo you can connect to multiple databases, but seriously one per addon is fine, you don't need more than one database per addon, thats just a plain waste of space.
Reasons why I prefer tmysql over mysqloo: has not crashed ONCE, multithreading (never EVER causes lag on my server(s)), much faster, more reliable, easier to script, easier to understand.
There, you see, those are reasons. You had a bad experience, and you prefer tmysql because it solved your problems where mysqloo didn't. That's wonderful.
However, when someone has a problem with this module, the first reaction shouldn't be "its borked, dump it". I have been using mysqloo on all my servers, without the slightest bit of issues. I am running linux and windows. Clearly, unless you are doing something drastically different, and much more demanding than me, the errors are user errors, not a fault of the module.
Again, if you prefer tmysql, that's perfectly fine; but, don't push your opinion on others. You can offer them the option, and give your reasons why you use it, but the attitude of "this sucks don't use it" gets rather irksome after a time.
As for not having any update in a while, what does that have to do with anything? The module isn't broken, and unless you have some fantastic feature you want added, it doesn't need to be updated. One could argue that frequent are a sign of an incomplete or buggy system, over a stable, functional one that doesn't need constant maintenance.
Again, I'm thrilled you've had success using tmysql, and am sorry you had a bad experience with mysqloo, but please don't shove your opinions on other without reasons, as you have been known to do quite frequently.
Out of curiosity, what exactly were you trying to do when you ran into trouble with this module? Again, I've been using it on both platforms for a while, without any sort of lag or errors, and I abuse this module to death.
Take a look here: http://www.facepunch.com/threads/933...1#post28312756
It was even me that tried to help you, and you shrugged it off as "a problem with my dedi."
I don't have any issues with you suggesting tmysql to people. I have an issue with people having a tiny, easily correctable error, and you instantly telling them to drop what they are doing and switch modules instead of trying to help. It's not helpful.
You need the vs2008 redistributable maybe?
Seth could possibly be onto something, thanks seth.
Popping it out of my ass? You never gave a specific error, only that it failed to require. The most likely case is that you installed it incorrectly. If you were to give an actual error, other than "hurrr it doesn't work", then we might be able to help you out.
Can you show us a directory map of where you put everything?
Otherwise it's down to personal choice.
Mhm, I moved from tmysql to mysqloo for that exact reason (multiple databases).