On Fri, Mar 17, 2017 at 9:30 AM, Simon Slavin <slav...@bigfraud.org> wrote:
> On 17 Mar 2017, at 7:49am, Dominique Devienne <ddevie...@gmail.com> wrote:
> > Richard, why is SQLite ignoring an attempt to giving these an explicit name?
> > […]
> >> sqlite> create table t (id constraint u1 unique);
> You are supplying a name for the constraint. But you’re still leaving it
> up to SQLite to create the index it will need. So SQLite gets to choose
> the name for the index. If you want to supply the name yourself you have
> to define the index yourself.
But what prevents SQLite from using the constraint's name, if one is
specified, from using it for the index?
Constraint and index names are in different namespaces, AFAIK, so that seem
entirely possible, and even
desirable in the same "Great journeys begin with a single step" vein to
reduce the schema size in memory,
of the original OP. --DD
sqlite-users mailing list