Skip to main content

Disco v0.2.0 is out

This blog post might be outdated!
This blog post was published more than one year ago and might be outdated!
· 2 min read
Stephan Hochdörfer
Head of IT Business Operations

Last week when I was in Miami to speak at the SunshinePHP 2016 conference I took the time to prepare the version 0.2.0 release of our PHP DI container called Disco. This release features 2 important changes which I want to highlight in this blog post.

Using Doctrine, ramsey/uuid-doctrine and willdurand/hateoas

This blog post might be outdated!
This blog post was published more than one year ago and might be outdated!
· 2 min read
Stephan Hochdörfer
Head of IT Business Operations

Recently I experimented a bit with Doctrine ORM and the willdurand/Hateoas library to expose my Doctrine objects via an HATEOAS api which luckily is a fairly trivial thing to do. All you need to do is set up the Hateoas serializer and call the respective serialize() method passing your Doctrine object as well the serialization type:

Increase the Speed of Reading XLSX Files

This blog post might be outdated!
This blog post was published more than one year ago and might be outdated!
· 2 min read
Florian Horn
Business Analyst Digital Sales

A few month ago, I wrote an article about some PHPExcel performance tweaks. Sadly we encountered some nasty memory exhaustion issues while reading big XLSX files with PHPExcel. The issues does not occur directly in PHPExcel, furthermore the current PHP process is killed in the SimpleXML/LibXml library execution silently, without any exception or error notification.

Vagrant 1.8 supports Linked Clones

This blog post might be outdated!
This blog post was published more than one year ago and might be outdated!
· One min read
Stephan Hochdörfer
Head of IT Business Operations

When browsing the Vagrant 1.8 Changelog file I realized that the latest Vagrant version supports Linked Clones which according to the Changelog means that imports during the vagrant up process will run much faster than before. Since it did not work out-of-the-box for me, I had to dig deep in the Vagrant documentation to figure out that you need to explicitly enable the feature. Simply add the following lines to your Vagrant configuration and your vagrant up command will probably run faster than ever:

Vagrant 1.8 Upgrade Issues

This blog post might be outdated!
This blog post was published more than one year ago and might be outdated!
· 2 min read
Stephan Hochdörfer
Head of IT Business Operations

Earlier this morning Mitchell Hashimoto released version 1.8 of Vagrant. I immediately upgraded and quickly hit a problem. After running vagrant up I got this error message:

PostgreSQL - Count() Performance Boost

This blog post might be outdated!
This blog post was published more than one year ago and might be outdated!
· 4 min read
Florian Horn
Business Analyst Digital Sales

Counting is a slow measure in Postgresql, and it is even slower with a lot of data and complex statements. This issue is related with the kind of how the data consistency is implemented. As a result Postgresql must check the visiblity of all rows first and so it has to iterate over them all.