Jump to content
  • 0
Sign in to follow this  
Originale

Fully Error item_award

Question

I have my syslog file that fills many towels as its

Feb 27 18:04:49 :: ReturnQuery SELECT id,login,vnum,count,socket0,socket1,socket2,mall,why FROM item_award WHERE taken_time IS NULL and id > 0
Feb 27 18:04:54 :: [     7200] return 0/0/0 async 0/0/0
Feb 27 18:04:54 :: ReturnQuery SELECT id,login,vnum,count,socket0,socket1,socket2,mall,why FROM item_award WHERE taken_time IS NULL and id > 0
Feb 27 18:04:59 :: [     7250] return 0/0/0 async 0/0/0
Feb 27 18:04:59 :: ReturnQuery SELECT id,login,vnum,count,socket0,socket1,socket2,mall,why FROM item_award WHERE taken_time IS NULL and id > 0
Feb 27 18:05:04 :: [     7300] return 0/0/0 async 0/0/0
Feb 27 18:05:04 :: ReturnQuery SELECT id,login,vnum,count,socket0,socket1,socket2,mall,why FROM item_award WHERE taken_time IS NULL and id > 0
Feb 27 18:05:09 :: [     7350] return 0/0/0 async 0/0/0
Feb 27 18:05:09 :: ReturnQuery SELECT id,login,vnum,count,socket0,socket1,socket2,mall,why FROM item_award WHERE taken_time IS NULL and id > 0
Feb 27 18:05:14 :: [     7400] return 0/0/0 async 0/0/0
Feb 27 18:05:14 :: ReturnQuery SELECT id,login,vnum,count,socket0,socket1,socket2,mall,why FROM item_award WHERE taken_time IS NULL and id > 0
Feb 27 18:05:19 :: [     7450] return 0/0/0 async 0/0/0
Feb 27 18:05:19 :: ReturnQuery SELECT id,login,vnum,count,socket0,socket1,socket2,mall,why FROM item_award WHERE taken_time IS NULL and id > 0
Feb 27 18:05:24 :: [     7500] return 0/0/0 async 0/0/0
Feb 27 18:05:24 :: ReturnQuery SELECT id,login,vnum,count,socket0,socket1,socket2,mall,why FROM item_award WHERE taken_time IS NULL and id > 0

it may be due to the new DB "Official" that give .Shogun?

-- ----------------------------
-- Table structure for `item_award`
-- ----------------------------
DROP TABLE IF EXISTS `item_award`;
CREATE TABLE `item_award` (
`id`  int(11) NOT NULL AUTO_INCREMENT ,
`pid`  int(10) UNSIGNED NOT NULL DEFAULT 0 ,
`login`  varchar(30) CHARACTER SET latin1 COLLATE latin1_swedish_ci NOT NULL DEFAULT '' ,
`vnum`  int(6) UNSIGNED NOT NULL DEFAULT 0 ,
`count`  int(10) UNSIGNED NOT NULL DEFAULT 0 ,
`given_time`  datetime NOT NULL DEFAULT '0000-00-00 00:00:00' ,
`taken_time`  datetime NULL DEFAULT NULL ,
`item_id`  int(11) NULL DEFAULT NULL ,
`why`  varchar(128) CHARACTER SET latin1 COLLATE latin1_swedish_ci NULL DEFAULT NULL ,
`socket0`  int(11) NOT NULL DEFAULT 0 ,
`socket1`  int(11) NOT NULL DEFAULT 0 ,
`socket2`  int(11) NOT NULL DEFAULT 0 ,
`mall`  tinyint(1) NOT NULL DEFAULT 0 ,
PRIMARY KEY (`id`)
)
ENGINE=MyISAM
DEFAULT CHARACTER SET=latin1 COLLATE=latin1_swedish_ci
AUTO_INCREMENT=1;
-- ----------------------------
-- Indexes structure for table item_award
-- ----------------------------
CREATE INDEX `pid_idx` ON `item_award`(`pid`) USING BTREE ;
CREATE INDEX `given_time_idx` ON `item_award`(`given_time`) USING BTREE ;
CREATE INDEX `taken_time_idx` ON `item_award`(`taken_time`) USING BTREE ;

I searched a bit and I found that the function

void ItemAwardManager::RequestLoad()
{
	char szQuery[QUERY_MAX_LEN];
	snprintf(szQuery, sizeof(szQuery), "SELECT id,login,vnum,count,socket0,socket1,socket2,mall,why FROM item_award WHERE taken_time IS NULL and id > %d", g_dwLastCachedItemAwardID);
	CDBManager::instance().ReturnQuery(szQuery, QID_ITEM_AWARD_LOAD, 0, NULL);
}

As I look what she squeezes if someone can give me some precision its would be nice

 

Share this post


Link to post

0 answers to this question

Recommended Posts

There have been no answers to this question yet

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  
  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...

Important Information

Terms of Use / Privacy Policy / Guidelines / 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.