- Issue created by @claudiu.cristea
- @claudiucristea opened merge request.
- Issue was unassigned.
- Status changed to Needs review
almost 2 years ago 10:36am 22 January 2023 - First commit to issue fork.
-
marcoscano →
committed 5d6f7577 on 8.x-2.x authored by
claudiu.cristea →
Issue #3335488 by claudiu.cristea, marcoscano: Table entity string IDs...
-
marcoscano →
committed 5d6f7577 on 8.x-2.x authored by
claudiu.cristea →
- Status changed to Fixed
almost 2 years ago 4:07pm 23 January 2023 - 🇪🇸Spain marcoscano Barcelona, Spain
Supporting entity reference fields OOTB is a basic feature, so I'd classify this as a bug. Thanks for filing the ticket and providing the MR. (special thanks for the update tests! 👏 )
Automatically closed - issue fixed for 2 weeks with no activity.
- Status changed to Fixed
almost 2 years ago 2:52pm 7 February 2023 - 🇧🇬Bulgaria pfrenssen Sofia
This is causing a fatal error when running the update hook on sites that have been using Entity Usage since version 2.0-alpha4 or older. In those early versions the
target_id_string
column still allowedNULL
values. Now the table is updated to mark the column asNOT NULL
which throws a fatal error when theNULL
values are encountered. Created followup issue to address this: 🐛 Fatal database error when updating to 2.0-beta9: "Invalid use of NULL value" Fixed .