network profile
| bio | website | kashit.org |
|---|---|---|
| location | Srinagar, India | |
| age | 27 | |
| visits | member for | 4 months |
| seen | Jan 31 at 4:05 | |
| stats | profile views | 2 |
I am an open source enthusiast from Kashmir
|
Jan 31 |
comment |
Billing Module (Fee) for School Management System Thank you for your advice. |
|
Jan 31 |
comment |
Billing Module (Fee) for School Management System Thank you. Surely will look into LedgerSMB |
|
Jan 17 |
comment |
Relationships in a school database @FrustratedWithFormsDesigner - What about if i have to fetch all students with their current_data attached? |
|
Jan 17 |
asked | Billing Module (Fee) for School Management System |
|
Jan 16 |
comment |
Relationships in a school database Course is just an example. THere is whole lot of other information associated with student_current table like roll no, section, bus route, fee slab, current photo url etc. That is the reason to have independent student_current table. Revisioning is for audit purposes, as it has to be maintained for legal purposes in case of student. Changes in name, date of birth etc have to be revisioned somewhere. I was thinking of creating an archive table for student table which will store previous revisions of the student record. |
|
Jan 16 |
comment |
Relationships in a school database What can be better approach in this scenario. student base table is having one-to-many relationship with student_current table. At any time, I want to fetch students with their current details (here the current detail will be latest one based on date). |
|
Jan 16 |
comment |
Relationships in a school database Student is having some additional data that keeps on changing like the class he is studying in, additional details related to that class like his roll no, section etc. Additionally the details in student base table may be updated at any time and I want to create a new revision of the record so that the previous record is saved somewhere. |
|
Jan 16 |
comment |
Relationships in a school database Thanks for the answer. But it will always be one to one in case of parents, while as for gaurdian, it might be one-to-many. This approach is appropriate. Thanks for the help. I would appreciate if you can help with the updated question. |
|
Jan 16 |
comment |
Relationships in a school database ypercube - It is always one to one as they need to store independent relationship for a sibling, as there can be simple variation in name etc of the parent. So doesnot need to be many to many. @gulli - Thanks. Please check the updated question. |
|
Jan 16 |
awarded | Editor |
|
Jan 16 |
revised |
Relationships in a school database added 783 characters in body |
|
Jan 16 |
asked | Relationships in a school database |
|
Jan 16 |
awarded | Autobiographer |
