Assalamualaikum sir, I just wanna thank you a lot for creating such amazing videos and explaination. Alhamdulillah sy dapat A dalam subject Db Engineering berkat pengajaran lecturer + video2 sir ...😘
Is it possible to have a combination of self join with any outer join to output data from a single table? If yes, will it be 1 real table + 2 'imaginary' tables?
@@notyournormalbrother What I mean is when we select 2-3 same tables but differentiate it with alias .For example SELECT employees e JOIN employees m .... JOIN employees l ..
@@ikmalasraf8850 there is no imaginary table. All are tables inside the database. Oracle just treat them differently because you gv it different names because they are all the same tables.
weak relationship - bila ada connection between strong and strong entities. (putus-putus) strong relationship - bila ada connection between strong entity with weak entity (solid line) strong entity - can exist on its own weak entity - need strong entity to exist (contoh, bridge entity)
courses ni refer to subjects yang dia ambil. contoh course: database. so, 1 subject many students, 1 student many subjects. 1 student boleh ambil banyak courses at the same time. contoh, satu semester kan student boleh ambil 5-6 courses kan. same goes, dalam satu semester, takkan sorang je ambil course database. ramai student ambil. So, maximum occurences utk student dengan course akan jadi, many students, many courses. Hence, kena ada bridge la in between students and courses.
Hi, how to represent "read_only", "view" roles or authentication on entities tables in ERD if that was written in the problem scenario please, also for the visitors users to an online forum , do we have to represent them in a separate entity please?
Sorry, I dont get your question. But, read only table can be done with alter statement. You create the table as usual, insert all the data needed, then alter the table into read only status to make sure the table cannot be updated or deleted. But, if you want the user has read only on the system, you need to handle it at your coding. For visitor of online forum, if you did not want to store their data, no need new entity. If you want to keep their details, they are not visitors, they have become user already.