On 4/11/06, Michael Bayer <[EMAIL PROTECTED]> wrote: > > all that other stuff is associated with a Schema as well. currently its > just through the Table objects, but the original idea I had for this (i.e. > last year) was that the Schema would really be a directory for all that > stuff. so it will probably become that kind of thing eventually. > > it all seemed like overkill at the time. > > what a lesson ive learned against the KISS principle !
The argument in favor of KISS and YAGNI is that while you might have an idea that *something* is needed in a spot and stick something there as your best guess, but you often don't get the right something in place until you actually get to the point where you need it. It's possible that putting that stuff on Schema early on would have dramatically changed other things in the implementation that followed, and not necessarily for the better. As much as possible, I like to see current requirements dictate features as opposed to vague ideas of the future. Take all of that with a big IMHO and a supersized dose of YMMV. Kevin ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642 _______________________________________________ Sqlalchemy-users mailing list Sqlalchemy-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sqlalchemy-users
