Re: Prepping to break every past release...
От | Dave Page |
---|---|
Тема | Re: Prepping to break every past release... |
Дата | |
Msg-id | 937d27e10903041332s19f48f73l505f4321ff441116@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Prepping to break every past release... (Bill Moran <wmoran@potentialtech.com>) |
Список | pgsql-hackers |
On Wed, Mar 4, 2009 at 9:24 PM, Bill Moran <wmoran@potentialtech.com> wrote: > In response to Dave Page <dpage@pgadmin.org>: > > Don't those folks have to tweak their code with each new release anyway? > Because those tables are constantly changing? I know we hit problems > with the way triggers are stored in 8.3 compared to earlier versions. pg_trigger.tgenabled changed type in 8.3. That's an extremely rare kind of change however - for example, triggers havent really changed since at least 7.3 aside from that. The sort of change JD seems to be suggesting /could/ involve rewriting virtually every query in pgAdmin, as well as surrounding code. > Granted, a sweeping change will necessitate a much larger tweak than > a few changed columns, but the long-term benefit should be cleaner > client code. Only if your app only targets one version of the server. -- Dave Page EnterpriseDB UK: http://www.enterprisedb.com
В списке pgsql-hackers по дате отправления: