Hello everyone, I know that the topic of titles as tiddlers ID have been discussed several times for TW itself. But what about external stores? This is directly related to sync adaptors and external databases as store for the tiddlers. Normally in databases there is a primary key, that is unique and incremental, and then the user data/fields. This have several advantages like traceability of a single element among all their changes. Sticking to the name as an unique identifier we will lose track of tiddler in every database system once you rename it. This is because how TW handles tiddlers: every change on a tiddler means deleting the old version and substitute it with a totally new one. This is against any DB system I know, and recently I have faced several problems (like loosing related attachments) because of that.
That's why I'm asking community for the best approach. Should we stick to titles as IDs when we sync to a remote database? Or should be treat the tiddler just as a collection of fields that we store in a particular entry of our DB? Of course the syncadaptor should handle the conversion however it's needed. Thanks for your point of view. -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/tiddlywiki. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/e53f5ef2-225a-4f88-8483-3d094300a259%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
