1 / 9

Exploring Drupal System Requirements: Past, Present, and Future Insights

This presentation by Jeremy Epstein discusses the evolution of Drupal's system requirements, focusing on its reliance on foundational technologies like PHP. It highlights the end of PHP4 and the transition towards PHP5, recognizing the need for proper object-oriented programming and database management. The session reviews the strengths and weaknesses of various databases, including MySQL and Postgres, and emphasizes Drupal 7's flexibility in accommodating different database management systems. Ultimately, it showcases the adaptability and potential of Drupal as a platform.

kevin-long
Télécharger la présentation

Exploring Drupal System Requirements: Past, Present, and Future Insights

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Jeremy Epstein 18 May 2008 Drupal system requirements: past, present and future

  2. Drupal is built on the shoulders of giants

  3. PHP dying? gophp5.org PHP4 end of life: no more feature releases since end of 2007 No more security releases after 8 Aug 2008 <? ?>

  4. Proper OO SimpleXML PDO

  5. SELECT * FROM {databases} WHERE name IN( • MySQL: “the Drupal database” • Lacking in features • Postgres: neglected sibling • More robust • Others: experimental support at best

  6. Drupal 7 will let you hammer in any old DBMS

  7. When the blocks fit together, anything is possible

More Related