Skip to content
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

5.2.40 breaks database queries on HHVM #14426

Closed
iangcarroll opened this issue Jul 22, 2016 · 8 comments
Closed

5.2.40 breaks database queries on HHVM #14426

iangcarroll opened this issue Jul 22, 2016 · 8 comments

Comments

@iangcarroll
Copy link
Contributor

iangcarroll commented Jul 22, 2016

Upgraded to 5.2.41 and now any database query causes the following error to be thrown on HHVM:

SQLSTATE[HY000]: General error: user-supplied class does not have a constructor, use NULL for the ctor_params parameter, or simply omit it (SQL: [...])

Looks like 5.2.40 introduced the error: https://laracasts.com/discuss/channels/forge/sqlstatehy000-general-error-user-supplied-class-does-not-have-a-constructor

@GrahamCampbell
Copy link
Member

What HHVM version please? If the latest, please report this bug to facebook.

@iangcarroll
Copy link
Contributor Author

We're on 3.12-lts.

@iangcarroll
Copy link
Contributor Author

Looks like #14052 is the reason this is happening.

@GrahamCampbell
Copy link
Member

Still facebook's fault for not being php compatible, but re-opening this since we should probably mitigate this ourselves.

@vlakoff
Copy link
Contributor

vlakoff commented Jul 22, 2016

I have submitted a fix for this: #14429.

@vlakoff
Copy link
Contributor

vlakoff commented Jul 22, 2016

HHVM isn't that wrong, as using an empty array is not "documented", in the error message.

Still, it is an incompatibility with PHP.

@GrahamCampbell
Copy link
Member

HHVM is wrong if it's not exactly the same as PHP. PHP is the definition of being correct.

@vlakoff
Copy link
Contributor

vlakoff commented Aug 8, 2016

Fixed by #14429 and Laravel 5.2.42 has been released, so this issue can be closed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants