Andreas Eberhart
Andreas Eberhart
we can CRUD uuid and bigserial vector can be displayed but not edited
re-applying $eval() to the result of $string manages to parse the illegal JSON this expression causes an error though: {"te\nst":"te\nst"} ~> |$|{}| Expected valid string character at 1:5
solution would be to move "firstlogin":$now() from on-login to the on-create trigger
not really that important
we are using the default react admin export feature https://marmelab.com/react-admin/List.html#exporter guess taking the projected columns into account would be possible (asked a question in the RA discord) not sure about...
opened an issue with react admin: https://github.com/marmelab/react-admin/issues/9986
We decided to stick with the default logic offered by the underlying framework. There are simply too many export options which make it quite complex. As a workaround, you can...
should also be applied to choice handler jsonata
we filter those columns until we find another solution (implicit transformation to replace . or a custom input that can access field names with dot)
we still have an issue when editing toolbar: Warning: Maximum update depth exceeded. This can happen when a component calls setState inside useEffect, but useEffect either doesn't have a dependency...