Hello and welcome to our community! Is this your first visit?
Enjoy an ad free experience by logging in. Not a member yet? Register.
Results 1 to 2 of 2
  1. #1
    Regular Coder
    Join Date
    Aug 2004
    The US of A
    Thanked 0 Times in 0 Posts

    A question of CMS Proformance

    I am building a CMS for my DND website. I am curious if I should have one big page that handles all the updating, adding, and deleting of data, have one page for each section (e.g. one for adding, one for updating, and one for deleting), have the SQL data handled on the same page but change the content to something like "Thank you for submitting your data." or something completely different.

    Right now I have eight different sections, multiple that by three and you have twenty-four different groups of SQL commands, plus one more for editing profiles. So twenty-five in total, and maybe a few more if I am tempted to let a few of my more trusted friends write some CSS for the site (which brings the count up to 28).

    I don't know what to do. Have one file that handles the SQL or break it up some how?

  • #2
    raf is offline
    Master Coder
    Join Date
    Jul 2002
    Thanked 0 Times in 0 Posts
    i don't realy understand the question.
    why not use some premade db-class?
    what's the relation to the CMS-perrformance? It looks more like a matter of maintenance and code-reusability then performance to me...
    Posting guidelines I use to see if I will spend time to answer your question : http://www.catb.org/~esr/faqs/smart-questions.html


    Posting Permissions

    • You may not post new threads
    • You may not post replies
    • You may not post attachments
    • You may not edit your posts