From: | "Scott Marlowe" <smarlowe(at)qwest(dot)net> |
---|---|
To: | "Elijah O(dot) Alcantara" <elijah(at)asti(dot)dost(dot)gov(dot)ph> |
Cc: | pgsql-php(at)postgresql(dot)org |
Subject: | Re: wouldn't insert |
Date: | 2004-07-12 02:18:25 |
Message-ID: | 1089598705.17991.24.camel@localhost.localdomain |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-php |
This subject came up tangentially in the -hackers list. You should look
at using the following functions:
http://www.php.net/manual/en/function.pg-result-error.php
http://www.php.net/manual/en/function.pg-result-status.php
supported since 4.2.0 came out a little over two years ago. Very nice
way to catch and handle errors.
On Sun, 2004-07-11 at 19: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(at)asti(dot)dost(dot)gov(dot)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(at)theMode(dot)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(at)theMode(dot)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
>
From | Date | Subject | |
---|---|---|---|
Next Message | Elijah O. Alcantara | 2004-07-12 05:20:57 | Resource id #12 |
Previous Message | Elijah O. Alcantara | 2004-07-12 02:16:06 | Re: wouldn't insert |