"But look how much space and processing time it would take up" Can you clarify what you mean by "space" ?
The processing time argument I understand. I think this is one of those things that if the database engine doesn't internally support it, it can't really be emulated. Sure would be nice to have INCLUDE columns support (here and in other places). - Deon -----Original Message----- From: sqlite-users [mailto:sqlite-users-boun...@mailinglists.sqlite.org] On Behalf Of Simon Slavin Sent: Wednesday, March 1, 2017 12:57 PM To: SQLite mailing list <sqlite-users@mailinglists.sqlite.org> Subject: Re: [sqlite] Non-unique columns in unique index On 1 Mar 2017, at 8:21pm, David Raymond <david.raym...@tomtom.com> wrote: > The trigger version you asked about would look something like the below I > believe. More risky than having the two indexes, but should work. (Famous > last words) I have no doubt it would work. But look how much space and processing time it would take up. Far simpler and clearer just to create the two indexes. Simon. _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
