Updated EQITEMS and BOTS editor

[GeorgeS]

I am still trying to fix the issue.

Regarding error "Old Edit gives 'Run time error '9' Subscript out of range' for any item."

This was fixed today. Field# exceeded variable declaration.

Now regarding the other more serious error. So we know that 'new edit' copy works fine, but fails if you save the copied item ~ around where it updates the "range" field.

Can you verify this assumption below?
if you save an original (not copied) item in new edit with no changes -- it works ok? but fails when saving the copied one?

BTW - I loaded in the latest schema and could not reproduce the error. Could be my version of mysql (mysql-5.0.77) that may be causing this, but still there has to be a reason why a simple query like UPDATE items SET range="0" WHERE id='1079' (it fails here everytime?)
fails???

This is weird and a real brain twister..
I'm on it and I'll let you know when I'm done

GeorgeS

[nosfentora]

Just tested now with a newly downloaded copy of eqitems (14.4.13) and newly installed OBDC drivers (3.51) to make sure i was up to date.

DB is still PEQ 946

It failed on saving an un-edited (non-copy) item, failed on saving an edited (non-copy) item, saving an un-edited copy, and saving an edited copy. (this time i tried on id 47344 (Abhorrent Brimestone of Charring)

could it be that MySQL 5.1.37 has something new that doesn't like that query?

Using NaviCat 8.2.11 i ran the query:
update items set range=0 where id=47344

it failed

"[SQL] update items set range=0 where id=47344

[Err] 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 'range=0 where id=47344' at line 1"

[GeorgeS]

ok so it looks like what appears to be simple sql fails. Can you try and see which of these work?

UPDATE items SET range="0" WHERE id='1079' 
UPDATE items SET range='0' WHERE id='1079'

One thing I can tell is that by the time range fails, many other fields using this query work, so it could boil down to the field struct - or something similar

Later
GeorgeS

[nosfentora]

Same error - i did try those variations before posting, should have posted that too =)

[nosfentora]

Dropped system and re-sourced Rev 946, still getting the same errors.

Something must have changed between 5.0.77 and 5.1.37 ... but why would updating a field (that particular one) fail?

is 'range' now a reserved word?

[nosfentora]

according to navicat, range is a reserved word (highlights blue like set, update, insert, etc)

update items set `range`=0 where id=1079

worked.