Once again messed up the subject line...aargh...ScreenInfo not screen_info Anyway, I found this reference from the archives so while I still think there is potential in moving ScreenInfo to a database I now have Leon's reasons for not originally doing so... --------------------------------------------------------------------- List: freetrade Subject: RE: [FreeTrade] ScreenInfo From: "Leon Atkinson" <[EMAIL PROTECTED]> Date: 1999-09-28 20:26:14 [Download message RAW] > Is there a reason that ScreenInfo isn't a database table (with > all that info > plugged in with build.sql)? Yep. First, it would cost a database hit, which is more expensive than including a file. Second, on a normal site build we add lots of entries to ScreenInfo and it's a lot easier to edit a file than mess with rows in the database. Third, we tend to throw in extra array elements depending on the site. For example, when navigation changes dramatically between secondary sections of a site, we put in an element to mark with navigation module to use. Leon -------------------------------------------------------------------- ---------------------- Lab2 Design-Unit URL: http://www.lab2.com.au e-mail: [EMAIL PROTECTED] ---------------------- _______________________________________________ FreeTrade-dev mailing list [EMAIL PROTECTED] http://share.whichever.com/mailman/listinfo/freetrade-dev
