And another option of course is to store all those extra columns as JSON, which you can query with the JSON1 extension. You can even index on the extracted values.
On Sat, 17 Jun 2017, 9:53 AM Wout Mertens, <[email protected]> wrote: > Could you not combine the data on the app side? > > On Sat, 17 Jun 2017, 9:15 AM J Decker, <[email protected]> wrote: > >> Probably need to use some CTE expressions to tackle that. >> >> https://sqlite.org/lang_with.html >> >> On Fri, Jun 16, 2017 at 10:59 PM, Robert M. Münch < >> [email protected]> wrote: >> >> > Hi, suppose I store my data like this: >> > >> > Table A: table, column, data >> > >> > Now I want to create a VIEW named A.table, with columns A.column and >> rows >> > A.data >> > >> > Is that possible? >> > >> > Background: We have one table where columns can be added/removed. We >> want >> > to use the session extension to keep track of changes to our database. >> But >> > the session extension can't handle schema changes. >> > >> > Thanks a lot. >> > >> > -- >> > >> > Robert M. Münch, CEO >> > M: +41 79 65 11 49 6 >> > >> > Saphirion AG >> > smarter | better | faster >> > >> > http://www.saphirion.com >> > http://www.nlpp.ch >> > >> > _______________________________________________ >> > sqlite-users mailing list >> > [email protected] >> > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users >> > >> > >> _______________________________________________ >> sqlite-users mailing list >> [email protected] >> http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users >> > _______________________________________________ sqlite-users mailing list [email protected] http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
