Bug 41036

Summary:	LO Base does not allow COALESCE() SQL function to be passed to SQL server
Product:	LibreOffice	Reporter:	Marcin <marszysz>
Component:	Base	Assignee:	Not Assigned <libreoffice-bugs>
Status:	RESOLVED WORKSFORME
Severity:	major	CC:	dr
Priority:	high
Version:	3.4.3 release
Hardware:	All
OS:	All
Whiteboard:
Crash report or crash signature:		Regression By:

Description Marcin 2011-09-20 05:42:05 UTC

When trying to run SQL code (or to open saved query) containing COALESCE function, LO Base displays error message saying "FUNCTION db.COALESCE() does not exist" and refuses to execute the query, regardless of "direct execution" setting. This way it's useless to anyone having such queries in their documents. OpenOffice handles them without problem.

Comment 1 Marcin 2011-09-25 22:58:43 UTC

I discovered that running explicit SELECT COALESCE(NULL, 1) works, but replacing literal NULL for anything else prevents the query from working.
This issue affects both LibreOffice 3.3.4 and 3.4.3 release versions.

Comment 2 Björn Michaelsen 2011-12-23 12:37:28 UTC

[This is an automated message.]
This bug was filed before the changes to Bugzilla on 2011-10-16. Thus it
started right out as NEW without ever being explicitly confirmed. The bug is
changed to state NEEDINFO for this reason. To move this bug from NEEDINFO back
to NEW please check if the bug still persists with the 3.5.0 beta1 or beta2 prereleases.
Details on how to test the 3.5.0 beta1 can be found at:
http://wiki.documentfoundation.org/QA/BugHunting_Session_3.5.0.-1

more detail on this bulk operation: http://nabble.documentfoundation.org/RFC-Operation-Spamzilla-tp3607474p3607474.html

Comment 3 Jochen 2012-07-24 19:45:32 UTC

(In reply to comment #1)
> I discovered that running explicit SELECT COALESCE(NULL, 1) works, but
> replacing literal NULL for anything else prevents the query from working.
> This issue affects both LibreOffice 3.3.4 and 3.4.3 release versions.

Hi Marcin,

are you using LO 3.5?
The last stable version is 3.5.5.
Is bug still in 3.5?

Comment 4 Jochen 2012-08-23 18:34:06 UTC

Hi Marcin:

please feel free to reopen this bug if you find out that the problem still exists with the current stable LibreOffice version and if you can contribute requested additional information due to (especially BugReport Details)!

Set status to "RESOLVED -> WORKSFORME"