> (1) I thought it might be quicker than Perl or PHP. Correct me if I'm wrong. > > (2) I have read a short description of Triggers, and I thought these > three lines of code might be an excellent AFTER INSERT trigger. (I > don't know enough about Triggers yet to know if they'll even take multiple > lines of code however.) (A) Could this be a Trigger? and (B) Would it be worth > doing? > > (3) I've written plenty of Perl and PHP code that concatenates fields > and builds XHTML cells and rows. I thought it might be interesting to > build the rows inside the database table and have my PHP do nothing but > count MySQL records in order to know when to open and close the XHTML > table rows.
I think things just start to get messy over time. One day will come when you want to search something in the database, and you will then have to accommodate that search with more "hacks" in order to ignore the html. Further, as time goes on, say you wanted to make some design changes to your html, you are now faced with constructing a rather complicated method for updating all your old records to the new html. If the html logic is pulled out into the php/web front end, you change in one spot, the site sees those changes on all pages. Databases are used to store data, I do not really see html as data so to speak, at least not important data. Even storing a path to an image is something I would stay away from, just store the image name in a field, and call the path out in your html. This in large part is my opinion, but I do tend to find most will agree with it. -- ------------------------------------------------------------- Scott Haneda Tel: 415.898.2602 <http://www.newgeo.com> Novato, CA U.S.A. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
