`bind_x` issue

EQ2Emulator Development forum.

Moderator: Team Members

Post Reply
User avatar
John Adams
Retired
Posts: 9684
Joined: Thu Jul 26, 2007 6:27 am
EQ2Emu Server: EQ2Emulator Test Center
Characters: John
Location: Arizona
Contact:

`bind_x` issue

Post by John Adams » Thu Jun 25, 2009 11:57 am

LE, recently I've started seeing odd DB Query errors in my console. I don't think it's harmful, because as far as I know, "Binding" is not implemented yet. Just seeing odd things in the DB regarding bind values as well.

Oddly, 2 of my own characters (John and Ugly) have a bind_x value, no one else does... but players online are throwing this error even without me being there.

Code: Select all

DB Query Error #1264: Out of range value adjusted for column 'bind_x' at row 1
Connect to phpMyAdmin for my EQ2Live DB and you can see the odd values I am talking about in character_details, relating to bind or housing values. Just wondering if maybe a struct is off, maybe? Can't think of why these values would be this odd.

Code: Select all

SELECT bind_zone_id, bind_x, bind_y, bind_z, bind_heading, house_zone_id FROM `character_details` ORDER BY bind_zone_id DESC LIMIT 0, 30;

SELECT bind_zone_id, bind_x, bind_y, bind_z, bind_heading, house_zone_id FROM `character_details` ORDER BY bind_x DESC LIMIT 0, 30;
just example queries, showing bind info ordered by desc values so you can see the odd values.

LethalEncounter
Team: Zombie
Posts: 2717
Joined: Wed Jul 25, 2007 10:10 pm

Re: `bind_x` issue

Post by LethalEncounter » Thu Jun 25, 2009 3:14 pm

You can safely ignore them for now. I'll add default values to fix the problem, but basically what I think is happening is that those clients are crashing before they are fully loaded and World is trying to save the bad data to the database.

User avatar
John Adams
Retired
Posts: 9684
Joined: Thu Jul 26, 2007 6:27 am
EQ2Emu Server: EQ2Emulator Test Center
Characters: John
Location: Arizona
Contact:

Re: `bind_x` issue

Post by John Adams » Thu Jun 25, 2009 3:18 pm

Hmm, perhaps. But if you look at the log on Tess, you can see it is happening just randomly, out in the middle of whatever else they are doing. I do not see it surrounded by connects/disconnects, I mean.

Either way, yeah I'll ignore them for now. More importantly was the bogus data I found when investigating bind_x values. But that too is probably no biggie since it's still not being used :)

Post Reply

Who is online

Users browsing this forum: No registered users and 1 guest