Oracle Database 23ai introduced the VECTOR data type as a first-class citizen for AI and similarity-search workloads. However, Oracle APEX 24.2 (and 26.1) currently has no way to work with VECTOR columns through the standard interface:

1. Object Browser / Table Editor — When creating or modifying a table through the APEX UI, VECTOR is not listed as an available data type. Developers must fall back to SQL Workshop or SQL*Plus to define VECTOR columns.
2. QuickSQL — QuickSQL's shorthand syntax has no directive for VECTOR columns (e.g., something like embedding vec or embedding vector(1536)), making rapid prototyping of AI-enabled schemas impossible from within APEX.

Proposed Enhancement:

• Add VECTOR as a selectable data type in the APEX Table Editor / Object Browser, with configurable dimension count and distance metric (COSINE, DOT, EUCLIDEAN).
• Extend QuickSQL to recognize a vector (or vec) type shorthand, optionally accepting dimension size — e.g., embedding vec(1536) — and generate the correct VECTOR(1536, FLOAT32) DDL.

This would allow APEX developers to build AI-powered applications (RAG pipelines, semantic search, recommendation engines) entirely within the APEX low-code environment, consistent with Oracle's vision of AI-ready databases.