Michael Markl

If you use `CurrentTimestamp` instead of `CurrentDateTime`, the error still occurs: ```kt import org.jetbrains.exposed.sql.javatime.CurrentTimestamp val createdAt = timestamp("created_at").defaultExpression(CurrentTimestamp()) ``` This is due to `CurrentTimestamp` not inheriting from Function but only...

@bog-walk I opened an issue: https://youtrack.jetbrains.com/issue/EXPOSED-112/SchemaUtils.addMissingColumnsStatements-fails-to-compare-timestamp-column-with-default-CURRENTTIMESTAMP-for-Postgresql

I think we should add least add a disclaimer at the top of the file *now* that explains which functions are copy-pasted, which ones are adjusted, etc. Otherwise, we're building...

I think we should do security tasks even if the customer has not required it. This would be a great security improvement for nürnberg; for bayern it's a bit harder...

@ztefanie No there was no input from nuernberg about this. I don't know the ending.

Yes, thank you!

I don't think this should be high prio right now. Data quality assurance *should* be done by regions / freinet / LBE themselves. Of course it would still be worth...

The verbosity has been reduced by @maxammann by just sending the exit status to ~entitlementcard-cert. 🎉 Maybe we want to have some summary of the imports nevertheless. It's (very) low...

yup :D my reaction was to write an issue, yours was to fix the problem :D

What are the pain points with the current setup?