-
-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot use a scalar value as an array #11466
Comments
I have a similar issue. The same error is manifested when calling \Phalcon\Db\Adapter\Pdo::connect() with a connection configuration containing:
In fact, as long as options key is present in the config, the error does not go away. Stack trace:
|
@rlaffers Could you please provide script to reproduce? |
@sergeyklay got exactly the same issue after trying to update from 2.0.13 to 3.2.2 (tried also 3.2.3, 3.1.x etc) both building and getting debian package from Packagecloud . The old way of setting default fetch mode (via passing options to Postgresql adapter constructructor as an example) is not working for some reason :( Just the same error
The strange thing is that it was thrown while i was doing model->save(); It also seems that the behavior "test if there's a record and create if there none or update existing" not working as it did before :( We were just saving models previously on 2.0.13 without checking existence and it was OK, but now it just throws an error |
@lightindigo Which database do you use? |
Hi, this bug is still active on phalcon 4.2.1 I found that:
|
@Druid33 Could you please open a new issue |
I did: #14330 |
Problem:
Cannot use a scalar value as an array in phalcon/mvc/model.zep on line 1070
which produces another error "You cannot serialize or unserialize PDO instances"
if
num
is scalar then fetchOne returns an object. If database returns object then my default fetch mode is FETCH_OBJ.If I comment this option, I get no error.
The text was updated successfully, but these errors were encountered: