v4.11.1 HUD proglem: "Unknown token encoutered"

[Mr Tiger]

You've had several replies from two different technicians since you created your ticket.

Yes, but no one concerning the main problem. Maybe they are working on it hard. But I don't know.

Please attach a new log with 4.11.1 so that we can take a look at how things stand right now; there was no new log in your last reply.

I attached the new logs in the message sent on May 23, 2014 12:20AM.

[kraada]

We are definitely working on it. Thank you for adding new logs.

[_dave_]

I don't understand the point of the lowercase conversions, It seems entirely superfluous.

Yes, postgresql columns are not case sensitive. but lowercasing all the words does not solve the issue where you have both "cnt_hands_SB" and "cnt_hands_sb" as distinct PT4 columns? lowercasing them both simply makes them have a colliding name in PT4 also, no? So something else must be done, e.g. adding a suffix to one of the names. which on it's own would have prevented postgresql name conflicts and avoided this unfortunate scenario of breaking everyone's work.

[_dave_]

Early reports show 4.11.2 fixes the unknown token errors with coffeehud

[StevenM]

I don't understand the point of the lowercase conversions, It seems entirely superfluous.

Yes, postgresql columns are not case sensitive. but lowercasing all the words does not solve the issue where you have both "cnt_hands_SB" and "cnt_hands_sb" as distinct PT4 columns? lowercasing them both simply makes them have a colliding name in PT4 also, no? So something else must be done, e.g. adding a suffix to one of the names. which on it's own would have prevented postgresql name conflicts and avoided this unfortunate scenario of breaking everyone's work.

You are right, but it would force column renaming instead because we are no longer lowercasing column names, we perform this duplication testing internally to detect potential cache column collisions instead. In 4.11.2 _SB is renamed to _SB_duplicate and a message is presented to the user stating that it needs renamed.

(to be more precise I am not positive is _sb or _SB would be renamed, unsure if its first come first serve or not but that should not matter for our explanation, its really just a behind the scenes issue).

[WhiteRider]

Please update to v4.11.2 if you haven't already - this should resolve the issue.

PT4 Download Page

[js2002]

I will tryout.
Waht was the problem with dublicate columns before 4.11.1?

[WhiteRider]

PostgreSQL columns are all lowercase, so when column names were added to the cache if two had identical names only different by case they clashed when added to the cache.

[js2002]

thx now my HUDs are workling again with 4.11.2 installed.

[majonyjony]

Now my custom stats working!

I think this release change my stats to lowercase, but not.