Fix zend framework 2 db multi queries should default to min/max 1/500

[gerardroche]

See #874 (comment)

[msmith-techempower]

This looks fine, but there are still some warnings in the travis output: https://travis-ci.org/TechEmpower/FrameworkBenchmarks/jobs/39345008

I can merge now, or you can commit more fixes.

[msmith-techempower]

This looks fine, but there are still some warnings in the travis output: https://travis-ci.org/TechEmpower/FrameworkBenchmarks/jobs/39345008

I can merge now, or you can commit more fixes.

[gerardroche]

What exactly are the warnings for? My guess is that it's because the json should have integer values rather than string integers. If this the case I say merge it as is because this is how 90+% of zf users would encode json using the framework.

The Zend Framework version 1of these benchmarks displays the same watnings too, so same as above. #874

[gerardroche]

What exactly are the warnings for? My guess is that it's because the json should have integer values rather than string integers. If this the case I say merge it as is because this is how 90+% of zf users would encode json using the framework.

The Zend Framework version 1of these benchmarks displays the same watnings too, so same as above. #874

[hamiltont]

My guess is that it's because the json should have integer values rather than string integers

Correct, that's the only thing it's warning about. This LGTM

[hamiltont]

My guess is that it's because the json should have integer values rather than string integers

Correct, that's the only thing it's warning about. This LGTM

[hamiltont]

For what it's worth, the warning is not being issued because TFB developers have some preferred representation of numbers in JSON - it's warning you because this might cause your framework to bump up against the physical limits of the networking hardware, as the quotation marks consume a few extra bytes per request.

If this is the natural JSON representation for zend I would totally ignore these warnings, unless Zend gets the top 2 or 3 spot in the preview data for the next round (then definitely optimize it and go for one!)

[hamiltont]

For what it's worth, the warning is not being issued because TFB developers have some preferred representation of numbers in JSON - it's warning you because this might cause your framework to bump up against the physical limits of the networking hardware, as the quotation marks consume a few extra bytes per request.

If this is the natural JSON representation for zend I would totally ignore these warnings, unless Zend gets the top 2 or 3 spot in the preview data for the next round (then definitely optimize it and go for one!)

[hamiltont]

LGTM, thanks again @gerardroche !

[hamiltont]

LGTM, thanks again @gerardroche !