Sylius: Taxon View, query broken on Postgres

[acornforth]

Not sure if this is an issue with the plugin skeleton, or with the sylius codebase itself..

Our sylius set-up was done by a Sylius partner, and uses the bitbag elastic search plugin. As a result, i have not seen this bug in our main sylius installation, but this issue report may rightfully belong in the main repo.

I am reporting it here, since it is with the plugin skeleton that I have seen the issue.

Steps to reproduce

I started again with a fresh create-project.

set the doctrine config to use a pgsql dsn

follow steps exactly as per readme.

click the 'dresses' menu item in the demo store.

if you have successfully replicated my scenario, you should now see the following error:

[LeoHugues]

I have same issue since yesterday, maybe after I do "composer update sylius/sylius --with-all-dependencies"

Solved with :
https://stackoverflow.com/questions/36829911/how-to-resolve-order-by-clause-is-not-in-select-list-caused-mysql-5-7-with-sel/39353160

[acornforth]

@LeoHugues
that is a reasonable workaround for people running mysql, postgres users will not have much luck with that though unfortunately...

[antiseptikk]

I have same issue for me, after composer update sylius/sylius --with-all-dependencies

[acornforth]

I have run a composer update on my plugin development project last week and this issue has gone away... It appears to have been fixed in a recent update! If anyone can confirm that, this issue can probably be closed !

[Zales0123]

@LeoHugues @antiseptikk can you check it out as well? It would be great if it's fixed :D 💃

[antiseptikk]

Hi @Zales0123,
I tried with Sylius 1.7.0@alpha and mysql percona:5.7 docker image (from sylius-standard repo) and the bug is still there.

I fix this by adding command: mysqld --sql_mode="" into the docker-compose.yml file but i don't think is the best solution.

I think the problem is here :
https://github.com/Sylius/Sylius/blob/master/src/Sylius/Bundle/CoreBundle/Doctrine/ORM/ProductRepository.php#L74

But I haven't found a solution to propose yet. Any idea ? :)

[Zales0123]

Hello guys, sorry for such a long response time 🖖

We're currently working on better support for Postgres. Stay tuned, I hope we'll be able to do something with this issue in the nearest future.

[stale[bot]]

This issue has been automatically marked as stale because it has not had any recent activity. It will be closed in a week if no further activity occurs. Thank you for your contributions.