All work
- ORMEvictEntity does not accept compound primary keysLDEV-2121Michael Offner
- ORMEvictEntity Cannot Find Entities When datasource attribute is specified (multiple datasources)LDEV-2092Michael Offner
- ORMEvictEntity throws Unknown Entity for All EntitiesLDEV-1984Resolved issue: LDEV-1984Michael Offner
- CFML Based functions and tags missing from docsLD-39
4 of 4
ORMEvictEntity does not accept compound primary keys
Description
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 - MitrahSoft 26 December 2018 at 05:34
Pothys - MitrahSoft
26 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.