2009/3/9 Christian Schröder <cs@xxxxxxxxx>: > > I understand why this is advisable; however, something inside me hates the > idea to put this kind of database specific stuff inside an application. How > about portability? Why does the application developer have to know about > database internals? He knows sql, that should be sufficient. > I have the (maybe naive) idea of a clear separation of database > administration (including performance tuning) and application development. > Is this idea completely wrong? > and it is a good idea, especially since you might want to consider heterogeneous DB target. Personally , I put views in DB, and wrap it in a nice LIB. That also means, that I can change things in one place. Just make sure, that you have proper test harness around that sort of LIB, and everything should be okay. I've seen projects in the past, where authors were trying to make queries work on mysql/psql - and that just doesn't fly with me. -- GJ -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
