The drop is always movingYou know that saying about standing on the shoulders of giants? Drupal is standing on a huge pile of midgetsAll content management systems suck, Drupal just happens to suck less.Popular open source software is more secure than unpopular open source software, because insecure software becomes unpopular fast. [That doesn't happen for proprietary software.]Drupal makes sandwiches happen.There is a module for that

My progress on Drupal 8: update #4

Submitted by nk on Tue, 2012-10-09 11:52

The system table removal patch went through some significant changes thanks to alexpott and sun and is now ready. That's great! I got busy with creating a proper version for the temporary key-value store patch: this is a requirement for Views in Core and also would allow for a nice entity preview workflow if someone would write it. EntityFieldQuery has been rewritten, there are a six more tests to fix, doesn't seem like a big problem, it still needs a lot of documentation and new tests but bojanz is back from vacation and promised tests. It seems the date formats patch takes a reboot because of changed expectations, this is unfortunate. However, marcingy have rewritten the file usage system to be pluggable so that's another table down. There's ongoing work to convert vocabularies, text formats and contact categories to config, that's very good news. After EFQ v2 is complete, I will either work on entity storage system or the date formats issue or perhaps convert content types. One thing for sure, very busy weeks ahead.

There is a Views in Core spring end of October then BADCamp and sprints after BADCamp. During BADcamp, marcingy, Zlender and I plan to write the D8 MongoDB drivers and see whether all this works as we hope. We will have almost a month to push big things and then another four to push smaller things if they don't.

Back in Paris bojanz had this crazy plan of unifying the condition interfaces of DBTNG, EFQ and Views. This seems entirely possible, the new entity query condition interface has been copied as much as possible from the DBNTG condition interface, the difference are not significant. I wish we could use Traits. It would help a real lot. But, realistically, this is not an option when so many hosts still default to PHP 5.2 and offer 5.3 as an option only.

The big battle plan is that eventually (but before April 1) Views will use EFQ if it can and switch to a SQL backend if it can't. This would be the best outcome, given that EFQ already has a MongoDB implementation in D7 and with $and introduced in MongoDB 2.0 we can write one for the new one as well -- it would mean that most Views created would run just like that on MongoDB.

Ps. sun and beejeebus tripped on NULL not being a scalar, that was news to me as well, I have fixed the is_scalar docs on Even after this many years I am superb cautious and in awe that I can commit to

Commenting on this Story is closed.

Submitted by Anonymous on Tue, 2012-10-09 13:55.

Will D8 seriously conform to 5.2 only? If it's scheduled for release next year and expected adoption rate is late 2013 into 2014- why not push for 5.4 compatibility now? Especially if it gives Drupal framework a better edge and makes things easier to deal with.

Submitted by bojanz on Tue, 2012-10-09 14:06.

5.2 was a typo.
5.3 is the version we are depending on (the current minimum being 5.3.5), but because of hosting providers & LTS releases we haven't been able to switch to requiring PHP 5.4.

Submitted by nk on Tue, 2012-10-09 19:34.

I said many hosts default to 5.2, that's alas a truth. We indeed will require 5.3.5.

Submitted by mitchell on Wed, 2012-10-10 06:54.

Could you please elaborate a bit or provide a link for this?