Jamie Lentin

@hyanwong once https://github.com/OneZoom/OZtree/pull/826 this is probably done. It might be worth trying to change the default for the username field to NULL, given PyDAL seems to do it's own thing...

> Are you suggesting this is done in db.py or directly in the database In ``db.py`` here: https://github.com/OneZoom/OZtree/blob/fb96f14ff9802aaa25827f0aeb7e0180a450bb38/models/db.py#L463-L462 It seems like web2py does it's own thing for defaults, rather than...

That's quite probably true, and that's why I was asking what the state of the live schema is earlier. But on further poking, I don't think it's relevant. Here, MySQL...

> but maybe that should be > db.auth_user.username.clone(unique=False, requires=None, default=None), Probably, but I'm not sure what ``clone`` does with the extra parameters. If it results in a correct default value...

Kinda related here, there's currently a bug for setting blocks in ``transition_out``. We in goto_next() currently leave() a tourstop before play_from_start() the next. So if the leaving tourstop tries to...

It does! ``` # find ./ -type f -mtime +90 | wc -l 90420 # find ./ -type f -mtime +60 | wc -l 90689 # find ./ -type f...

It's not that much work. It'd be nice not to have to do though, and have ``session.forget`` being the "default". However, I'd assume this requires patching web2py. OTOH, we could...

Could we, instead of sprinkling ``session.forget`` everywhere, put it once in ``models/db.py``? That would make it a lot harder to forget. The users of ``session.flash`` would need exceptions to this...

> I would be happy to do that, if it works I'm not entirely sure how it'd interact with the authentication, but I think it's worth trying. > Are there...

@jrosindell Whilst continuing to wrestle with this, I've noticed that we currently say "you could sponsor this leaf" for unavailable leaves, e.g. human. There's nothing we can immediately do about...