From: | John Burski <jburski(at)cloudnet(dot)com> |
---|---|
To: | アムス <ams(at)asiams(dot)com> |
Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Parse error |
Date: | 2002-11-16 20:21:47 |
Message-ID: | 3DD6A8DB.8010609@cloudnet.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
You might check for a typographical error in a preceding line. I *think"
that the "unexpected T_STRING" error means that the parser ran across a
new constant string that it didn't expect to see.
アムス wrote:
>When I run a php program connected to postgresql, I have the following
>error:
>
>"Parse error: parse error, unexpected T_STRING "
>
>The actual code for this part that caused the error is like this:
>
>$sql = "SELECT * FROM appconf ORDER BY sort_order"; <=== This line causes
>the error.
>$result = @pg_exec($sql);
>
>Do you know what is the unexpected T_STRING error is?
>
>THank you for your help.
>
>Abraham Lee
>AMS
>
>
>---------------------------(end of broadcast)---------------------------
>TIP 3: if posting/reading through Usenet, please send an appropriate
>subscribe-nomail command to majordomo(at)postgresql(dot)org so that your
>message can get through to the mailing list cleanly
>
>.
>
>
>
--
John Burski
@home S.I.M.U. (Well, sometimes I am)
... and still searching for new cheese
From | Date | Subject | |
---|---|---|---|
Next Message | Joe Conway | 2002-11-16 20:40:22 | Re: Doing sth. like oracles "connect by" |
Previous Message | Stephan Szabo | 2002-11-16 20:14:17 | Re: DECLARE CURSOR |