[Nextra]

Originally Posted by Bugsy The overhead for SQL isn't always necessary for basic data storage. nVault also does not require the knowledge of how to write queries. nVault provides a very basic and easy to understand means of saving\retrieving data to an external file.

This is why I said I'm going to stick with SQL, since I know how to query it is not a problem for me . It's definitely a helpful and nice tutorial for everyone else but as long as it is not extremely incomplex, temporary or limited data that has to be stored I will always use SQL.

Question: I have a bad opinion about vaults ever since my old WC3 Server suffered from a huge XP-database and crashed on every mapchange. Is this still possible with nVault?

[Bugsy]

Originally Posted by Nextra This is why I said I'm going to stick with SQL, since I know how to query it is not a problem for me . It's definitely a helpful and nice tutorial for everyone else but as long as it is not extremely incomplex, temporary or limited data that has to be stored I will always use SQL. Question: I have a bad opinion about vaults ever since my old WC3 Server suffered from a huge XP-database and crashed on every mapchange. Is this still possible with nVault?

Even if querying isn't a problem for you it could still be overkill depending on what you are storing. If you are only storing a single item and only need to retrieve it based on a single key then it is a waste of CPU to use SQL. Whatever floats your boat though.

I've never had any issues with nVault. I have used it for all of my data saving needs.

[Nextra]

Originally Posted by Bugsy Even if querying isn't a problem for you it could still be overkill depending on what you are storing. If you are only storing a single item and only need to retrieve it based on a single key then it is a waste of CPU to use SQL. Whatever floats your boat though.

Of course. As I said: If it's uncomplex or temporary data I wouldn't bother doing a SQL-implementation.

[Bugsy]

Thanks Exolent for catching the typo. +k

[ish12321]

Is it possible to have 2 entries with same key ?

[Exolent[jNr]]

Good job! I always wanted to know how to use the prune function.

PHP Code:

public cmdSaveScore(id)
{
    //Save 2 items into the value of the entry.
    //Example: STEAM_0:0:1234 15 5

    new szData[8];
    new szKey[40];
    formatex( szKey , 39 , "%sMONEY" , g_szAuthID[id] );
    formatex( szData , 7 , "%d %d" , get_user_kills(id) , get_user_deaths(id) );

    nvault_set( g_Vault , szKey , szData );

    client_print( id , print_chat , "* Your score was saved to vault." );
}

public cmdGetScore(id)
{
    //Read 2 items that that are saved in the same entry
    //Example: STEAM_0:0:1234 15 5

    new szData[8];
    new szKey[40];
    formatex( szKey , 39 , "%sMONEY" , g_szAuthID[id] );

    if ( nvault_get( g_Vault , szKey , szData , 7 ) )
    {
        new iSpacePos = contain( szData , " " );
        new szKills[4];
        new szDeaths[4];
        
        if ( iSpacePos > -1 )
        {    
            formatex( szKills , iSpacePos , "%s" , szData );
            formatex( szDeaths , 3 , "%s" , szData[ iSpacePos + 1 ] );

            set_user_kills( id , str_to_num( szKills );
            set_user_deaths( id , str_to_num( szDeaths );

            client_print( id , print_chat , "* Your score was loaded: %s kills, %s deaths" , szKills , szDeaths );
        }
    }
    else
    {
        client_print( id , print_chat , "* You have no score entry in vault." );
    }
} 


Don't you mean:

PHP Code:

formatex( szKey , 39 , "%sSCORE" , g_szAuthID[id] ); 


[Bugsy]

Made corrections to example plugin. There were a few minor typo's and added required modules to make it compile via copy and paste.

[Dygear]

If you could add a function to return just the timestamp for a vault key that would be great.

nvault_timestamp(vault, key[]); // Finds when the item was last touched.

Also, it would be awesome it we could write as to the save to the vault in the same data type that it was intended to be in.

[Exolent[jNr]]

stock nvault_timestamp(const vault, const key[]) {
    static data[2], timestamp;
    return nvault_lookup(vault, key, data, charsmax(data), timestamp) ? timestamp : 0;
}

[r4ndomz]

Thanks for the tut!