I don't think he was asking about *programmers* creating or modifying *schema*.
On Wed, Jul 30, 2008 at 11:07 AM, Tim Spalding <[EMAIL PROTECTED]> wrote: > This gets religious quickly, but, in my experience, programmers who > learn on a framework miss out on their understanding of database > necessities. They may not matter much when you have a low-traffic, > low-content situation, but as your traffic and data grow you're going > to want an understanding of how MySQL optimizes queries, what's > expensive and what's not, and so forth. Although anyone can learn > anything, experience is the best teacher, and, in my experience, > frameworks encourage you to avoid that experience. > > For example, the Ruby programmers I've worked with have been unaware > that MySQL only uses one index per table per select, causing them to > index far more than they need, how joins work across different MySQL > data types, the advantages of ganging your inserts together, etc. This > stuff adds up fast. > > Of course, the same arguments could be leveled against PHP in favor of > C, against C in favor of assembly, etc.. Abstraction always has merits > and demerits. > > Tim > > On Wed, Jul 30, 2008 at 10:46 AM, Cloutman, David > <[EMAIL PROTECTED]> wrote: >> This is why most Web applications have to implement CRUD interfaces. PHP is >> definitely for the uninitiated. >> >> Along the lines of CodeIgnitor, I would suggest using another framework >> Symfony. It's a very powerful, yet easy to learn framework, and it will >> autogenerate the CRUD for you. Really, some framework is probably the way to >> go for this, regardless of which you choose. >> >> - David >> >> -----Original Message----- >> From: Code for Libraries on behalf of Ken Irwin >> Sent: Wed 7/30/2008 6:35 AM >> To: [email protected] >> Subject: [CODE4LIB] what's friendlier & less powerful than phpMyAdmin? >> >> Hi folks, >> >> I have some straightforward MySQL data tables that I would like to be >> editable by some of my less-techy colleagues. I tend to think of >> phpMyAdmin as a perfectly serviceable and reasonably interface for >> updating database tables, but I'm told that it's kind of intimidating to >> the uninitiated. >> >> Are there alternatives that are meant for non-admin-types? I'd want >> something with read/write permissions, but that could be targeted at >> just a few tables, wouldn't have any of the more potent tools (drop, >> empty, etc.). In the ideal world, I might like something that would >> prevent users from doing things like accidentally changing primary key >> data and things like that. >> >> I've thought about writing something, but I suspect that would be >> reinventing the wheel. Any ideas? >> >> Thanks, >> Ken >> >> -- >> Ken Irwin >> Reference Librarian >> Thomas Library, Wittenberg University >> >> >> Email Disclaimer: http://www.co.marin.ca.us/nav/misc/EmailDisclaimer.cfm >> > > > > -- > Check out my library at http://www.librarything.com/profile/timspalding > -- Shawn Boyette <[EMAIL PROTECTED]>
