moor file doesn't support generated columns or json_extract

[thachnb85]

I have moor file with simple table:

CREATE TABLE t1(
   a INTEGER PRIMARY KEY,
   b INT,
   c TEXT,
   d INT GENERATED ALWAYS AS (a*abs(b)) VIRTUAL,
   e TEXT GENERATED ALWAYS AS (substr(c,b,b+1)) STORED
);

When I ran flutter pub run build_runner build

✗ [INFO] Generating build script...
[INFO] Generating build script completed, took 810ms

[INFO] Initializing inputs
[INFO] Reading cached asset graph...
[INFO] Reading cached asset graph completed, took 365ms

[INFO] Checking for updates since last build...
[INFO] Checking for updates since last build completed, took 1.4s

[INFO] Running build...
[WARNING] built_value_generator:built_value on lib/test.dart:
Your current `analyzer` version may not fully support your current SDK version.

Please try upgrading to the latest `analyzer` by running `flutter packages upgrade`.

Analyzer language version: 2.12.0
SDK language version: 2.13.0

If you are getting this message and have the latest analyzer please file
an issue at https://github.com/dart-lang/sdk/issues/new with the title
"No published analyzer available for language version 2.13.0".
Please search the issue tracker first and thumbs up and/or subscribe to
existing issues if present to avoid duplicates.

[INFO] 1.5s elapsed, 0/16 actions completed.
[INFO] 2.5s elapsed, 0/16 actions completed.
[INFO] 3.5s elapsed, 0/16 actions completed.
[INFO] 4.6s elapsed, 0/16 actions completed.
[INFO] 5.7s elapsed, 0/16 actions completed.
[INFO] 21.7s elapsed, 0/16 actions completed.
[WARNING] No actions completed for 21.7s, waiting on:
  - built_value_generator:built_value on lib/test.dart

[INFO] 22.7s elapsed, 0/16 actions completed.
[INFO] 23.9s elapsed, 15/31 actions completed.
[INFO] 24.9s elapsed, 15/31 actions completed.
[INFO] 26.0s elapsed, 25/39 actions completed.
[INFO] 27.1s elapsed, 36/52 actions completed.
[INFO] 28.2s elapsed, 53/67 actions completed.
[INFO] 29.3s elapsed, 74/88 actions completed.
[INFO] 30.4s elapsed, 91/107 actions completed.
[INFO] 31.5s elapsed, 109/112 actions completed.
[INFO] 32.5s elapsed, 124/140 actions completed.
[INFO] 33.5s elapsed, 150/166 actions completed.
[INFO] 34.5s elapsed, 178/193 actions completed.
[WARNING] moor_generator:moor_generator on lib/services/data_manager/database.dart:
There were some errors while running moor_generator on package:test/services/data_manager/database.dart:
[WARNING] moor_generator:moor_generator on lib/services/data_manager/database.dart:
line 5, column 10: Expected closing parenthesis
  ╷
5 │    d INT GENERATED ALWAYS AS (a*abs(b)) VIRTUAL,
  │          ^^^^^^^^^
  ╵
[WARNING] moor_generator:moor_generator on lib/services/data_manager/database.dart:
There were some errors while running moor_generator on package:test/services/data_manager/database.dart:
[WARNING] moor_generator:moor_generator on lib/services/data_manager/database.dart:
line 5, column 10: Expected closing parenthesis
  ╷
5 │    d INT GENERATED ALWAYS AS (a*abs(b)) VIRTUAL,
  │          ^^^^^^^^^
  ╵
[INFO] Running build completed, took 36.2s

[INFO] Caching finalized dependency graph...
[INFO] Caching finalized dependency graph completed, took 282ms

[INFO] Succeeded after 36.5s with 2 outputs (225 actions)

with another database.moor file:

create table todos (
  title TEXT,
  idx text generated always as (json_extract(json_data, '$.index')) VIRTUAL,
  json_data TEXT
);

it also doesn't work. Probably need support from next version or moor? Thank you.

[simolus3]

We don't yet support generated columns (even though it doesn't sound like that much work in the generator, feel free to open a feature request issue for that).
Json functions are supported, but they are disabled by default. This is because not all sqlite3 installations come with that module, so we wouldn't want to assume it exists when analyzing queries. You can change the assumed environment as explained here.

[thachnb85]

Thank you for your reply, if so can we create the table using customStatement to create a table with generated columns?

[simolus3]

Yeah, that should work as a workaround.