Adamb10 Posted November 7, 2006 Share Posted November 7, 2006 I made a powerful guestbook script months ago. It was my most advanced script since it had advanced features but it lacked efficentcy. In order to fix that I tried recoding the query backend which thus forced a complete DB redesign. If I have a table called "settings" which would store items such as feature enabling/disabling, the title, and other various options what fields would I create? I get Fields, rows and columns mixed up alot. :(Thanx Link to comment https://forums.phpfreaks.com/topic/26451-fields-rows-columns-its-all-confusing/ Share on other sites More sharing options...
fenway Posted November 7, 2006 Share Posted November 7, 2006 Fields and columns are synonymous -- I like using columns, since it works well with rows (i.e. rows have multiple columns, like an actual table layout, like the DB table too); good analogy. As far as DB design, you want to keep related columns in the same table, and then relate the tables together. Link to comment https://forums.phpfreaks.com/topic/26451-fields-rows-columns-its-all-confusing/#findComment-121105 Share on other sites More sharing options...
Adamb10 Posted November 7, 2006 Author Share Posted November 7, 2006 Well my old way involved using the fields to store the data and stuff never involving with columns and rows. Thats what I'm trying to fix and develop a new way. Link to comment https://forums.phpfreaks.com/topic/26451-fields-rows-columns-its-all-confusing/#findComment-121209 Share on other sites More sharing options...
fenway Posted November 7, 2006 Share Posted November 7, 2006 Forget about how the DB will work, and just organize the data logically. Link to comment https://forums.phpfreaks.com/topic/26451-fields-rows-columns-its-all-confusing/#findComment-121219 Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.