-
Notifications
You must be signed in to change notification settings - Fork 898
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
[Bug] Null is being populated as a String if MariaDB used #5659
Comments
Hello there! Thanks for opening your first issue on this repo! Just a heads-up: Here at Backpack we use GitHub Issues only for tracking bugs. Talk about new features is also acceptable. This helps a lot in keeping our focus on improving Backpack. If you issue is not a bug/feature, please help us out by closing the issue yourself and posting in the appropriate medium (see below). If you're not sure where it fits, it's ok, a community member will probably reply to help you with that. Backpack communication channels:
Please keep in mind Backpack offers no official / paid support. Whatever help you receive here, on Gitter, Slack or Stackoverflow is thanks to our awesome awesome community members, who give up some of their time to help their peers. If you want to join our community, just start pitching in. We take pride in being a welcoming bunch. Thank you! -- |
Hey @pedja1982 I'm unable to reproduce the issue. Can you recheck on your end? If the problem continues, please let me know the steps to reproduce it. |
Hey @karandatwani92 @pedja1982 , The problem is with the database server. On MySQL it works, but on MariaDB, "NULL" appears in the input field if the field is nullable in the database. Confirmed! I have that bug as well, but so far I haven't found a solution other than not using MariaDB. MARIADB - 10.6.18-MariaDB-cll-lve - MariaDB Server MYSQL - 8.0.39-cll-lve - MySQL Community Server - GPL @tabacitu Please confirm this bug and find a solution. |
Mariadb 10.2.7 and later quote literals to distinguish them from expressions
|
Bug report
What I did
I create a model and table in DevTools that contains a nullable field, and when I open the create form in CRUD, I get the default value "NULL" as a "STRING" instead of an empty field.
What I expected to happen
I expect the input to be empty (value='').
What happened
I am getting the value NULL as a string (value='NULL').
What I've already tried to fix it
We have a
datetime
field in the database that is nullable. When I went to create, the datepicker didn't work—it didn't show up at all until I set->value('')
to empty in thedatetime_picker
. That's how we solved the issue of getting the datepicker to work, because if "null" stays as a string, it throws an error since it can't parse the date (Uncaught TypeError: defaultDate() Could not parse date parameter: NaN
). However, it's not right that we have to manually remove the string "null" from every input field that is nullable in the database.Is it a bug in the latest version of Backpack?
After I run
composer update backpack/crud
the bug... is it still there? YESBackpack, Laravel, PHP, DB version
When I run
php artisan backpack:version
the output is:The text was updated successfully, but these errors were encountered: