We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
When baking a fixture with a custom name when the name parameter exceeds 28 characters it throws an exception.
It should be using the --table parameter for the table name but after you exceed 28 characters it looks to be using the name param instead of --table
--table
bin/cake bake fixture --conditions "purchase_order_response_id IN (2325, 2323)" -r -n 10000 --table purchase_order_response_lines AldiPurchaseOrderResponseLines
throws [Cake\Database\Exception\DatabaseException] Cannot describe aldi_purchase_order_response_lines. It has 0 columns.
[Cake\Database\Exception\DatabaseException] Cannot describe aldi_purchase_order_response_lines. It has 0 columns.
# this works bin/cake bake fixture --conditions "purchase_order_response_id IN (2325, 2323)" -r -n 10000 --table purchase_order_response_lines CustomNameIsLimitedToThisLen
5.0.7
8.1.28
The text was updated successfully, but these errors were encountered:
Are you using postgres by any chance?
Sorry, something went wrong.
No branches or pull requests
Description
When baking a fixture with a custom name when the name parameter exceeds 28 characters it throws an exception.
It should be using the
--table
parameter for the table name but after you exceed 28 characters it looks to be using the name param instead of--table
bin/cake bake fixture --conditions "purchase_order_response_id IN (2325, 2323)" -r -n 10000 --table purchase_order_response_lines AldiPurchaseOrderResponseLines
throws
[Cake\Database\Exception\DatabaseException] Cannot describe aldi_purchase_order_response_lines. It has 0 columns.
CakePHP Version
5.0.7
PHP Version
8.1.28
The text was updated successfully, but these errors were encountered: