MySQL Error showing up on GM screen

[demonstar55]

The changelog.txt is in the root folder of the repo, if you are building it yourself, you should see it ...

[Riklin]

Thanks for that info about changelog. I found it and will diligently use it for now on!.

In trying to figure out the error itself...

SELECT
c.id,c.name,c.class,c.level,c.timelaston,c.zoneid,
g.guild_id,g.rank,g.tribute_enable,g.total_tribute ,g.last_tribute,g.banker,g.public_note,g.alt
FROM vwBotCharacterMobs AS c LEFT JOIN vwGuildMembers as g ON c.id=g.char_id
AND c.mobtype = b.mobtype WHERE g.guild_id=1

This is looking for c.timelaston. There indeed is no column in vwBOTCharacterMobs called "timelaston". There is a column called "last_login" which appears to be the same thing.

I have a version of the database which is empty, created from the 9/25/2014 peq database. It has been appropriately patched. That version also has this error and the bot views appear to be set up identically. I suspect this is a code issue somewhere. I'll continue to look at it. Maybe I'll get lucky and stumble on the code somewhere... LOL!

Riklin

[Riklin]

This query works correctly... I believe this is what the query should be.

SELECT
c.id,c.name,c.class,c.level,c.last_login,c.zone_id ,
g.guild_id,g.rank,g.tribute_enable,g.total_tribute ,g.last_tribute,g.banker,g.public_note,g.alt
FROM vwBotCharacterMobs AS c LEFT JOIN vwGuildMembers as g ON c.id=g.char_id
AND c.mobtype = g.mobtype WHERE g.guild_id=1


Now to figure out where it goes...

Riklin

[Riklin]

This query is a bit more dynamic than I thought. The guild ID value changes, so I suspect this is a resulting query from some sql assembler process.

[demonstar55]

Originally Posted by Riklin

Thanks for that info about changelog. I found it and will diligently use it for now on!.

Make sure you read the commit messages, some of us like to be lazy and piss akka off.

[dagulus2]

Originally Posted by Riklin

This is looking for c.timelaston. There indeed is no column in vwBOTCharacterMobs called "timelaston". There is a column called "last_login" which appears to be the same thing.

I have a version of the database which is empty, created from the 9/25/2014 peq database. It has been appropriately patched. That version also has this error and the bot views appear to be set up identically. I suspect this is a code issue somewhere. I'll continue to look at it. Maybe I'll get lucky and stumble on the code somewhere... LOL!

Riklin

My PEQ Database does have a timelaston column is vwBOTCHaracterMobs, so one of us is not up to date.