*bool

I’ve just switched mine off for the day :) Nah, the scope was fine; the code I pasted wasn’t what was actually used. I needed to reinterpret the variable using a logical OR prior to passing it to the function, so it wasn’t interpreted as a book.

Got it working, but wasted too much time on it 🫠

It returns index of 0, which is correct - passing the result of the findIndex (0) into a function is where javascript acts like an ass - it interprets it as false

You’re all right. UTC always for the win; always use and convert to UTC before committing.

However: pick timestamp over datetime field types when setting up the DB, is what I learned. Your field type choice matters!

True, agreed - but - inserting a value into a `datetime` field, if another application connects to the DB and attempts to apply timezone offsets to the inserted data based on its own timezone configuration, the offset won't get applied to the datetime fields, only the timestamp fields. Interesting

Hope this helps another dev out there!

Case in point: github.com/metabase/met...

I managed to lose a wordy issue submission 😭 - note to self, write it in a text editor first!

Ah - thanks Bron! It's usually something I'm doing too - glad it's not me :)

Anyone out there start their programming on either of these two machines? Might be mainly folks based in Europe back in the mid 80s :)