In that case, if you have only just started, you may well be better off
describing what your database is supposed to do before going further.
Because bad design makes your work later on MUCH more difficult. If
you design your database well, querying etc is easy (well, most of the
time!) If you do it wrong, then querying is well nigh impossible.
So, I hate to put you on the spot, but describe what this thing does...
What "things" are you keeping info about? How are they related? Once
you've nailed that down, what info do you want out of this thing?
Hope this points you in the right direction.