hey dude, how can i get the query time in ms ? is there a good way ?
Use GetGameTimer. Record that before then after the query has completed then subtract the two.
up is anyone has the answer ?
Thanks you my friend !
vSql 1.5.1
- Improve
mysql-async
compatibility - Improve exception log format
- Update MySqlConnector to 0.66.0
Binaries: https://github.com/warxander/vSql/releases/tag/v1.5.1
@Warxander hey man, appreciate your work, I am wondering if you have an implementation that I can use within my C# scripts directly, without using the exported methods?
EDIT: Figured it out, edited your source a little bit to my own needs. If anybody wants to know how, reply to my post I will post it then.
It would be a better idea to make a pull request, what do you think about it?
mysql-asnyc has been updated quite frequently in the past, @Warxander can you do another benchmark? Would be interesting to see if yours still performs better
I understand that but some sync feature actually important like inventory addon account. So is there anyways to convert Sync form to async form it always return a nil value so I donât know what to do with that. Or there is nothing to do with that.
Here is the error that I donât know about it.
Sorry for bad English
Could we get an updated Benchmark ? Thx
You can do it yourself because I was not able to run latest mysql-async
on my machine.
I updated vSql
benchmark results and benchmark itself.
Also, you will need to restart benchmark resource after launching server to start getting viable results.
Okay, will do some test with Mysql-async 3.3.1 to see
Mmh i tried everything, could not get the Benchmark working with MySQL
Maybe they changed interface somehow, idk.
My goal was to replace old MySQL.Async, because I donât trust new one + it didnât support transactions when I needed them.
Got it fixed, on transaction the second arg can not be nil with MySQL it has to be {}, running benchmark now
MySQL.Async 3.1.1
.transaction(ms) [ 96, 96, 97]
.execute (ms) [ 50, 50, 49]
.fetchScalar (ms) [ 51, 50, 51]
.fetchAll (ms) [ 50, 52, 52]
So a big improve, but transaction are still slower than vSql for sure !
( Running on my computer btw, idk if this got an positive or negative impact )
You should also test vSql on your PC for correct comparison.
will do later