Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

cfstoredproc fails with parameters when called by synonym which contains #

Description

When executing procedures via synonyms which contain # Lucee does create a SQL statement without parameters and therefore Oracle responds with the following exception:

PLS-00306: wrong number or types of arguments in call to 'TESTPROC2' ORA-06550

Generated SQL: call BU#.testproc2()

The attached test includes the SQL to generate the package with 2 procedures and a synonym for the package.

Calling the package by normal name succeeds for calls with and without parameters. Calling the package by synonym succeeds for calls without paramaters. Calls by synonym with parameter fail with the above exception.

This is an isolated test case and i could reproduce it on Oracle Express 11. The behaviour for Oracle Enterprise is the same.

The test is build upon the test case of the related bug (LDEV-637).

Related google group post:
https://groups.google.com/forum/#!topic/lucee/UCwt4FFExX8

Any help is appreciated. Thanks in advance!

Environment

Lucee: 5.1.0.34
Driver: Lucee Oracle Extension 12c (version 12.1.0.2)
Oracle: Database version 11 (Enterprise/Express)

Attachments

13
  • 25 Jan 2018, 12:22 am
  • 24 Jan 2018, 05:40 pm
  • 24 Jan 2018, 05:39 pm
  • 24 Jan 2018, 05:07 pm
  • 24 Jan 2018, 04:57 pm
  • 24 Jan 2018, 05:44 am
  • 24 Jan 2018, 03:39 am
  • 23 Jan 2018, 09:40 pm
  • 23 Jan 2018, 09:39 pm
  • 23 Jan 2018, 08:06 pm
  • 23 Jan 2018, 07:58 pm
  • 07 Jan 2017, 07:32 pm

Activity

Show:

Igal Sapir 23 July 2019 at 03:58
Edited

Can users affected by this issue test Lucee 5.3.4.13-SNAPSHOT to ensure that there is no regression? Thank you!

Igal Sapir 21 March 2018 at 21:58

Also patched in 5.2.6.61

Igal Sapir 21 March 2018 at 21:48

My apologies. I have placed the patch in a separate branch because I wanted it tested thoroughly first, and it looks like I never merged it to the main branch.

It is now in 5.2.7.50

Sorry about that.

MartinF 9 March 2018 at 15:33


I don't think, that the https://luceeserver.atlassian.net/browse/LDEV-1147#icft=LDEV-1147 is already merged into the 5.2 branch, see:
https://github.com/lucee/Lucee/compare/5.2...5.2-LDEV1147

Also, I couldn't see any pull request to confirm, that this is already merged.

Searching the repo also didn't show your commit with the fix:
https://github.com/lucee/Lucee/search?q=ldev-1147&type=Commits&utf8=%E2%9C%93

Igal Sapir 26 February 2018 at 16:59

Thank you for confirming that.

As for your previous question, the fix is in `5.2.6.44-SNAPSHOT` - see https://github.com/Lucee/Lucee/commit/55a94162536666dd4fa89f9c1d5f2a249a070dc1

5.2.6.59-RC came after 5.2.6.44 so it should be there. I'm not sure why you're not seeing it?

Any version greater than 5.2.6.43 should have this patch in the 5.2 branch. In the future when we merge branch 5.2 with branch 5.3 it will be available in 5.3.x as well.

Fixed

Details

Assignee

Reporter

Priority

Labels

Fix versions

New Issue warning screen

Before you create a new Issue, please post to the mailing list first https://dev.lucee.org

Once the issue has been verified, one of the Lucee team will ask you to file an issue

Sprint

Affects versions

Created 7 January 2017 at 19:55
Updated 23 July 2019 at 22:43
Resolved 1 February 2018 at 16:31

Flag notifications