Log in

View Full Version : Problem with zone_points.sql and 0.6.1-DR1?


xealblade
06-08-2005, 09:22 PM
When trying to run either Cavedude's or Suedeworthey's 0.6.1-DR1 binaries, everything seems to work fine until it goes to load a zone, which gives the error message in zoneperl:

Error 1 in LoadStaticZonePoints query 'SELECT x,y,z,target_x,target_y,target_z,
target_zone_id,heading,target_heading,number FROM zone_points WHERE zone =
'freportn' order by number' #1054: Unknown column 'target_zone_id' in 'field list'

Looking in zone_points.sql, I see that the table is created as

CREATE TABLE zone_points (
id int(11) NOT NULL auto_increment,
zone char(16) NOT NULL default '',
number tinyint(3) unsigned NOT NULL default '1',
x float NOT NULL default '0',
y float NOT NULL default '0',
z float NOT NULL default '0',
target_x float NOT NULL default '0',
target_y float NOT NULL default '0',
target_z float NOT NULL default '0',
target_heading float NOT NULL default '0',
target_zone char(16) NOT NULL default '',
heading float NOT NULL default '0',
keep_x tinyint(1) NOT NULL default '0',
keep_y tinyint(1) NOT NULL default '0',
zoneinst smallint(5) unsigned default '0',
PRIMARY KEY (id),
UNIQUE KEY NewIndex (number,zone)
) TYPE=MyISAM;


Is it trying to use an older zone_points format or something? Am I going to have to edit the SQL file by hand to fix this problem?
Edit: My zone_points.sql is the latest one from CVS, I peeked into both PEQ's and Cavedude's DBs and noticed the table structure in those is identical to the one from CVS. Could I get away with just inserting that extra column and values for it, or do I need to completely redo the whole table structure to match exactly the order ZonePerl is asking for?

cavedude
06-09-2005, 02:29 AM
On CVS under the utils folder there is a file called 0.6.1-upgrade.sql Run that and it should fix you up. In 0.6.1 target zone IDs were changed from name to number.

xealblade
06-09-2005, 05:46 AM
Doh! Can't believe I forgot to source that in there. Thanks a bunch, Cavedude.