https://bugs.documentfoundation.org/show_bug.cgi?id=144038
Alex Thurgood <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Ever confirmed|0 |1 --- Comment #2 from Alex Thurgood <[email protected]> --- (In reply to Richard Demattio from comment #1) > tested again with > Version: 7.4.2.3 / LibreOffice Community > Build ID: 382eef1f22670f7f4118c8c2dd222ec7ad009daf > CPU threads: 4; OS: Linux 5.15; UI render: default; VCL: gtk3 > Locale: de-AT (en_US.UTF-8); UI: en-US > Calc: threaded > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~+ > > In the following command "oResult = oSQL_Command.executeQuery(stSQL)" > the commas of the "stSql" string are interpreted as separators > and the error message shows, that there are 3 columns, but 5 values I can confirm the conversion to the comma as decimal point, and the corresponding column miscount error from Firebird when executing the macro. However, if I surround the constant values provided in the macro with double-quotes, the conversion still occurs, but at least it doesn't produce a Firebird column mismatch error. Tested on macOS Silicon M1 Ventura Version: 7.4.1.2 / LibreOffice Community aarch64 Build ID: 3c58a8f3a960df8bc8fd77b461821e42c061c5f0 CPU threads: 8; OS: Mac OS X 13.0.1; UI render: default; VCL: osx Locale: fr-FR (fr_FR.UTF-8); UI: fr-FR Calc: threaded I'm not a macro language expert, but does the property "localeSensitive" have anything to do with the introduction of a comma decimal separator into the constructed SQL statement, or does that serve some other purpose ? -- You are receiving this mail because: You are the assignee for the bug.
