On Jun 23, 8:16 am, Oveek <[email protected]> wrote: > Minor hiccup with the addition of the validation code. After its > introduction, the policies table (assuming sqlstore) is expected to > have the new 'accept' column. But when using an older sqlstore > instance without an 'accept' column, the latest tiddlyweb master > crashes on list_recipes because the 'accept' column doesn't exist. > Don't know if the crash is due to postgres' strictness.
I didn't have this problem with the sqlite based store used for tiddlyweb.peermore.com, but I was assuming it would happen. > I don't know if the underlying issue of new versions of tiddlyweb > demanding columns that don't exist in older store versions is going to > occur frequently enough to warrant attention. My hope is that it is not. One of the reasons (among) I've been holding off on making a 1.0 release is that I want the data model to as ironed out as possible before then. I'd prefer changes there to be very rare. Such changes cascade throughout the code and become a real PITA. For example, the recent discussion of doing recipes in recipes is harder and messier than I because of some earlier assumptions. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TiddlyWikiDev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/TiddlyWikiDev?hl=en -~----------~----~----~----~------~----~------~--~---
