jblumenthal

It was a good discussion with the general feeling that PODS was pretty much a work in progress. The hard core database coders all stuck to their hard coding, and I would have to admit that they did make a case based on efficiency, etc., especially if the database design is fixed.

Experience however, has taught me that the real task in database applications is in the design stage and rigorous prototyping pays off. If you are indeed a non-coder, then PODS may be a perfectly good tool for doing your development. I took a look at the internals for MySQL in php and it doesn’t look all that foreboding. My recommendation would be to go ahead and try PODS for your prototype. If performance becomes an issue you can address it later.

Thanks for the info, and I’m glad to see you use the word “properly” in database design. When a system is screwed up it is more likely than not in the design and everything goes downhill after that.

Our local WordPress Group (Chicago) is having a PODS session at our next meeting so I’ll have a chance to see and hear a bit more. The ability to extend WordPress is an interesting topic and I’d like to learn more about how the pros like yourself approach it.

BTW: I’m 75-years old and have been coding stuff for a very long time. I expect my tombstone to read, “He knew FORTRAN.”

I’ve heard about the PODS plugin but haven’t looked at it. On the surface it appears to be a way of creating a relational database, but I’d have to check it out before making a statement.

Got it. Thank you, and aside from solving this dilemma I now know to look at all the available screen options.