[Bad_Bud]

Geez. You weren't kidding when you said "a hell of a lot more code".

[Basic-Master]

good article imo, thanks hawk

[Coksnuss]

Nice Tut...
Too bad dbi is outdated because its alot easier to handle then this ****.

[Hawk552]

Originally Posted by Coksnuss Nice Tut... Too bad dbi is outdated because its alot easier to handle then this ****.

Please, think before you say something. It's roughly the same in the areas they both have support for. The reason SQLx is harder is because it's capable of so much more. If you want to use DBI, go ahead, but I recommend that you don't.

[TheNewt]

Yeh, thanks Hawk, now i actually know some SQL (I wouldn't even went to SQL side of AMXx stuff, but i got drawn to it by this

lol, you don't know SQL, you know how to connect to a SQL server database using the SQL functions in AMXX, but you don't know SQL.
If you knew SQL, you'd know how to connect two seperate databases, to search for an item that has correlations between two different tables. Assuming one table being player XP and the second table being player Class, then the second database could be a seperate server you have. So maybe you want to search for a player on two servers and connect his XP/Class, but I don't think you know how to do that from memory. :O

[Rolnaaba]

Originally Posted by MysticDeath lol, you don't know SQL, you know how to connect to a SQL server database using the SQL functions in AMXX, but you don't know SQL. If you knew SQL, you'd know how to connect two seperate databases, to search for an item that has correlations between two different tables. Assuming one table being player XP and the second table being player Class, then the second database could be a seperate server you have. So maybe you want to search for a player on two servers and connect his XP/Class, but I don't think you know how to do that from memory. :O

I am pretty sure he meant with amxx, and not actuall SQL cut him a break.

FYI hawk your sig's saying is wrapping:

[Hawk552]

Originally Posted by Rolnaaba I am pretty sure he meant with amxx, and not actuall SQL cut him a break. FYI hawk your sig's saying is wrapping:

I know, been too lazy to deal with it.

[Bad_Bud]

Originally Posted by Hawk552 SQLx is harder is because it's capable of so much more.

Or... because it's a logic rapist, because almost every time you read in a value, the threadquery is generally the last thing you do in the function that calls the threadquery, because the code then has to shift over to a handling function for when Amxx recieves the callback, so instead of having:

PHP Code:

Function(LOL)
{
    new Variables
    Variables=Do some SQL in this function
    client_print(LOL,print_chat,"%d",Variables)
} 


You end up with:

PHP Code:

Function(LOL)
{
    New Data[1]
    Data[0]=LOL// :*C
 
    Do some query making[].
    SQL_ThreadQuery(Stuff,"MyCuteHandler","MyQuery",myData,1)
}
 
MyCuteHandler(WTF STUFF HERE)
{
 
    COPY AND PASTED ERROR CHECKS()
 
    if(SQL_MoreResults(Query))
    {
        client_print(Data[0],print_chat,"%d",SQL_ReadResult(Query,0))
    }
} 


For essentially the same thing. That's why SQLx is "harder". It completely rearranges your code and thought process, kind of...

[Hawk552]

You left out the error checking in the first block, because there should always be error checking for SQL. It makes perfect sense IMO, you just can't run a threaded query the way you want it to.

[Drak]

Question. I want to use threaded queries for this. How would I go about accomplishing this? Due to the fact, I need to return the value soon as a player connects. Would I have to make a delayed task, and check a value?

public client_connect(id)
     if(!IsBetaTester(id))
          // Kick them here

bool:IsBetaTester(id)
{
    new AuthID[36],bool:Tester = false
    get_user_authid(id,AuthID,35);
    
    new ErrorCode,Error[128],Handle:g_SqlConnect = SQL_Connect(g_SqlHandle,ErrorCode,Error,127);
    new Handle:Query = SQL_PrepareQuery(g_SqlConnect,"SELECT * FROM BetaTesters WHERE SteamID='%s'",AuthID);
    
    if(!SQL_Execute(Query))
        return false
    
    if(SQL_NumResults(Query) < 1)
        Tester = false
    else
        Tester = true
    
    SQL_FreeHandle(Query);
    
    return Tester
}