[11.3.279 Pro] - BUG: Formatting operators (PostgreSQL)

[11.3.279 Pro] - BUG: Formatting operators (PostgreSQL)

Similarly to the assignment operator ( := ) in MariaDB (see here), the two parts of the "->" operator in PostgreSQL get "divorced" after formatting.

I'm quoting this here, for my intention was only to refer to that topic, not to continue it as that issue with the := operator no longer manifests on MariaDB, and for that matter, it isn't present on PostgreSQL either, which has the same assignment operator.

	SysOp wrote:
	We have tried it on multiple test systems and still unable to reproduce it. The team says they cannot fix it as they don't know what's wrong with it, and unable to debug it, not being able to reproduce the same result with MariaDB. I'm now asking them to try with PostgreSQL and -> operators.

Would it help if the team had access to my sqlassist.sas file? Perhaps it's something with my settings that causes this issue? Though I'm pretty new to Postgres so my tinkering with related settings is kept to the minimum (so far, at least :).

It certainly would. Thank you. It would help with reproducing your setup. Could you please send settings export file to supportATsofttreetech.com. In the export options you can unselect database connections to avoid sharing sensitive data.

Thank you very much for the provided config file. We managed to reproduce the issue with PostgreSQL, but not yet with MariaDB
With PostgreSQL it impacts -> and ->>, we are still investigating the root cause. Hopefully will will succeed with reproducing MariaDB case too.

Er... You might have missed in my post above that I no longer experience the issue of the := operator cracking apart so trying to reproduce that might lead to a wild goose chase. Whether if it was you making some changes having this fixed as a side-effect, or it was me doing something, I don't know, I don't even remember when it vanished.

With that said, the null-safe equal operator <=> in MariaDB does indeed suffer the same fate after formatting. Less than and equal stays together, greater than goes to the right, and it becomes:

	Code:
	<= >

Thank you for the additional clarifications. Yes, we have been still chasing the illusive =>
I will let them know about <=>. And thanks for the tip, I learned something new today, I have't heard of the null-safe operator before.

Fixed as well.