Hi All,
I'm developing a chat application for one of my internal dashboards, during the DB planning stages, I came across this really handy time-saver:
It basically provides a pre-written framework for a basic chat app, if you're looking to develop something like this, I suggest you have a gander - it saved me a heap of time and gave me a great base for starting out on.
I think many Wapplers would benefit from having database architecture suggestions 
For example, I once learned we shouldn't build web apps with functionality tied to individual users, but rather "accounts". So, you can have an account with 1 user, or you can have an account with multiple users (e.g. in case of businesses), so functionality is tied to accounts rather than users. Hope I make sense!
This practice is in fact used by GitHub, I don't remember where I read it, but basically a Git repository belongs to an account, that can be either an individual user or an organization.
Here’s a sneak peek at what I’m working on—employee details scattered cleverly across multiple tables. It’s a bit of a security jigsaw: crack one table, and all you’ve got is gibberish without the others.
Looks interesting, stop tempting me, got too much on my plate currently!
Thats hoiw a like to work, lots of rel;aterd small tables satisfying a specific function rathter than a big file.
Always feel it is more efficient (may be wrong) in terms of data queries, being able to query small tables at an almost granular level.
Modular table design feels so much cleaner and scalable. I’ve been pairing that with strategic use of foreign key constraints to lock down relationships across the scattered tables, plus some handy database views to present unified record sets to the frontend without exposing sensitive joins directly. It’s like giving structure and security a front row seat while keeping flexibility under the hood.
Just a tip, once those database schema’s are in your database you can create a Wappler database template and share it with others for even more easier usage, see:
I never thought of that George, thanks for the reminder. I've developed some more complex ones so once I've tested them I'll post - they're using MariaDB which has its own little foibles so I'm sure they'll be handy for someone...
The good things about the Wappler's Database Template generator is that it generates universal code - so the exported template can be imported in any database!