Hi, David García Granda schrieb am 01.12.2011 23:06: > I see it similar to current database approach where I find > much easier to use sqlite instead of using locally installed mysql > one.
Completely agree with you here. The portability and robustness of sqlite is a huge advantage. (I just had a look to CouchDB because I wanted to learn/play around with a document oriented storage - and indeed it's very relaxed ;) Nevertheless if one has higher structured data (like our gpx), relational DBs like sqlite are a bit cumbersome. One can a) store data in FS and parse/map on demand. b) create tables of tables to mimicry nested structures like laps within an activity c) use some object-relational mapping mechanism d) like a), but store within DB, dictionary like (JSON) pytrainer used a)+b) so far. Nathan proposed moving towards c), right? With an ORM solution one is always bound to some specific mapping (specific version, specific programming language etc.) But I'd rather prefer to have my data stored transparently. Universal and open - however I want to access them in the future. Apropos future: Very interesting this interview with Richard Hipp (creator of sqlite), together with Damien Katz (dito couchdb) they try to establish a document oriented query language. Hipp also plans to build 'unqlite' an embedded document-DB equivalent to sqlite. http://www.infoq.com/news/2011/08/UnQL Regards, Arnd ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d _______________________________________________ Pytrainer-devel mailing list Pytrainer-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/pytrainer-devel
