[dsego]

There are annoying show-stopper bugs that the developer refuses to fix, like this one for not being able to set options for null/empty values when importing data from csv ( https://github.com/jakob/Postico/issues/406). Or issues importing CSVs exported by Postico itself, that seems like a pretty basic requirement. On the other hand, even though DBeaver has an annoying and ugly UX (as any other 90s Java software) and is full of warts (eg not showing a unique key constraint in a postgres table, which was visible in Postico), it somehow feels more substantial.

[pensatoio]

An empty string "bug" report is not a great example of a show-stopper since it's arguably a terrible way to use posgres.

[dsego]

It's not an empty string bug report. It's not being able to import CSVs with blank values, because postico interprets them as null, and no way to remap the values. Depending on your workflow, this could be a serious hinderance.