Hi & welcome! I’m really not sure, but from looking in the docs I understand that creating the DECIMAL SQL type usually also expects further parameters. If not set it will fall back to default with a scale=0. I’m still wondering how/if such parameters (e.g. also varchar(5) or decimal(4,2)) can be passed to the queryNew() function. So if you define DECIMAL without further parameters I think 6 would be what to expect. However, FLOAT works, but according to the docs that would not be as precise as using a DECIMAL with the correct paramaters.
hmm, curly one, the problem is that we don’t have the scale information for a decimal column, especially when created with queryNew, so when the column is created in hsqldb due to the join, it’s being created a a double with no precision, hence the rounding
So I guess Lucee 184.108.40.206 used an older version of HSQLDB that somehow managed to retain the precision of the decimal value from the queryNew decimal type column? It would be a shame to lose that magic, however it was done.
Newbie question. My servers do not have access to the internet so updates must be applied manually. When updating from minor versions, like 220.127.116.11 to 18.104.22.168, is it still done by adding the snapshot.jar file to the patches folder? Is it the same for a 5.4 release to a 5.5 release? What about from 5.4 to 6.0? Or should major versions be a completely fresh install?
Windows Server with IIS. My original installation was from the 22.214.171.124 windows executable file if that matters.
I actually wanted to update our productive server to 126.96.36.199 next week. However, since our billing system uses a lot of QoQs, in the worst case all billings might have been incorrect. That would be a major disaster.
To be on the safe side, I will now test everything extensively myself before I update to 188.8.131.52.