I build a few login and password systems in MySql, my general layout is as follows:
Users table and account table. The users table has the bare minimum columns in it, id, username, password, session, updated, added. Account table has stuff like first name, last name, email address, street address etc etc. Sometimes upwards of 30 or so fields. My logic in this comes from a past history with Filemaker, which never really supported relations well, relations were each separate databases. The idea was, the less data in each database, the faster you can select it. So with only minimal data in the users database in filemaker, I and not needeing the account data very often, that is how I built it. In a login pass system, I am selecting from the users table on every page load, I only need to select the session field generally. My question is, does it matter? it would be easier to put all the data in one table, but then that one table will have more data in it. I however, will only be selecting one item from that now large table. Summary: is SELECT session from users where session = 'x' faster or slower depending on how many columns are in the table? -- ------------------------------------------------------------- Scott Haneda Tel: 415.898.2602 <http://www.newgeo.com> Fax: 313.557.5052 <[EMAIL PROTECTED]> Novato, CA U.S.A. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
