I get this question a lot, and generally, the answer is no. The good news is most of the time, it’s not really necessary…what is it you want to do?
Thanks for the quick reply. And thanks for making such a great plugin. It’s nearly everything I want.
So here’s what I was hoping to accomplish:
1. Create a Family database to track family names and contact information.
2. Make this available to my family on a password-protected page.
3. I maintain this database myself – nobody else adds records.
4. Create a separate Gamers database for specific games.
5. Players of a particular game can add their player ID and provide specific information about what they offer (and what they need) in the game.
6. Make this Gamers database available on a public page (no password or sign-in required).
Basically these are two completely unrelated databases. And now that I’m describing it for you I can already see the flaw in my logic.
I originally chose this plugin because I didn’t see how I could add simple tables to my WP pages. Now I think maybe there are plugins for adding tables that would be better for handling the family contact info.
Then I can use your plugin for the Gamers database.
What do you think?
Yeah, sounds right. You might just need a simple contact management plugin for your family contact info.
Yep. I tried it out last night. I got a simple tables plugin for doing the contact list (it’s pretty static as data goes).
Now I’m recreating the DB as the gaming db I wanted to do. Thanks for your help.
I’ll be donating to you at my next payday. I think your plugin is fantastic.
For what it’s worth, I think there’s a gap in the plugin space for a quick and dirty database tool that allows you to create and manage multiple simple databases on a single web site. There’s a My Treasures plugin that is similar to what I have in mine, but it’s not configurable like yours. If you’re ever interested in exploring this, I’m a software Product Manager with deep experience in UX and software requirements. I feel confident I could put together a good set of simple requirements/use cases to define this sort of plugin. I’d enjoy working on it with you.
All the best,
David
Thanks David, sounds very interesting. I am in the process of designing a full-featured database plugin…not the simple one you suggested. I think there is a design challenge in what your suggesting, just the right balance of simplicity/utility will not be easy to hit, and that makes it intriguing.
Agreed. I found your design to be extremely easy to use – very intuitive. I wouldn’t change it all. I was actually thinking that adding some sort of identifier that allows for differentiation between tables might be all that’s really needed. And yes, I realize I’m probably oversimplifying it because I have no real understanding of how your plugin is coded.
Of course, I’m assuming that no two tables would ever share data.
