i want some of what you've been smoking...

erm not neccesarily so...
if you use MySQL then depending on the licence you use you may have to pay for it.

its free if you release the source code of your application under the GPL
If you bundle it as part of your application then you have (well ought) to get a commercial licence for the server. the premise from MySQL is if you are making money by using MySQL then they want some of the money aswell, whihc seems fair enough in my books givent he amount of time energy and money that has gone into developing MySQL

I'm not to sure where the dividing line falls if you ship an application which can talk to a MySQL server and the organisation/person installing the App installs their own copy of MySQL.

equally I'm not to sure where the dividing line is if you develop software inhouse targetting an internal MySQL db.

however if it was a critical db application then you would have a commercial licence, wouldn't you

This must be the weirdest thread hi-jacking I have ever seen.
And the most blatant quest to ask other people doing your homework.

Create a new thread for this, post what you have done so far and let us know where you are having problems.

The trick with databases is to organise the info properly first. Think about the types of info, write it out on paper and try a few different things. Think about how people will use the database, how will they want to retrieve the info.

helps?

nope I rated it as a (more) sophisticated (than usual) sig spammer.. so it got canned