[Predailien12]

I made a plugin that many servers use same database.

so I had to use SQL_ConnectCustom which is Non-Threaded.
and for the good and not lagging query, I used SQL_TQuery which is Threaded.
but I don't know whether they crash if in different server.
I mean, I wonder SQL_ConnectCustom from A server can crash with SQL_TQuery from B server.

do they crash if in different server??

[Monkeys]

There is no distinguishing between threaded and non-threaded on a database connection. (So both types of queries can happen on one connection, if locked properly)
Only mixing threaded and non-threaded queries unproperly is bad.

[Predailien12]

Originally Posted by Monkeys There is no distinguishing between threaded and non-threaded on a database connection. (So both types of queries can happen on one connection, if locked properly) Only mixing threaded and non-threaded queries unproperly is bad.

then what should I do?

I have to hide mysql password and so on.
But the only SQL_ConnectCustom help me hide it.
And SQL_Query occurs Lags.

what should I do?

[berni]

SQL_ConnectCustom can't hide mysql password, nothing can.

[Predailien12]

Originally Posted by berni SQL_ConnectCustom can't hide mysql password, nothing can.

but I heard that I can hide it if I distribute the only SMX file
and general people can't find it.

[berni]

Then you shouldn't listen to them.
You can get serious problems with the law when you don't give the soure code to people when you give them the compiled plugin. Sourcemod's GPL license says you to.

And they can just open your plugin with a hex editor and get your mysql password, that's why this is a bad idea. It breaks the configurability and it makes no sense anyway.

[Predailien12]

Originally Posted by berni Then you shouldn't listen to them. You can get serious problems with the law when you don't give the soure code to people when you give them the compiled plugin. Sourcemod's GPL license says you to. And they can just open your plugin with a hex editor and get your mysql password, that's why this is a bad idea. It breaks the configurability and it makes no sense anyway.

Um...
I am running a RPG plugin which I made.
What I want to do is to make it public one.
I wanted to make a plugins that everyone can do in every server that uses my plugin so they can play in every server.

but I am afraid of being hacked.
So I want to hide it.

There is another reason, Easy to install it.


And I didn't know that there is a law.

Hmm..

[berni]

Originally Posted by Predailien12 Um... I am running a RPG server which I made. What I want to do is to make it public one. I wanted to make a plugins that everyone can do in every server that uses my plugin so they can play in every server. but I am afraid of being hacked. So I want to hide it. Easy to install it. And I didn't know that there is a law. Hmm..

That's not gonna work... like I said.
People either use their own MySQL Server or no MySQL at all.

Besides MySQL isn't meant to connect to it across the whole planet.
The idea isn't bad, but you can't do that.

[Predailien12]

Originally Posted by berni That's not gonna work... like I said. People either use their own MySQL Server or no MySQL at all. Besides MySQL isn't meant to connect to it across the whole planet. The idea isn't bad, but you can't do that.

you are right.

Maybe I have to abandon this plugin.

[DarkEnergy]

i have distributed plugins with hard coded database connections, since then i have switched to sockets + http.

a database connection is the same no matter how you connect it.
threaded queries removes the lag, but does not mean your results return instantly, it just allows the game to continue without mysql blocking it.
MIXING THREADED AND NON THREADED REQUIRES SQL_LOCKDATABASE
like this

THREADED QUERY
LOCK
NON THREADED QUERY
UNLOCK
THREADED QUERY