Hello, you might emulate it this way, depends on the scale, size matters 8)
hstore id | key | value 1 | firstname | John 1 | lastname | Doe 2 | firstname | John 2 | lastname | Doe obj2hstore id_obj | id_hstore 2 | 1 3 | 2 Best. On Tue, Mar 18, 2014 at 6:09 PM, mm.w <0xcafef...@gmail.com> wrote: > Hello, > > you can do a pivot, depends how big the data are, the best option would > be to extend a script like mysql2sqlite and then transform the DB to avoid > serialized like oddities. > > other option use json > > > > > > > On Tue, Mar 18, 2014 at 1:09 PM, Petite Abeille > <petite.abei...@gmail.com>wrote: > >> >> On Mar 18, 2014, at 8:56 PM, Stefan Keller <sfkel...@gmail.com> wrote: >> >> > And, actually, as you may have realized, PostgreSQL proved that even >> > (post-)relational databases can handle KVP efficiently. >> >> Just because one can, doesn't mean one should. But, as always, to each >> their own. >> >> _______________________________________________ >> sqlite-users mailing list >> sqlite-users@sqlite.org >> http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users >> > > _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
