Tsynergy

Hi

I am to design a community rental database.
I've already done the following:

1. Read a book on php&mysql
2. Gained access to hosting where php and mysql tools are available for my use
3. Able to use an already registered domain name
4. Working experience of html

The book I read gives the syntax for php and mysql scripts. Yet its seems to me that I don't just begin coding without some kind of road map. Something that connects every aspect of the community rental requirement for this database; and, which results in a functional website from both server and client side. Please help me get started.

Tj

Administrator

This is a huge undertaking considering you are just learning all of this. Everyone has their own take on how to begin something like this and a lot depends on how much programming you've done in the past. If you are an experienced programmer, this will be much easier of course. If not, then it will take you a very long time. I wouldn't worry about the road map at first. I'd start with one module/aspect of what you're looking to do. Build it simple first, then as you get experience, build more of it, and then you'll be ready to plan a road map.

If you have a timetable and want to get a headstart, you might want to look at some existing app that's similar and that you can modify. Or look at a templating system that can give you a huge headstart. I never used it, but I heard that "smarty" was good.

Vmusic

Hi,
Yes designing databases is extremely important and can be tricky. I do it for a living.
What exactly are you renting? Properties?

You normally start by describing all the business entities and their relationships. For example
A person can rent zero, one, or many properties.
A property can be rented by one person at one time, and many people over time.
A property is owned by a person or company.
A property rental rate varies by calendar date(s) or seasons


Some smart practices for design, if you're not keeping history on your business entities include: each and every table should have 4 tracking columns: creation_date, creation_userid, last_update_date, last_update_userid; use auto increment to generate unique identifiers for your business entities


I can tell without knowing your requirements, you'll have to store people and organizations or companies. You can place them into one table called a 'party' table. It should minimally have
party_id, party_type, person_fnm, person_mi, person_lnm, org_nm
if a row in this table represents a person it's party_type will be 'PERSON' whereas if it represents a copmany or organization it will be 'ORGANIZATION'.

Keep a separate table to store information about the property vs. the rental. The property itself exists if or if not it is ever rented. The rental is the association or relationship of a person (or many people), a property, some time frame, some amount, etc.

OK... you have to start with defining your business entities and their relatoinships to see what information you have to capture

Good Luck
Tell E.F. Codd I said Hi!!!

Vmusic

Administrator

Unfortunately he passed away recently. What a genius he was. The guy who taught me everything I know about databases knew him and talked a lot about the theory behind databases.