Hi! On Wed, Oct 16, 2019 at 3:29 PM Richard Hipp <d...@sqlite.org> wrote: > Are you trying to store a big matrix with approx 100k columns? A > better way to do that in a relational database (*any* relational > database, not just SQLite) is to store one entry per matrix elements:
Sure, this is useful for sparse matrix. But in our case we would like to preserve as much as possible of the original dataset structure. So those types of transformations then require also users to restructure data back. For example, Pandas DataFrame can be easily read out of the SQLite, but if it is converted in a way you described, then user has to make one more step to move things around. https://pandas.pydata.org/pandas-docs/stable/reference/api/pandas.read_sql_table.html I would hope that if this is something which is generally a good idea, that databases would internally do such mapping, while exposing regular structure back to the user. Mitar -- http://mitar.tnode.com/ https://twitter.com/mitar_m _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
