{"id":2,"date":"2014-01-26T21:56:51","date_gmt":"2014-01-26T21:56:51","guid":{"rendered":"http:\/\/oracle-internals.com\/blog\/?page_id=2"},"modified":"2020-04-21T20:13:24","modified_gmt":"2020-04-21T20:13:24","slug":"sample-page","status":"publish","type":"page","link":"http:\/\/oracle-internals.com\/blog\/sample-page\/","title":{"rendered":"My Research"},"content":{"rendered":"

Overview<\/strong>
\nAs a longtime database internals developer, I’ve worked on many different areas of database engine development. Given I’ve never worked on the Oracle Database, however, there are a few cool things it does that interest me. This is a summary of my academic research in those areas.<\/p>\n

Research Methodology<\/strong>
\nFrom a problem-solving standpoint, there are only so many ways to skin a cat. As such, all vendors generally solve the same computational problems in a similar fashion. While I often have a hunch about how to solve something, I like to ensure I have a solid understanding before sharing any information with others. Accordingly, my process is as follows:<\/p>\n

    \n
  1. Play with the feature using public blogs, demos, and examples.<\/li>\n
  2. Apply what I know about how the feature could be developed, from an algorithmic perspective, to how Oracle may have implemented it.<\/li>\n
  3. Write personal code (My Projects<\/a>) to test my knowledge.<\/li>\n
  4. Share my findings.<\/li>\n<\/ol>\n

    In terms of sharing my findings, I generally do that based on the following:<\/p>\n