What you probably want to do is go to amazon, and get these two books:
"The Practical SQL Handbook"
"The Practical SQL Handbook: The Sequel."
These two books are on general DB design issues, and discuss
normalization in depth. I have them, and enjoy them very much.
And as for
thods,
and over time methods of payment might be deleted or added. So, I use the
one-to-one relationship to create tables like this:
_payments_ _creditCard__check_
paymentID paymentID paymentID
invoiceID cardNum check
Hi,
I'm not sure that this is the best forum, as it is more of a database
design question, but I hope that someone can help me.
I am creating a billing system. Each customer can pay via several methods,
and over time methods of payment might be deleted or added. So, I use the
one-t
