Quick Links

Re: pgAgent reports failure upon success

From:	"Martin French" <Martin(dot)French(at)romaxtech(dot)com>
To:	Dave Page <dpage(at)pgadmin(dot)org>
Cc:	pgadmin-support(at)postgresql(dot)org,pgadmin-support-owner(at)postgresql(dot)org
Subject:	Re: pgAgent reports failure upon success
Date:	2012-07-10 12:57:58
Message-ID:	OFE3F5F4C7.38B73E7C-ON80257A37.0046014D-80257A37.004739C2@LocalDomain
Views:	Raw Message \| Whole Thread \| Download mbox \| Resend email
Thread:
Lists:	pgadmin-support

<html><body>Hi <tt>Thanks for the feedback. I certainly won't be discouraged by it! :)</tt> <tt>> - You have member name of [Get|Set]LastResult which set/return a > member variable called lastStatus. These should be consistent to avoid > confusion.</tt> <tt>Will amend accordingly.</tt> <tt>> - Rather than setting lastStatus to 0 or -1, why not set it to > PQresultStatus(). That seems like it would be more useful in the > future (and potentially in the log files).</tt> <tt>I'd set it to only two values, as it made the comparison easier. As I see it, ExecStatusType ENUM can be anyone of 0 - 8 inclusive, but some of those are error messages, so it'd either have to determine which ones are OK and which are not either with a case statement or with an extended "if". Happy to code that in along the lines of (or inverse, testing for fails...):</tt> <tt>switch (rc)</tt> <tt>{</tt> <tt> case PGRES_COMMAND_OK:</tt> <tt> case PGRES_TUPLES_OK:</tt> <tt> case PGRES_COPY_OUT:</tt> <tt> case PGRES_COPY_IN:</tt> <tt> case PGRES_COPY_BOTH:</tt> <tt> </tt><tt>stepstatus = wxT("s");</tt> <tt> break;</tt> <tt> default:</tt> <tt> </tt><tt>stepstatus = steps->GetString(wxT("jstonerror"));</tt> <tt> break</tt> <tt>}</tt> <tt>If you think that's a more viable option? Let me know and I'll sort it :)</tt> <tt>> - When creating the diff, please use "git diff", or if working from a > source tarball (not recommended for development) - take 2 copies and > then diff them, eg "diff -c -r pgagent-src/ pgagent-src.orig/ > > mypatch.diff". That'll put the entire patch in one file, which makes > it much easier to handle and reapply.</tt> <tt>I'm afraid I'm limited to source tarballs at the moment. Attempting to pull from git gives me "Connection Refused". So will create a single patch file using the method suggested.</tt> <tt>Cheers</tt> <tt>Martin. </tt> =============================================

Romax Technology Limited
Rutherford House
Nottingham Science & Technology Park
Nottingham,
NG7 2PZ
England

Telephone numbers:
+44 (0)115 951 88 00 (main)

For other office locations see:
http://www.romaxtech.com/Contact
=================================
===============
E-mail: info(at)romaxtech(dot)com
Website: www.romaxtech.com
=================================

================
Confidentiality Statement
This transmission is for the addressee only and contains information that is confidential and privileged.
Unless you are the named addressee, or authorised to receive it on behalf of the addressee
you may not copy or use it, or disclose it to anyone else.
If you have received this transmission in error please delete from your system and contact the sender. Thank you for your cooperation.
=================================================
</body></html>

Attachment	Content-Type	Size
unknown_filename	text/html	3.6 KB

In response to

Re: pgAgent reports failure upon success at 2012-07-10 12:19:54 from Dave Page

Responses

Re: pgAgent reports failure upon success at 2012-07-10 15:05:18 from Dave Page

Browse pgadmin-support by date

	From	Date	Subject
Next Message	Dave Page	2012-07-10 15:05:18	Re: pgAgent reports failure upon success
Previous Message	Dave Page	2012-07-10 12:19:54	Re: pgAgent reports failure upon success