I'm starting to notice some bad decisions I made regarding @pixelfed database structure

In 2018 when I first started Pixelfed, I took a lot of inspiration from Mastodon, and while their DB structure makes sense for them, I'm realizing that it's starting to limit us

Storing posts, replies, and shares in a single table doesn't make sense for us

Fixing this will be fun, I love challenges and look forward to blogging about it after a seamless deployment.

The goal is to make this unnoticeable 😎

4
Share
Share on Mastodon
Share on Twitter
Share on Facebook
Share on Linkedin
StephOne :javascript:

@dansup @pixelfed what structure would make sense?

1
3mo
wikiyu

@dansup @pixelfed

Years ago when i was younger i would suggest "procedure" approach -> move all DB stuff to as encapsulated procedures as possible (crud)

then making a migration BUT with stay on application side to procedures that are changed with migration.

Now? I dont know, i didnt thought about stuff like that for at least 4? 5? years as i am doing a bit different part of it development now then then.

1
3mo
Henri

@dansup I think this is just copying the Twitter concept of a tweet?

0
3mo
kcarruthers

@dansup data architecture is often a gotcha. Good luck.

0
3mo
Replies