Adam Cameron
IFNULL in QoQ with data from a MySQL DB. Cannot tie down what the actual issue is yet, but am getting there is a problem to execute sql statement on query (nice English, btw) and incompatible data type in operation as the detail.
The columns in question are both varchar(100) in the DB. And in the dataset I'm seeing it on, there are no nulls, or anything else quirky about the data.
I will look more into it a bit later, just thought I'd let you know.
This is a show stopper for us upgrading to 5.4.
TBC...Rodney
06/22/2023, 12:24 PMIFNULL is MySQL specific so I wouldn't expect it to work in a QoQ, just as I wouldn't expect ISNULL for MS SQL to work. Have you tried COALESCE which is more universal?Rodney
06/22/2023, 12:53 PMIFNULL, ISNULL, and COALESCE all worked for me in a QoQ using 5.4.0.80. The original query was from MS SQL since I don't have access to a MySQL server at the moment but that really shouldn't matter.zackster
06/22/2023, 1:27 PMzackster
06/22/2023, 1:27 PMbdw429s
06/22/2023, 1:32 PMbdw429s
06/22/2023, 1:32 PMAdam Cameron
ISNULL as a work around.
NB: this all works fine on 5.3.x, and has for quite some time.Adam Cameron
Adam Cameron
Adam Cameron
Adam Cameron
Adam Cameron
bdw429s
06/22/2023, 1:35 PMbdw429s
06/22/2023, 1:35 PMbdw429s
06/22/2023, 1:36 PMAdam Cameron
Andreas
06/22/2023, 3:01 PMAdam Cameron
Andreas
06/22/2023, 3:54 PMAdam Cameron
zackster
06/22/2023, 4:04 PMAdam Cameron
COALESCE works. This works around it for me, but... there's still a regression there.
I've not been able to isolate it from our app for a repro case yet