[eluser]jedd[/eluser]
Actually, I'm regretting now not pushing to have the distinction between student and guardian somewhat blurred - or rather, made in a different way to having two similar tables - as it's just going to get messier having all
people having addresses, emails, phone numbers and so on - but having to double up on each of those connecting tables.
I'll run it through the background processing part of my brain, but my thought now is table to combine student / parent:
person: [ id , type , fname , lname ]
type could be ENUM or just a CHAR and obviously denotes parent or student.