The forums have permanently moved to This forum will be kept around in read-only mode for archival purposes. To learn how to continue using your existing account on the new forums, check out this thread.

Results 1 to 5 of 5

Thread: Calling all database/cms/backend PROs...

  1. #1

    Calling all database/cms/backend PROs...

    Ok, I need to make a customer database system, and i'm not sure where to start.

    Right now, the business is doing all their customer management using paper and files, and they want a computersed system. Just to give you an idea, they're a suit-hire company, and they loan out about 1200 suits per week. They need something to keep track of customer details, suit details, checkout and return dates, etc, etc, etc... My main concern is that the database will be massive...

    I'm thinking PHP+MySQL, cos thats all I know Plus, being web-based would be good, since the other stores could use the same database, but that's just a though.

    I'm totally newb to anything other than PHP+MySQL... but ive heard of other stuff like oracle and stuff...

    Any advice or suggestions would be appreciated!

    Thanks in advance.

    I think you should visit my site.

  2. #2
    I'd just go with php+mysql.. I've been making CMS's with those technologies for a good couple years now and I love it. Super easy to work with as you probably know, and it won't require you learning something new.

  3. #3
    home cooking is killing the restaurant industry
    Moved to Server-Side
    There are only 10 kinds of people in this world:
    Those that might know ternary, those that do, and those that don't
    Say NO to DRM.

  4. #4
    You'll be OK with PHP+MySQL, but look at things like transactions and InnoDB.

    With any business where money's involved, you want to make sure that you either update the database, or you don't - transactions will allow you to make sure you don't fail in the middle - for example, updating a client record that an order has been placed, but not updating the store record.

    InnoDB also gives you things like hot-backup, row level locking, and a bunch of other tools you'll find very useful when dealing with money.

    I wouldn't worry about the size, though. 1200 suits per week = 62000 rows per year (assumes 1 row in some order table for each order). The good news is that MySQL will work fine up to millions of rows, as long as you write your queries correctly (efficiently).

  5. #5
    Oh, ok. Thanks for that JustJeff Much appreciated.
    I guess I'll just stick to PHP+MySQL.

    Good to know MySQL should be fine with millions of rows. If it makes any difference, the host I'd be using have Dual-P3 1GHz CPUs. Could you explain what you mean by 'efficient' queries? I'll probably just be using SELECT, INSERT and UPDATE...

    Also, what's this InnoDB? I had a look at the site, but was a little dissolutioned... If it's for backing-up, the host does weekly tape backups anyway. I doubt they'd be needing to do money transactions from the program - just record keeping (if that's what InnoDB is for )

    Thanks again for your info

    I think you should visit my site.

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

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

Home About Meet the Moderators Advertise

 Link to Us


Copyright 1999 - 2012