Cannot test migrations using modular approach with store_date_time_values_as_text: true about drift HOT 4 CLOSED

Thanks for the report! The schema.json file should have a top-level options key containing whether store_date_time_values_as_text was enabled for the particular schema. Is that not included in your schema?

from drift.

Oh wait I think I know what the problem is here... Does this work?

targets:
  $default:
    builders:
      drift_dev:
        # Disable the default builder in favor of the modular builders configured
        # below.
        enabled: false
        options:
          store_date_time_values_as_text: true

      drift_dev:analyzer:
        enabled: true
        options: &options
          store_date_time_values_as_text: true
          named_parameters: true
          sql:
            dialect: sqlite
            options:
              version: "3.45.3"
              modules: [fts5]
      drift_dev:modular:
        enabled: true
        options: *options

We're parsing the build.yaml to check the options from the CLI, that logic doesn't properly account for the other builders.

from drift.

Hi @simolus3,

Ahhhh yes, thank you so much, that is the problem, indeed. The schema was building with the key set to false. Adding it in properly to the build.yaml causes it to be set to true. Oh man. Words cannot express my gratitude! Thank you!

Sarah

from drift.

No problem, and thanks for the report! The underlying problem has been fixed in f129675, so the workaround will stop being necessary with the next drift release.

from drift.