NULL is not considered null

Created on 31 August 2023, over 1 year ago

Problem/Motivation

When using csv sources, I have NULL columns in some rows, but those are imported as NULL string even with skip_if_empty.
I think the source should take care of that.

Steps to reproduce

TBD

Proposed resolution

TBD

Remaining tasks

TBD

User interface changes

TBD

API changes

TBD

Data model changes

TBD

🐛 Bug report
Status

Closed: works as designed

Version

3.0

Component

Code

Created by

🇪🇸Spain penyaskito Seville 💃, Spain 🇪🇸, UTC+2 🇪🇺

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @penyaskito
  • Status changed to Needs review over 1 year ago
  • Open in Jenkins → Open on Drupal.org →
    Core: 9.5.x + Environment: PHP 7.4 & MySQL 8
    last update over 1 year ago
    16 pass
  • 🇪🇸Spain penyaskito Seville 💃, Spain 🇪🇸, UTC+2 🇪🇺

    Attached patch for triggering discussion.

  • heddn Nicaragua

    the module is a non opinionated CVS source plugin. this could easily be added in one off situations. perhaps that would be better then changing this on folks who maybe already depend on this "feature".

  • Status changed to Closed: works as designed over 1 year ago
  • 🇪🇸Spain penyaskito Seville 💃, Spain 🇪🇸, UTC+2 🇪🇺

    Most db export tools use the string "NULL" for NULL as default, even if they provide extended options to change that (mysqladmin and some others I'm aware). Even if this would be nice, we can always use hook_migrate_prepare_row.

    I understand if I'm migrating my php docs site, treating "NULL" as NULL can be an issue. I don't want to generate another Norway problem.

Production build 0.71.5 2024