On Fri, Nov 21, 2014 at 10:45 AM, RSmith <rsm...@rsweb.co.za> wrote: > Alternatively you can serialize anything object-like to XML or JSON and > simply store the resulting string in the database. This allows you to not > spend a lot on DB design and to use the same DB layout for any future > changes to the base objects and save more since object-to-JSON etc. > serializers are usually freely available and easy to code >
Apropos: for such a C++ library, see http://s11n.net (caveat: i haven't updated it in several years, but do respond to feedback and questions via private mail (not the list, as SourceForge can't keep the spammers out of it)). Alternately, a lighter-weight, JSON-only solution: http://fossil.wanderinghorse.net/repos/nosjob/ -- ----- stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal "Freedom is sloppy. But since tyranny's the only guaranteed byproduct of those who insist on a perfect world, freedom will have to do." -- Bigby Wolf _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
