Error Mysql _real_query

[henkas]

Hi so im using my old dtabase everything was perfect i used it before no errors, and today after a while i decide to open it on localhost and see whats good but i noticed that console showed these errors i was like wtf is going on why is that?

Gyazo

gyazo.com

How can some tables dissapear if i did nothing iside it or its somekind of glitch or what?

 

[henkas]

bump

 

[henkas]

bump

 

[henkas]

bump

 

[Shadow_]

your database is missing 2 tables, player_misc and player_murders couldn't find them in 0.4 copy or 1.3 that i have so you can find them in you schema file of sql

-- found it by browsing on google
import this

CREATE TABLE `player_misc` (
  `player_id` int(11) NOT NULL,
  `info` blob NOT NULL
) ENGINE=InnoDB DEFAULT CHARSET=latin1;

then go to you database structure and set onlinetime BIGINT11 player_murders issue can be solved by importing this (not sure you gave us the least information possible tho)

CREATE TABLE `player_kills` (
  `player_id` int(11) NOT NULL,
  `date` bigint(20) UNSIGNED NOT NULL DEFAULT '0',
  `target` int(11) NOT NULL,
) ENGINE=InnoDB DEFAULT CHARSET=latin1;

 

[henkas]

your database is missing 2 tables, player_misc and player_murders couldn't find them in 0.4 copy or 1.3 that i have so you can find them in you schema file of sql

-- found it by browsing on google
import this

CREATE TABLE `player_misc` (
  `player_id` int(11) NOT NULL,
  `info` blob NOT NULL
) ENGINE=InnoDB DEFAULT CHARSET=latin1;

then go to you database structure and set onlinetime BIGINT11 player_murders issue can be solved by importing this (not sure you gave us the least information possible tho)

CREATE TABLE `player_kills` (
  `player_id` int(11) NOT NULL,
  `date` bigint(20) UNSIGNED NOT NULL DEFAULT '0',
  `target` int(11) NOT NULL,
) ENGINE=InnoDB DEFAULT CHARSET=latin1;

Fixed biggest part of the errors.

Gyazo

gyazo.com

I didnt gave more information because those erros appeared randomly. Extraded this sql long time ago and now imported on new pc and got it for some reason. For murders im using this system Support to old frags skull system · mattyx14/otxserver@bbdfef2 (https://github.com/mattyx14/otxserver/commit/bbdfef26ad5e39e8d00cfb1118a65ed27a9c53da)
Adding that sql code you gave

CREATE TABLE `player_kills` (
  `player_id` int(11) NOT NULL,
  `date` bigint(20) UNSIGNED NOT NULL DEFAULT '0',
  `target` int(11) NOT NULL,
) ENGINE=InnoDB DEFAULT CHARSET=latin1;

Static analysis:

1 errors were found during analysis.

1. A symbol name was expected! (near ")" at position 146)

SQL query: Copy

CREATE TABLE player_kills ( player_id int(11) NOT NULL, date bigint(20) UNSIGNED NOT NULL DEFAULT '0', target int(11) NOT NULL, ) ENGINE=InnoDB DEFAULT CHARSET=latin1

MySQL said:

#1064 - You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ') ENGINE=InnoDB DEFAULT CHARSET=latin1' at line 5

 

[Shadow_]

my bad forgot to do a little change use that then

CREATE TABLE IF NOT EXISTS `player_murders` (`id` bigint(20) NOT NULL, `player_id` int(11) NOT NULL, `date` bigint(20) NOT NULL) ENGINE=MyISAM DEFAULT CHARSET=utf8;

 

[henkas]

my bad forgot to do a little change use that then

CREATE TABLE IF NOT EXISTS `player_murders` (`id` bigint(20) NOT NULL, `player_id` int(11) NOT NULL, `date` bigint(20) NOT NULL) ENGINE=MyISAM DEFAULT CHARSET=utf8;

Yea fixed it but it looks like it still bugged out with saving. Created a new character and this is what it gives
Havent done this - then go to you database structure and set onlinetime BIGINT11
Because not sure what you mean

Gyazo

gyazo.com

 

[Shadow_]

Yea fixed it but it looks like it still bugged out with saving. Created a new character and this is what it gives

Gyazo

gyazo.com

told you goto your database then goto players and view in structure mode and then edit onlinetime to bigint(20)

 

[henkas]

told you goto your database then goto players and view in structure mode and then edit onlinetime to bigint(20)

Thanks works. Weird that randomly my sql glitched out