phalcon | phalcon项目结构 | Model View Controller library

Your issue is only partially related to Phalcon. The error itself is a sub error of PHP directly. https://3v4l.org/F8EfM

Phalcon 5 has a number of backwards incompatible changes. Most prominent is all the classes in the base Phalcon namespace were moved to more accurate locations.

• Phalcon\Config -> Phalcon\Config\Config
• Phalcon\Di -> Phalcon\Di\Di

Etc

Check the release notes at https://github.com/phalcon/cphalcon/blob/master/CHANGELOG-5.0.md for specific changes.

The documentation for Phalcon's Request object explains that it is primarily a wrapper around PHP's native "superglobals", such as $_POST. In particular:

The $_POST superglobal contains an associative array that contains the variables passed to the current script via the HTTP POST method when using application/x-www-form-urlencoded or multipart/form-data as the HTTP Content-Type in the request. You can retrieve the data stored in the array by calling the getPost() method

Note that important caveat that this array is only populated when using two specific content types - specifically, the two content types that browsers use when submitting HTML forms. Form processing is the original task PHP was built for, and it can handle things like file uploads; but it doesn't natively do anything with JSON, XML, or other input types.

(As an aside, that documentation is subtly wrong: despite its name, $_POST will be populated for any HTTP method with an appropriate request body, e.g. PUT, just as $_GET is populated even when the method is POST.)

In your request, you're not using those content types, because you're posting a JSON string, so PHP doesn't populate $_POST, and Phalcon doesn't have anything to read with getPost().

As you've discovered, there's a separate method which allows you to decode the JSON body to a PHP array:

getJsonRawBody(): Gets decoded JSON HTTP raw request body

There's no mention of JSON at all in the Phalcon 3.4 Request documentation so I'm not sure whether that functionality has changed, you've misremembered, or you were using some additional plugin or configuration.

The REST tutorial shows usage of getJsonRawBody() in both the 5.0 version and the 3.4 version.

if you created your project using phalcon's cli devtools then the session service would be created by default in app/config/services.php

that being said in your controller when you access the instance's property session aka $this->session this would look for a service called session and by default it would setup session using file adapter and starts it and $this->session would return an instance of Phalcon\Session\Manager

Can you just remove new and try?

An explanation...

Your faster query can find the 10 rows before looking in documents. So, it needs only 10 probes into that table.

In the original query, the Optimizer was not too smart. It planned to execute the query as if there were no LIMIT. Instead, it decided to optimizer the join to documents by fetching the entire table into the "join buffer" into RAM and built a hash index into it. While this would help some queries like yours, it was a big waste for the mere 10 rows that you needed.

So, your reformulation convinced the Optimizer to do it a better way.

If you had needed only one column from d, there is another way:

The "72" in "php72-phalcon" refers to PHP 7.2, but you are using PHP 7.4, so it's not going to be compatible - extensions need to be built against the correct version of PHP in order to run. The version of Phalcon it's installing (3.4.2) is also out of date, because that was the last version supported on that version of PHP.

The instructions for installing Phalcon 4.0 on a Mac are here: https://docs.phalcon.io/4.0/en/installation#macos

They refer to a different homebrew repository:

The issue was that I did not install phalconphp dev tools properly in the first place. I had multiple versions of php installed on my machine. So I uninstalled all unwanted versions of php and stuck with php7.2 and reinstalled phalcon and the dev-tools and everything worked fine.

Leaving it out there for someone in the future.

The docs are incorrect at the moment and reference the old dependencies required.

In case that you want to use Guzzle the following should work: