Skip to content

Do not flatten the index 'Options', keep them as in payloads/responses #104

@sl-at-ibm

Description

@sl-at-ibm

The Table*IndexDefinition classes currently do some (subclass-dependent) work to push and pull individual options to/from the Options dictionary to maintain the correct (nested) payloads/responses while presenting a flattened API to the calling code.

For example, TableIndexDefinition exposes Ascii, Normalize and CaseSensitive as root-level attributes, at the expense of laboriously storing them into, and retrieving them from, its Options.

This should be replaced by a true-to-the-data-api-structure arrangement.

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions