Unexpected YEAR..

Okay, I was tempted into upgrading to 6.3.0 possibly before I should have just stopped and READ the CHANGELOG!.. PATIENCE, it is said, IS A VIRTUE! … now can’t rebuild index (among other things) and am seeing… unexpected YEAR near ‘year asc’ … I imagine this is a CCTZ library thing, where year suddenly became a reserved word.

Well, I can alias it as something else, but “year” is a pretty useful column name, if you know what I’m saying.

Can year still be used as a column?

Any/all help… greatly appreciated.

Okay, just noticed this…

ERROR: table ‘foo’: year is not a valid attribute name.

let me see what I can do.

year(date) as year should work. I will probably leave this here, in case anyone else runs into it.

…also noticed explicit declaration of id as:

# sql_attr_uint = id

is now an error… so, I just commented all of those out.

No real need to reply, unless you need a clarification.

Thank you everyone, for all your fine work!

Hi @manx

Thanks for this topic.

Can year still be used as a column?

FYI the related task is Escaping does not work with reserved keywords · Issue #1827 · manticoresoftware/manticoresearch · GitHub