On 2012-05-03, Chrishelring <christianhelring@xxxxxxxxx> wrote: > Maybe I should clarify what I mean. > > I have a db (postgresql 8.4.1 with a postGIS spatial extension) with about > 200+ tables in it. Some of them is supposed to be updated using an > application what requres that some of the columns are in uppercase (a > leftover from Oracle I suppose) but the main application that uses these > tables requres that the columns are in lowercase. I had an idea that using a > trigger I could chance the columns from lowercase to uppercase before > updating /changing the tables and after the update chance them back to > lowercase. Is that possible and how do I do that? No, you could try fashioning an updatable view in a different schema and exploiting schema search path such the main application sees one version and the legacy application sees the other. this means writing a view to handle selects, and do instead rules for updates and deletes. shema search path can be defaulted on a per-user basis so if one of the applications always uses a distincr username for the databse connection this can be implemented in a way that's transparent -- ⚂⚃ 100% natural -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
