The problem with solutions like PouchDb is that there are no turn-key installations. You have to pretty much do everything yourself down to the bare metal.
SQL, on the other hand, is supported almost everywhere. The workaround re fields is to specify the fields you want in advance. Rebuild the database when you need to add fields. Or to have a dozen fields with generic names in the database, but then map them with a configuration file. Mostly, I'm saying that a solution that is for everyone needs to based on technology that's commonly available. Of course, there's nothing to prevent someone from creating cool stuff, just because. -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/92975eba-bd46-43d3-83c4-68be96fde807%40googlegroups.com.
