Title:
[ANeff] ER for: Array notation to respect query cell data type for simple values
| View in TrackerStatus/Resolution/Reason: To Test//CannotReproduce
Reporter/Name(from Bugbase): Aaron Neff / Aaron Neff ()
Created: 08/06/2017
Components: Database
Versions: 2016
Failure Type: Usability Issue
Found In Build/Fixed In Build: /
Priority/Frequency: Normal /
Locale/System: /
Vote Count: 0
This ER is for array notation to respect query cell data type for simple values.
Issue: Query building/manipulating code must be unnecessarily verbose, in order to ensure a conversion exception is thrown for simple values. It cannot use array notation (even in queryNew(), querySetCell() and queryAddRow()), b/c array notation suppresses conversion exception for simple values.
CF-3000469 requested array notation to match querySetCell(). However, I'd not considered the case of setting complex values. Result: CF-3000469 was not implemented.
New suggestion: Continue to suppress conversion exception for complex values, and allow them to always be set (existing behavior remains). Continue to convert simple values if possible (existing behavior remains). Throw conversion exception for simple values, if conversion fails (new behavior introduced).
Example 1: If myQuery.myColumn's type is numeric, then myQuery.myColumn[1]=true sets 1 into cell (existing behavior remains).
Example 2: If myQuery.myColumn's type is numeric, then myQuery.myColumn[1]="foobar" throws conversion exception (new behavior introduced).
Example 3: If myQuery.myColumn's type is numeric, then myQuery.myColumn[1]={foo="bar"} sets {foo="bar"} into cell (existing behavior remains).
Related tickets: CF-3000469 and CF-3143550.
Attachments:
Comments: