Fatal error: Invalid default value for 'UpdatedDate' - On Lute installation about lute

[jzohrab]

Thanks HF for the note! Hopefully this is a quick fix, looking into it.

You still need the migration, even on a fresh db install. That migration hasn't been made permanent in the baseline db.

[jzohrab]

I believe I'm off by 1 second. Per this SO post which points to the docs:

the range for TIMESTAMP values is '1970-01-01 00:00:01.000000' to '2038-01-19 03:14:07.999999'

That migration has

alter table textstatscache
add column UpdatedDate timestamp default '1970-01-01 00:00:00'
after TxID;

alter table textstatscache
add column LastParse timestamp default '1970-01-01 00:00:00'
after TxID;

Fixing that migration in master.

[jzohrab]

I changed these columns to be NULLable, which makes more sense, rather than putting in a dubious date.

Fixed in master, but I'll leave this issue open until a) @HugoFara gets a chance to test it out, and b) I've created a new release with this hotfix.

Thanks Hugo! (I'll see about setting up a GitHub action to test this in an Ubuntu environment, right now I'm just testing on my Mac, which isn't good enough.)

[jzohrab]

GitHub CI set up, and would have caught this issue :-( Alas. Issue is fixed in master as well.

[HugoFara]

Hi! I pulled your latest version today, and the issue does not longer appear so well done. Ironically enough, you signaled me this exact same bug for LWT last month (hugofara/lwt#78) 😆

Have a nice day!