Hello, sorry for a late answer, but here it comes.
On Tue, 27 Aug 2002, Mylin Campos wrote: > I'm a newbie with mysql. I have a few question and would really appreciate > it if you can help me. I'm creating a database for a payroll system. I > actually finish with my entity relationship diagram. What should be the > next step? I know I should create the database already but while reading the > mysql documentation I've been encountering so many questions that I'm > getting all confused on where to start. Right, if you have the root account or any other account that has enough privileges, the right way to start is to create your own database. For now stick with the default settings for that, they are OK. > First, where does the priviledges come in? Specifically the alter, drop, > select, insert (etc) priviledges come in? Or does this concern the database > administrator which is not my concern since I'm only the software developer. Every time you run a query on MySQL it checks whether you have enough permissions to do so or not. If not, it returns an error. If you are the owner of your database (I suppose you are), you have all rights to that database, including ALTER, DROP, CREATE and so on. As the owner you also have SELECT, INSERT, UPDATE, DELETE at your disposal, along with others. If you read the manual beginner's section very carefully, I think you will grasp the permissions topic fairly well. It's important to remember that users are defined using username/hostname pairs. That is, for example, you can have different privileges, depending on whether you login from your work computer or your home computer, as they have different IP addresses and host names. > Should I create the tables and then what next? Yep, create tables. Then insert/dump your data into them. Or do anything that suits your needs. :-) > Mysql does not a have a feature like access where you link one key to > another by dragging one field to another. does this mean that linking the > tables in mysql is done manually via the sql statements? That's because MySQL is just a database backend, Access has the Jet engine that it uses as a separate DLL, MySQL clients are available but their current functionality is a bit limited in some cases. MySQLFront is a good one to start with. You can use Access, too, to use MySQL but all its graphical features won't work, though. phpMyAdmin is fairly efficient, but it requires you to have a web server running PHP. For most of your daily work you can use any graphical frontend you want to, but for the more advanced (mostly administrative) tasks you will want to learn enough pure SQL to accomplish those tasks more effectively. A URL for graphical MySQL frontends: http://www.mysql.com/downloads/gui-clients.html MyCC is pretty OK, but its development is still underway. Hope this helps, feel free to ask further questions as needed. Best regards, Iikka ****************************************** * Iikka Meriläinen * * E-mail: [EMAIL PROTECTED] * * Vaala, Finland * ****************************************** --------------------------------------------------------------------- Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
