Old 09-06-2004, 04:46   #1 (permalink)
byte
world class cynic
 
byte's Avatar
 
Join Date: May 2004
Location: North West
Posts: 140
Send a message via MSN to byte
Backend & Design!?

Right, so I'm designing a site with database integration - what order do you do things? Database first or design the site first?
__________________
Byte.Visual Media - Out Now
The Booklist - Coming Soon
  Reply With Quote
Old 10-06-2004, 09:26   #2 (permalink)
Static
::H4xx0r::
 
Join Date: Jun 2004
Location: UK
Posts: 57
both =)
  Reply With Quote
Old 10-06-2004, 09:42   #3 (permalink)
Bill Posters
trouble free and loverlee
 
Join Date: Mar 2003
Location: YooKay
Posts: 2,968
Quote:
Originally Posted by Static
god you can never get a proper answer out of you ppl i ask a proper question n u lot take the fukin piss
.
  Reply With Quote
Old 10-06-2004, 09:43   #4 (permalink)
Stickman
Dr. Lucien Sanchez
 
Stickman's Avatar
 
Join Date: Mar 2003
Location: UK
Posts: 5,638
The law of karma.
  Reply With Quote
Old 10-06-2004, 09:45   #5 (permalink)
Static
::H4xx0r::
 
Join Date: Jun 2004
Location: UK
Posts: 57
i said both because while making a site wiv intergrated DB you would do both as u add the tables at the same time or as u create the sites needs
  Reply With Quote
Old 10-06-2004, 13:16   #6 (permalink)
spacious
Registered User
 
Join Date: May 2004
Posts: 6
Although "both" may be how you learn the hard way - I would disagree.

After recently completing a pretty in-depth CMS (w/ PHP & MySQL) and trying different approaches I found doing it that way lends to bad dB design or a constant reworking of both the front and back ends (which gets damn old). These are the steps I suggest (which work for me):

1. Do a breakdown of all the content on all the pages you want to store in the dB. (before any markup or programming).

2. Read some articles or books on basic database design and architecture. (This is a huge subject, but if you get the jist of index tables and joins etc you will be on the right track.)

3. Using this info, map out your dB structure. On paper or in a spreadsheet format - Think about forward compatibility (ie how will this strucure do if it grows? will it work well with future designs? is it easily upgradeable? etc.)

4. Also give some thought to the names of tables and fields. This will help later when remembering them or accessing from forms (ie naming <input>s the same as field names and building your queries dynamically).

5. Once you are satisfied with your foundation (dB) then begin to buid your UI.

You may still go back and alter a few things that weren't apparent at the time, but this will save you mad development time (and a few headaches) and your database will be easier to maintain and update in the long run.

I just found that when you redesign a site a good solid dB design will save you the time of redesigning that as well.

Hope that helps.

peace.
  Reply With Quote
Old 10-06-2004, 13:26   #7 (permalink)
byte
world class cynic
 
byte's Avatar
 
Join Date: May 2004
Location: North West
Posts: 140
Send a message via MSN to byte
That's how I've done it previously, I was just wondering if I was using the best method or not!
__________________
Byte.Visual Media - Out Now
The Booklist - Coming Soon
  Reply With Quote
Reply



Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)
 
Thread Tools Search this Thread
Search this Thread:

Advanced Search


Contact Us - Web Design Forums - Archive - Top
Search Engine Optimization by vBSEO 3.0.0 RC8