On Thu, Sep 4, 2014 at 3:59 AM, Dominique Devienne <ddevie...@gmail.com> wrote: > On Thu, Sep 4, 2014 at 2:04 AM, Nico Williams <n...@cryptonector.com> wrote: > >> [...] but there's a gotcha: SELECT * on a table >> source with computed columns might result in much more work being done >> than the user might have expected. > > If that's a real concern, you can always use the existing HIDDEN keyword to > remove that virtual/computed column from the select-star. --DD
Ah! Good point. Getting computed columns as part of the process of getting indexing on expressions would be very, very good. It would allow having computed columns in PRIMARY KEY and UNIQUE table constraints, for example. Nico -- _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
