You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using a repositories design patter, we are having criteria that build a query based on the data in the specific criteria,
we don't check on this level agains existing columns. I believe array_unique could be executed on the columns just before sending a query. It does not affect any column select aliases.
Can anyone please confirm that this was indeed resolved? I can't seem to find the changes in the production code. It seems that the changes went into a fork.
Description:
For aggregate selects it's forbidden to have a duplicated column names.
[2020-09-01 18:59:47] local.ERROR: SQLSTATE[42S21]: Column already exists: 1060 Duplicate column name 'description' (SQL: ... at /var/www/html/laravel/vendor/laravel/framework/src/Illuminate/Database/Connection.php:671)
Steps To Reproduce:
Execute this query.
Motivation
When using a repositories design patter, we are having criteria that build a query based on the data in the specific criteria,
we don't check on this level agains existing columns. I believe array_unique could be executed on the columns just before sending a query. It does not affect any column select aliases.
#34097
The text was updated successfully, but these errors were encountered: