Skip to content

Add ABI interface for custom index#436

Open
villagedeb wants to merge 1 commit intomainfrom
deb/custom-index/1
Open

Add ABI interface for custom index#436
villagedeb wants to merge 1 commit intomainfrom
deb/custom-index/1

Conversation

@villagedeb
Copy link
Copy Markdown
Member

No description provided.

@villagedeb villagedeb self-assigned this May 6, 2026
#define VEF_INDEX_CAP_REVERSE_SCAN ((vef_index_cap_t)1u << 2)
// Index scan returns results in key order, allowing the optimizer to satisfy
// ORDER BY on the index columns without a separate sort step.
#define VEF_INDEX_CAP_ORDER_BY ((vef_index_cap_t)1u << 3)
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this implied by RANGE_SCAN? I am trying to figure out if these are all completely independent capabilities.

// Opaque index descriptor reference from MySQL/InnoDB
typedef void *vef_index_ref_t;

// Naming convention for function pointer typedefs in this header:
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this only in this header? We should have standardized conventions across headers.

// error_msg - Output: error description on failure
// error_msg_len - length of error message buffer
// Returns false on success, true on error (writes to error_msg).
typedef bool (*vef_type_index_insert_func_t)(
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why vef_type_index as opposed to vef_index_. When to use 'type'?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants