Database Design Project : Library Management System

[@sonavijapure2668]

Why you are so good 😭😊

[@Rebellionrider]

Thank you! Glad to be of help 😊

[@sushantourpride7037]

Can you please explain Oracle fusion joints. I got so many duplicate values while joining. 🙏

[@harshalzungare9298]

Please show how to code the library management database. 😇

[@Rebellionrider]

Download the code from my GitHub github.com/RebellionRider/Library_management_system/

[@rahathussain9313]

Do you have Oracle apex play lisy

[@Rebellionrider]

Absolutely! While I don't have a specific Oracle APEX playlist at the moment, I appreciate your interest. 🙌 What aspects of Oracle APEX are you keen on exploring? Let me know, and I'll consider creating content tailored to your preferences! 🚀💻

[@satyabez6204]

Needs quiet a bit of improvement. In inventory table, is there is a need for inventory ID as a primary key. The table could have had the bookID and BranchID as composite primary key. This enforces to have an identifying relationship between inventory, branches and books. In your design, its a non-identifying reltaionship. Some of the relationships between tables are missing the multiplicity or relationship degree, these need to be stated at both ends of the relationship line. Some attributes like author, genre needs to have their own respective tables. A book can be written by more than one author and an author could have written multiple books. Same in the case of genres. Regarding the Table : Fine, It does not need the copyID as the attribute, it needs checkedoutID. Rationally thinking, in case of reporting or other metrics for business insights, a user could have checked out the same book multiple times. Based on your design, for audit purpose, I cannot determine when the fine was applied. The fine amount per day, could have changed over time. For Audits, need to track the fine amount against a checked out record. This would guarantee, a valid fine was calculated. In your design, you cannot track against the checked out details. It would be simpler to have the checkedOutID in the Fine table. With the checkedout ID, we can determine the copyID. If its too time consuming operation, we can denormalise the fine table and let it have the copyID.

[@ArshDeep-nx4cr]

Plzz show the library code

[@Rebellionrider]

Download the code from my GitHub github.com/RebellionRider/Library_management_system/