I?m in the process of re-designing a database at the moment. I?ve spent the last few days on it to make sure that it?s perfect. I?m aiming to have it in 3NF with cascading updates and deletes.
Guess I have a few questions:
Most of my tables have primary keys; others are just relationships such as ?enrolments? ? what students are assigned to classes. At the moment this table has two regular keys ?class_id? and ?student_id?? should both of these be primary keys (or unique) or should I just leave the table the way it is?
I have not specified any limits for my varchars. Is this bad practice or does it even matter seen that they are ?variable length? characters? From what I understand one byte equates to one regular latin character. This will be a multi-lingual application so the tables will need to be UTF-8 character encoded. How does this affect the varchars length? Eg: varchar(25) how many UTF-8 characters can this store, will this allow the same amount of characters no matter what language script is used?
Question
Guest
I?m in the process of re-designing a database at the moment. I?ve spent the last few days on it to make sure that it?s perfect. I?m aiming to have it in 3NF with cascading updates and deletes.
Guess I have a few questions:
From what I understand one byte equates to one regular latin character. This will be a multi-lingual application so the tables will need to be UTF-8 character encoded. How does this affect the varchars length?
Eg: varchar(25) how many UTF-8 characters can this store, will this allow the same amount of characters no matter what language script is used?
Thanks in adva:pe ? hope someone can help :p
Link to comment
Share on other sites
12 answers to this question
Recommended Posts