Talk comments

Very good presentation. Well thought out, concise and well presented. This is the fist time I've seen Matt speak, I know it won't be the last.

Anonymous at 15:39 on 21 Oct 2015

Quite interesting, but also agree with the others - a slower pace would have been helpful

Geri I Jennings at 15:32 on 21 Oct 2015

Great discussion of what's to come in MySQL 5.7. Looking forward to testing it out!

I'm a MySQL junkie. This talk about 5.7 in general and the JSON type and "functional indexes" in particular was the highlight of zendcon so far.

Good talk. Many questions from the audience and Morgan had no problem answering any of them.

Anonymous at 15:22 on 21 Oct 2015

Per your request. I would nix the live coding, i find it quite distracting and prefer to see the finished code - it also reduces the changes for errors. Also, i would talk a little slower and practice to check the timing. The talk ran 30 minutes short.

Some feedback I received from people around me was:
They were completely lost as they had never done any async before, so perhaps spend some time on the basics of how the async problem is solved: ie> select polling, io etc.

I really enjoyed learning about libraries that I never heard of. I also really enjoyed your accent and story time.

You could have slowed the pace a tad, and used your extra time for Q&A instead of ending 25 min early. Great material though.

Thanks, Chris. Very interesting talk. Would appreciate if you would slow down. Would also have been good to start with a real use case for WHY you want to use async with PHP.

Anonymous at 15:15 on 21 Oct 2015

Although the talk was helpful in understanding REST and the way HTTP requests work and should be interpreted, the information given was misleading. Currently, Doctrine's IBM DB2 driver is community driven and not fully complete. For example, the doModifyLimitQuery() function does not pass the ORDER BY statement to the OVER() function in the SQL. This means that the pagination cannot be ordered (see https://github.com/doctrine/dbal/pull/839 for more information). There is even a comment in the source code describing the issue.

It is important to understand that the DB Connect and Doctrine Connect functionality is still experimental and should be used with caution and understanding for the underlying functionality. I feel like some are going to go home and try Apigility on their boxes and find out that it doesn't work the way described, or at least not as easily as portrayed. This may lead them to giving up on Apigility as a solution. Please keep this information in mind, because Apigility is a wonderful tool and can help abstract the DB2 database and make it more accessible to modern techniques.

it helps me to understand what requests are sent because many specific examples of request of Apigility.