Account data

[TheIceman1]

How can i remove account data?

[Castillo]

You can't remove it.

[Tete omar]

Of course you can; by setting the data value to false

bool setAccountData ( account theAccount, string key, string value ) 

E.g:

setAccountData (getPlayerAccount(getPlayerFromName("TheIceman1")) , "theData", false ) 

and according to getAccountData

Returns a string containing the stored data or false if no data was stored under that key.

[TheIceman1]

I fix it already

[Castillo]

Of course you can; by setting the data value to false

bool setAccountData ( account theAccount, string key, string value ) 

E.g:

setAccountData (getPlayerAccount(getPlayerFromName("TheIceman1")) , "theData", false ) 

and according to getAccountData

Returns a string containing the stored data or false if no data was stored under that key.

I know that you can do that, but you can't remove the data, like you can with element data.

[Tete omar]

Hmm, you mean 'theKey'?, or there is no function that removes the data?

[Castillo]

The row on the database, it can't be removed.

[TAPL]

The row on the database, it can't be removed.

You can by setting it to false or nil, i tried before and it was removed but i don't remember which one.

[IIYAMA]

You can set it to nil. But will the account + keyword still remain?

With tables it can't be removed like this.

playerT= {}

playerT[1] = player

playerT[1] = nil

#playerT --1

--playerT={nil} but table.remove(,)

Also when you use key names like this.

playerT={}

playerT[player]={}

playerT[player]=nil

-- #playerT does not work. (not in fake array)

It will probably look like this: playerT={[player1]=true,[player2]=true} and when nil: playerT={[player1]=nil,[player2]=nil}

Tables are another story.... but it makes sense to me, that it works the same only in another scripting language.

[Castillo]

The row on the database, it can't be removed.

You can by setting it to false or nil, i tried before and it was removed but i don't remember which one.

Oh, with false it works, I had tried something like this before, since this was already asked, but it didn't work, maybe I tried with nil.