Error in trigger when accessing properties with long names

[cmglezpdev]

Hello.

When I am in a trigger and try to access a property of the NEW object, if this property has a large name, postgres throws an exception telling me that NEW does not have that property. However, if the property has a short name, this is fine.

Example:

For a property with name short_description, postgres throws me the following exception:

Error running SQL: record "new" has no field "short_description"

This error is produced just with accessing to the property. For example NEW.short_description. For names like type, price, and even full_description this doesn't have problems.

[GaryAustin1]

Can you show your table definition? No capital letter, no extra space at end? Does it occur on another column also?
Never heard of a limit on column names in new.

[GaryAustin1]

I can confirm not likely a length issue...

begin
raise log 'long, short = %,%',new.my_very_very_very_very_very_long_name_column, new.id;
return new;
end;

[cmglezpdev]

Sure.

This is my table.

and the trigger

So, when i run a simple update:

---

Now, if i print the id, type, formula in logs:

However, with shop_description and full_description this works fine.
I don't know.

[GaryAustin1]

At the moment I suspecting a space...



That column has an extra space at end.
You could look in the UI and highlight the name.
Or you could try new."price_with_discount "; notice the extra space.

[cmglezpdev]

Indeed. The error was that, it had a whitespace at the end.

Thank you very much!!.

[GaryAustin1]

Hey, could you say how you created the column initially? I thought the dashboard trimmed it now, but could be wrong.

[cmglezpdev]

Yes. I created the table using the dashboard, and apparently it did not remove the spaces. I don't know if it has anything to do with it, but I'm using cli version 1.106.1.

[GaryAustin1]

Current release...
It could have been fixed as your release is over 7 months ago.