Need a solid basis, a primer, a "101", help!

[davidjam]

Ever since I started with php/mysql I've been absolutely fascinated with project management and service-oriented websites integrated with a database backend. BUT, I feel a little over my head here as far as the logic goes.

Can anyone refer me to a book of substance, or site that goes indepth into structuring sites like these..?? "Like what?" OK, maybe I haven't made myself clear.

For instance, I have a business forms company. There are customers. Each customer has a number of jobs in-progress or completed, which they both entered and can edit on-line anytime. Then each job could in effect be divided again into these "sub-jobs" / "items"...

Essentially, I've got: company->customers->jobs->items.

I'm not expecting a major explanation on this thread (though I would most grateful for your thoughts...). Does anyone know of a book or some other resource that is a great "primer" for this kind of application?

[leatherback]

If it is really about the logic, I would suggest something like database management (wATSON; wILEY & SONS) and some primer in programming & logical thinking.

Because that is all you need: A basic in programming (Which is nothing more then ordening your thoughts & required processes in a logical series of steps, the coding is just foolswork after that) and knowledge on how-to manage databases, and proper ordening of tables / records in them.

But I feel you need more on the actual PhP/MySQL;:
Read more on this website, and learn about mysql at mysql.org

Furthermore.. there are sticky FAQ threads in each forum. An other good starting point.

J

[pohopo]

I can't think of a good database management book off the top of my head, but I would recommend you read up on Entity Relationships and Normalization. The understanding of these two ideas will help you greatly in understanding relational databases.

[Shrike]

dotProject (http://www.dotproject.net/) is a job management system which one of my clients uses. It seems fairly decent so it might be worth having a look to see how things run under the hood.

We also have a bespoke system at work. I used to sit opposite the developer who wrote it. He has left now, for psychiatric help I think. Plus he went bald. Well actually he got a new job and was always bald, but I think it was a very complicated project ;)