pg.ddx.io  pgsql-php@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Elijah O. Alcantara <elijah@asti.dost.gov.ph>
To: pgsql-php@postgresql.org
Subject: Re: wouldn't insert
Date: Mon, 12 Jul 2004 10:16:06 +0800
Message-ID: <1089598566.11624.12.camel@Falcon> (raw)
In-Reply-To: <1089596732.11624.3.camel@Falcon>
References: <1089340768.18180.9.camel@Falcon>
	<Pine.BSF.4.58.0407091459400.2007@themode.com>
	<1089596732.11624.3.camel@Falcon>

Bingo! no wonder it can't push through the loop, there wasn't any
results in the first place at the first query. Error_log()'s very useful
=)

Thanks,
Elijah

On Mon, 2004-07-12 at 09:45, Elijah O. Alcantara wrote:
> I tried using error_log() but never got any emails... 
> 
> error_log("This is query2 inserting $ctrl_no $category $contact_no
> $organization_name $address $telephone $fax $email", 1,
> "elijah@asti.dost.gov.ph");
> 
> looks like it never went in the for loop, somethings wrong... 
> 
> Thanks for the advice, 
> Elijah
> 
> On Sat, 2004-07-10 at 03:08, brew@theMode.com wrote:
> > Elijah.....
> > 
> > > There are no errors whatsoever, must be something wrong with the logic
> > > somewhere...
> > 
> > What I do when I can't find errors is break down the code into
> > smaller steps and add error checking.
> > 
> > Make the connection and check the return value.
> > 
> > Put together the sql statement and print it.
> > 
> > Query the database and check the return value.
> > 
> > and so forth.....
> > 
> > Check php.net to see some examples of error checking.
> > 
> > On another note, if I'm only working with only one db I just connect once
> > near the start of the script and then use that connection for the
> > subsequent calls.
> > 
> > brew
> > 
> >  ==========================================================================
> >                   Strange Brew   (brew@theMode.com)
> >      Check out my Musician's Online Database Exchange (The MODE Pages)
> >                         http://www.TheMode.com
> >  ==========================================================================
> > 
> > 
> > ---------------------------(end of broadcast)---------------------------
> > TIP 9: the planner will ignore your desire to choose an index scan if your
> >       joining column's datatypes do not match
> 
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 5: Have you checked our extensive FAQ?
> 
>                http://www.postgresql.org/docs/faqs/FAQ.html




view thread (8+ messages)  latest in thread

Message-ID: <1089598566.11624.12.camel@Falcon>
Permalink:  ../1089598566.11624.12.camel@Falcon/
Also on:    postgresql.org/message-id/1089598566.11624.12.camel@Falcon

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-php@postgresql.org
  Cc: elijah@asti.dost.gov.ph
  Subject: Re: wouldn't insert
  In-Reply-To: <1089598566.11624.12.camel@Falcon>
  References: <1089340768.18180.9.camel@Falcon> <Pine.BSF.4.58.0407091459400.2007@themode.com> <1089596732.11624.3.camel@Falcon> <1089598566.11624.12.camel@Falcon>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox