Self-studying databases and doubts on PhD
- How exactly does an SQL engine organize the tables? What data structure does it use (trees? heaps?)? Does it change to a B-tree when the index is created? How does all of this work?
- What does it mean by an elastic database?
- Completely unrelated, but this is one thing I've been obsessed with recently: How does one choose what to work on in a PhD, especially in the database area? For example, I am interested in query optimization, but what should I research? How does one start? Also, I've seen some profiles of individuals who pursued a different domain for undergrad and master's but then went into a CS PhD. How can one do this? Basically, how do you look for a problem in something you're interested in, and how do you know that it can be solved?
Thank you all! Appreciate your time.
https://news.ycombinator.com/item?id=36504838
https://news.ycombinator.com/item?id=17212926
There's likely a lot more to be dug up with a less half-assed search.
The normal two cases is doing a master, and by contacting professors you find opportunities and build with the help of the future PhD director the subject. Second case is there is an open position for a already existing subject.
In extremly rare cases, the subject is proposed by (brilliant) students to Prof.
but in all cases, you don't work alone and you stand on the shoulders of giants
https://www.oreilly.com/library/view/designing-data-intensiv...
- Database internals
https://www.oreilly.com/library/view/database-internals/9781...
All of your questions (and much more) will be answered!