Issues
- ORMEvictEntity does not accept compound primary keysLDEV-2121Michael Offner
- cfajaxproxy does not correctly serialize arraysLDEV-2115Resolved issue: LDEV-2115Pothys - MitrahSoft
- xmlValidate Cannot find the declaration of elementLDEV-2113Resolved issue: LDEV-2113Michael Offner
- cfschedule creates tasks but they do not appear in Lucee AdminLDEV-2112Resolved issue: LDEV-2112Pothys - MitrahSoft
- limit debugging memory usage by total size, not just the total number of requests loggedLDEV-2106
- first POST request after startup results in a 302LDEV-1988Michael Offner
6 of 6
ORMEvictEntity does not accept compound primary keys
Description
Details
Assignee
Michael OffnerMichael OffnerReporter
Samuel W. KnowltonSamuel W. KnowltonLabels
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
Affects versions
Priority
Major
Details
Details
Assignee
Michael Offner
Michael OffnerReporter
Samuel W. Knowlton
Samuel W. KnowltonLabels
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
Affects versions
Priority
MajorCreated 17 December 2018 at 18:16
Updated 19 May 2021 at 11:23
Activity
Pothys - MitrahSoft26 December 2018 at 05:34
I've analysed this ticket & confirmed the issue happened on lucee. I've checked with ACF18 & it returns as expected but lucee allows string only in that argument not the compound keys.
In Adobe CF, you can specify a compound key when calling ORMEvictEntity, e.g.
ORMEvictEntity( "EntityName", { key1 = value1, key2 = value2 } );Lucee throws an error because it expects the second argument to always be a string.