Hi Martin, Thanks for the quick reply....I have gone throu the link and it gives good insight of data managment from tables perspective...
But, from users point of view can it be something like this /home/user/user1/user1.db [User1 will have table to hold contacts list] /home/user/user2/user2.db [User2 will have table to hold contacts list] . . . /home/user/userN/userN.db [UserN will have table to hold contacts list] The idea is that at any point of time user1 should not access user2 details and vice-versa. Does it make sense conceptually and is it feasible technically ? Thanks, Pavan. On 2/15/07, Martin Jenkins <[EMAIL PROTECTED]> wrote:
Pavan wrote: > Should i create different tables for each user, so hat at any point > of time only one users data will be accessed ? Should i store all the > information in one table and then acess it ? The word you want is "normalisation" and you could have a look at, say, http://www.devshed.com/c/a/MySQL/An-Introduction-to-Database-Normalization/ The URL suggests it's for MySQL but it's pretty generic stuff. Martin ----------------------------------------------------------------------------- To unsubscribe, send email to [EMAIL PROTECTED] -----------------------------------------------------------------------------
-- '**************************************************************** Always finish stronger than you start *****************************************************************
