Ranter
Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
![](/static/devrant/img/pipeless-devrant-banner-white.png)
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Comments
-
@PieSage I did... Cudnt understand a thing... confused me more âšī¸
Can’t get dbms stuff in my head đđ
Tried for ~3 hours... I might just skip the topic now đ -
A view is a SELECT that is treated as a table. It can either be materialized (that is stored in the system like a table) or requeried each time.
-
Conflict serializabilty is locking. Only one person can do “something” at a time. If someone is reading, no one can write. Sometimes a chain of events happen that causes deadlock. Locks can happen at the row, page, or table level; system dependent.
-
@bkwilliams so basically, view serializable is viewing the table??
And conflict serializable is conflicting in read/write in concurrent transactions? đ¤ -
@Electrux views are just SELECTs that are saved like tables.
Conflicts can happen between multiple readers not just read/write and now to deal with the situation. -
@Electrux some reads are “bigger” than others:
select top 1 field from table;
select field from table;
select count(field) from table;
select distinct field from table;
select count(distinct field) from table;
All of these are reads and if you could “do them all at once” the locking optimizer would try to figure out which is the simplest and therefore fastest; and it goes first. -
@bkwilliams oooh I guess m understanding it now... kinda... thanks a lot â¤ī¸â¤ī¸đđ
Related Rants
Ok... I hate databases... ( subject )
I can’t understand a single thing đđđ
What the hell is view and conflict serializability!!!
Tomorrow is my exam... đđđđ
If someone can tell, it’ll b extremely helpful đ¨
rant
wth
dbms
help
serializability