Post AT10V9sYsdxPIejFLM by tedu@honk.tedunangst.com
 (DIR) More posts by tedu@honk.tedunangst.com
 (DIR) Post #AT0ndpvr73m4dc4rJo by tedu@honk.tedunangst.com
       2023-02-24T17:49:56Z
       
       0 likes, 0 repeats
       
       I think it's time for a #honk database upgrade, which hasn't happened in quite a while, and reminds me of these fine moments in early schema evolution.https://honk.tedunangst.com/u/tedu/h/kXMNMt12dV3sh7KshThttps://honk.tedunangst.com/u/tedu/h/9LWw52gfRD15s6p297https://honk.tedunangst.com/u/tedu/h/qKD4xW119Fm3Wl4CX3
       
 (DIR) Post #AT0rMENjs1Nh4Uyotc by jxs@honk.jxs.me
       2023-02-24T18:04:50Z
       
       0 likes, 0 repeats
       
       @tedu this is where my schema fork with FTS5 burns me.
       
 (DIR) Post #AT0rMF8B5MWnOWhuHQ by tedu@honk.tedunangst.com
       2023-02-24T18:31:33Z
       
       0 likes, 0 repeats
       
       @jxs yeah, i see that. I think you can minimize the ongoing diff and conflict by creating a key like 'altavisted' in the config table, then check for that in main() after the regular version check, and auto upgrade if it's missing. a little sloppy.
       
 (DIR) Post #AT10V96hkZfyuEL1kW by jxs@honk.jxs.me
       2023-02-24T20:06:48Z
       
       0 likes, 0 repeats
       
       @tedu thanks for the pointer. I like the idea of separating out altavista given it’s generated from the core tables anyway. I’ll follow up with my approach.
       
 (DIR) Post #AT10V9sYsdxPIejFLM by tedu@honk.tedunangst.com
       2023-02-24T20:14:00Z
       
       0 likes, 0 repeats
       
       @jxs I'm generally okay with making small changes to stay out of the way and reduce conflict with forks if it doesn't tangle up the original too much.