>From: Vincent Veyron Sent: Wednesday, May 04, 2016 3:35 PM >I write management applications for businesses, and give _a lot_ of care to the database structure. >I find that the number of lines of code that need to be written is strictly inversely correlated to the >appropriateness of the database design (meaning that the better the database structure, the lesser >code is needed). >Knowing about the many fine functions Postgresql offers also helps, of course. > Bien à vous, Vincent Veyron An inverse corollary is also true, imo: encountering demands for exotic, wild functions, cursors and code constructs (like triggers calling triggers or frankly, triggers in general), is nearly always an indication of poor database design. I'm not talking about windowing functions or json or CTEs, btw. Postgres and mysql have piles and piles of functions that I will never use and can't even imagine scenarios in which to use them. So I agree 100% - it's all about the database (design). BTW, I'm currently designing/building OLTP databases for use in genomics research (using Postgres)...that's big data...where there is zero tolerance for slack db design that could cause scalability or performance issues. My stored functions are...relatively simple. Mike Sofen (San Diego, CA USA) -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
