From: | Jasmin Dizdarevic <jasmin(dot)dizdarevic(at)gmail(dot)com> |
---|---|
To: | Dave Page <dpage(at)pgadmin(dot)org> |
Cc: | Magnus Hagander <magnus(at)hagander(dot)net>, pgadmin-hackers(at)postgresql(dot)org |
Subject: | Re: Step ordering pgAgent |
Date: | 2011-01-04 17:22:10 |
Message-ID: | AANLkTindXK2Uq+OvUv_YnH=f6qfK_-t12oawTW6m9ZXk@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers |
I'm with you about the ease of use, but I don't agree that triggers and jobs
are so near to each other. In my opinion there is at least a functional
difference: Triggers are needed on application level and are maintained by a
developer. Jobs are helpers for database admins to keep the database "clean"
or to update data (data cumulation, definition updates,...).
But we can discuss this topic later, if it's requested by more users.
Jasmin
2011/1/3 Dave Page <dpage(at)pgadmin(dot)org>
> On Mon, Jan 3, 2011 at 6:08 PM, Jasmin Dizdarevic
> <jasmin(dot)dizdarevic(at)gmail(dot)com> wrote:
> > Why is the trigger consistency so important for you?
>
> Consistency is critical to ease of use in any kind of application. If
> there are different techniques used to accomplish similar tasks, then
> it reduces the intuitiveness of the user interface which can lead to
> user confusion.
>
> --
> Dave Page
> Blog: http://pgsnake.blogspot.com
> Twitter: @pgsnake
>
> EnterpriseDB UK: http://www.enterprisedb.com
> The Enterprise PostgreSQL Company
>
From | Date | Subject | |
---|---|---|---|
Next Message | Ashesh Vashi | 2011-01-04 17:46:40 | Re: pgAdmin III commit: Pull keywords dynamically from PostgreSQL headers |
Previous Message | Dave Page | 2011-01-04 16:55:26 | pgAdmin III commit: Fix a rendering issue in the SQL text box on Mac, w |