tracker issue : CF-4199436

select a category, or use search below
(searches all categories and all time range)

[ANeff] ER for: Array notation to respect query cell data type for simple values

| View in Tracker

Status/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.



Hi Adobe, I see this is "ToFix". w00t!!!!!!!!!!! This will reduce a pretty-insane amount of verbose code =D Thanks!!, -Aaron
Comment by Aaron N.
447 | August 22, 2017 08:23:14 AM GMT
Hi Adobe, I _really_ hope this can make it in Aether. So that we can build and populate queries w/ array notation, and have column type respected when inserting simple values. Thanks!, -Aaron
Comment by Aaron N.
448 | March 13, 2018 06:53:38 PM GMT
Adobe? In a release focused on type-preservation, this ticket isn't being implemented yet? You keep adding features we can't use (like adding query rows via array notation) when we actually _rely_ on type being enforced. And preventing us from being able to use new features (like member functions) in cases where type-_casting_ makes the most sense. :/ -Aaron
Comment by Aaron N.
28993 | May 31, 2018 07:20:48 PM GMT