Ian,
Just a suggestion...for the login information tracking, you could simply use the Sessions table (unless people clear that table on a regular basis), then you could create a Login_Track table that would track all the login stuff you were planning on adding to the Users table and use the COUNT function rather than incremeting a column within the user table.
Example schema:
Links_Login_Tracking
UserID (INDEX, NOT UNIQUE, NOT NULL)
Logged (DATETIME, NOT NULL)
Then you can reference the UserID as a FK to the Users table in your script.
Just a suggestion...since with your schema, you are only tracking to three logins.
Using M<->M connections as much as possible allows for future growth of applications/systems.
========================================
Buh Bye!
Cheers,
Me
Just a suggestion...for the login information tracking, you could simply use the Sessions table (unless people clear that table on a regular basis), then you could create a Login_Track table that would track all the login stuff you were planning on adding to the Users table and use the COUNT function rather than incremeting a column within the user table.
Example schema:
Links_Login_Tracking
Quote:
UserID (INDEX, NOT UNIQUE, NOT NULL)
Logged (DATETIME, NOT NULL)
Then you can reference the UserID as a FK to the Users table in your script.
Just a suggestion...since with your schema, you are only tracking to three logins.
Using M<->M connections as much as possible allows for future growth of applications/systems.
========================================
Buh Bye!
Cheers,
Me
