eMerzh

I think, some of the issues here is that first nextcloud tries to be compatible with any managed / mutualized hosting.

They also treat every "module"/"apps" whatever you call it, as completely distinct spa without proving much of a sdk/framework. Which mean each app, add is own deps, manage is own build, etc...

Also don't forget that app can even be a part of a screen not the whole thing

would be interesting to find some mutualisation with umap-project.org ... or at least become a friend project :)

sorry but that is simply not true... I think there are areas where it can be, probably those more remote, or where there are less contributors but at least in western europe, the map is built and maintained by individuals like me. Maybe helped with external datas but still carefully handpicked and integrated by individuals

Nice I was looking to test this at work... But not sure if login does not work for me (and my buddy) or something else.... But we kept beeing redirected to the login button

No errors ...didnt type anything funky... Numbers ....

Yeah but what it state here is that if you want to add a limit on field size, then add a check constraint... Much easier to deal with than changing type

It's me or a lot of those points don't explain anything? I totally get they don't want to open source it as a company but don't try to give false reason for it.

It's not because it's open source that you can't have quality, central design, or good documentation.

I've used the mysql FDW for a project at work, it was really helpfull. We've replaced an old "ETL" using a bunch of hard to maintain scripts to mysql_fdw and some materialized view.

It was easier for us because it helps write maintainable logic, you can easily sync multiple databases, multiple servers, without much changes.

A few things to note though:

- we had issues with 0000-00-00 dates that are valid in mysql but not in postgres. So we had to write include a convertion in plsql into the mat view.

- We stumble upon a bug in mysql_fdw, in which the selected row is skipped if the size of a column exceed a given size. This is reaaaaally hard to catch and really bad experience as you won't get any error, notice or warning.

- we had trouble with a few type casting like json and others.