|Think about Loose Coupling|
Re^7: Matching alphabetic diacritics with Perl and Postgresqlby chacham (Prior)
|on Jun 04, 2017 at 20:39 UTC||Need Help??|
moving it downward into the database is going in the wrong direction
I disagree. If anything, as the data can be manipulated from more than one location, the best place is "downward" in the rdbms. That is the one centralized location for your data. Anything else adds more code that needs to be kept in sync, reinvented, and allows for inconsistencies.
creating not only unnecessary internet communication
No matter what, you have to communicate with the database, and the communication at some point goes over the Internet anyway, so you have not saved anything. Even if you mean that the UI can handle some of the manipulation without communication, that would include none of the validations that require the database. I do not see how you are saving anything significant communication-wise.
but unnecessary communication between application and DBMS.
I fail to understand what you even mean here, sorry. Communication between the application and the database in the single most important factor in a data driven application. In many cases, the drivers automatically compress the data for you as well.
Ideally, data should be cleaned before it gets to the database.
You seem to be viewing the database as a dumb data container instead of the complex data master that it is. The database is made for this. There are keywords and functions specifically designed to help you clean and manipulate your data. To do it elsewhere first and then put it in the database, is reinventing the database outside of it.