Okay, so I’ve been trying to read about Wappler’s subtables.
Is that how Wappler prefers to handle those kind of sorts?
I was under the impression that having the DB do the aggregation was better than sending all the data back and forth.
But, I’m probably misunderstanding Wappler and subtables.
{EDIT: I guess I do realize that Wappler makes a different table on my MySQL but I’m still confused}
I’ve read here: Creating Sub Tables with Database Manager
I’m not sure how to apply a subtable to my situation.
My DB structure.
Every worship song has a Song_ID.
Every time the band plays that song it’s entered into the “WorshipSongDates” table. The foreign key connects on the WorshipSongDates - SongID
So, do I make a subtable underneath WorshipSongDates or underneath WorshipSongs?
And what do I do with it?
I’m sorry. It’s been a long week, maybe I’m tired. LOL!