hi
i am in the middle in creating a user activity logging facility for my system which records any updates, inserts, removals from the database
I was wandering if my implementation looks ok or can any one see any major pitfalls or redundancy with proceeding with this architecture??
thanks..
so far ive come up with tables like this:
eventRecord (
session_id int ,
ts timestamp,
primary key(session_id, ts)
event_type int,
extra_details varchar(30)
)
eventList
eventList_id eDescription
1 Register
2 Login
3 Wrong Question
4 Wrong Answer
5 Wrong Sound
6 Finish Ok
7 Finish unsuccessful
Then to allow a single session to contain multiple events i have the table :
session (
session_id (PK) ,
user_id,
ts_Start,
ts_finish
)
so for example I could have entries like:
Session: 1 , 187, 2004022313379,20040333372
(user logs in)
eventRecord: 1, 200488918911, 2, 'login ok'
(user gets a question wrong)
eventRecord: 1, 200488919912, 3, 'q5'
i am in the middle in creating a user activity logging facility for my system which records any updates, inserts, removals from the database
I was wandering if my implementation looks ok or can any one see any major pitfalls or redundancy with proceeding with this architecture??
thanks..
so far ive come up with tables like this:
eventRecord (
session_id int ,
ts timestamp,
primary key(session_id, ts)
event_type int,
extra_details varchar(30)
)
eventList
eventList_id eDescription
1 Register
2 Login
3 Wrong Question
4 Wrong Answer
5 Wrong Sound
6 Finish Ok
7 Finish unsuccessful
Then to allow a single session to contain multiple events i have the table :
session (
session_id (PK) ,
user_id,
ts_Start,
ts_finish
)
so for example I could have entries like:
Session: 1 , 187, 2004022313379,20040333372
(user logs in)
eventRecord: 1, 200488918911, 2, 'login ok'
(user gets a question wrong)
eventRecord: 1, 200488919912, 3, 'q5'