Three reasons to keep a table of card types: 1. Generally as an added check, you ask the user to specifiy the card type, then ask for the number. If that card type check is data-driven, you will need less code modification over time.
2. Once MySQL comes to support stored procs, there is a case to be made for storing the early-digit rules as data in such a table. 3. You will likely want a gif for each card type. PB ----- >> From: David T-G [mailto:[EMAIL PROTECTED]] >> ...I still have to figure >> out how to make sure that our credit card types and skill levels don't >> get corrupted (MC, MasterCard, mastercard, ...), but I guess that gets >> enforced in the software interface, right? >Isn't the card type a piece of derived data? You should never have to enter it directly; it's >computable from (the first digit(s) of) the card number. --------------------------------------------------------------------- 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
