Jump to content

Question

Posted

Salut, primesc mai multe erori de tipul: [ERROR] cache_get_field_content_int - invalid datatype

Aveti idee daca pot modifica ceva sa vad si linia? Sunt sute de linii care contin cache_get_field_content_int

1 answer to this question

Recommended Posts

  • 0
Posted (edited)

[ERROR] cache_get_field_content_int - invalid datatype 
Treaba asta se poate referi la faptul ca incerci sa salvezi variabile de tip integer (int) in variabile de tip char (string-uri, sau array-uri)

Ideea e ca syntaxele respective sunt din MYSQL R30, R33 sau  R33-6 etc. Personal iti recomand sa treci pe MYSQL R41-4 (ultima versiune cred).

Poti verifica liniile de cod si sa vezi daca sunt corect scrise in parametrii, dar normal ar trebui sa arate cam asa:

new destination[32];
cache_get_field_content(row_idx, field_name[], destination[]);


respectiv

int dest = cache_get_field_content_int(row_indx, field_name[]);

De asemenea, pentru putina documentatie despre MySQL R33 poti verifica aici https://team.sa-mp.com/wiki/MySQL_R33.html

[EDIT]
In principiu trebuie sa verifici toate liniile in care apare cache_get_field_content_int si sa scoti al 3-lea parametru daca este prezent, care reprezinta connectionHandle-ul cu baza de date.

Adica ceva de genu:

new integer = cache_get_field_content_int(0, "integer", connectionHandle);

trebuie sa fie new integer = cache_get_field_content_int(0, "integer);

Edited by Trippie

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Answer this question...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. For more details you can also review our Terms of Use and Privacy Policy.