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 "cle
On Mon, Jan 3, 2011 at 6:08 PM, Jasmin Dizdarevic
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 inte
On Mon, Jan 3, 2011 at 19:08, Jasmin Dizdarevic
wrote:
> Why is the trigger consistency so important for you? In my opinion triggers
> have nothing to do with job steps. Other agent implementations (e.g.
> sqlagent) also provides the ability to reorder steps.
> Magnus, you're right there is no bug
Why is the trigger consistency so important for you? In my opinion triggers
have nothing to do with job steps. Other agent implementations (e.g.
sqlagent) also provides the ability to reorder steps.
Magnus, you're right there is no bug report on it. Could a reason for that
be that pgAgent isn't use
On Fri, Dec 31, 2010 at 15:38, Jasmin Dizdarevic
wrote:
> Hi,
> I'm starting another thread for this topic. You'll find the last comment
> from Dave at the bottom.
>> 1. Step ordering
>> I suggest adding a column named "jstorder" to pgagent.pga_jobsteps, so
>> we don't have to rename the steps
Hi,
I'm starting another thread for this topic. You'll find the last comment
from Dave at the bottom.
> 1. Step ordering
> I suggest adding a column named "jstorder" to pgagent.pga_jobsteps, so
> we don't have to rename the steps "A_", "B_" if an ordering is required.
In
> the GUI we would add
