> print "$_POST['foo']"; // generates a warning
The above is only true in PHP 4.3.0-1 as there was a
bug that caused the E_NOTICE there. In all other PHP
versions, the above will cause a parse error.
Regards,
Philip
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http
On Tue, 2003-06-17 at 07:47, Chris Hayes wrote:
> At 16:37 17-6-03, you wrote:
> >On Tue, 2003-06-17 at 09:09, nabil wrote:
> > > A side question along with this ,,, how can I include
> > $_POST['foo'] in the
> > > :
> > > $sql ="select * from db where apple = '$_POST['foo']' ";
> > >
> > > wit
On 17 Jun 2003 09:37:12 -0500, Tom Woody <[EMAIL PROTECTED]> wrote:
On Tue, 2003-06-17 at 09:09, nabil wrote:
A side question along with this ,,, how can I include $_POST['foo'] in
the
:
$sql ="select * from db where apple = '$_POST['foo']' ";
without getting an error ??
should I append it as
This is explained in the manual with tons of examples:
http://www.php.net/types.string
http://www.php.net/types.array
http://www.php.net/types.array#language.types.array.foo-bar
Regards,
Philip
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/u
Alternative, using concatenation:
$sql = "SELECT * FROM db WHERE apple = '". $_POST['foo'] . "'";
-Original Message-
From: CPT John W. Holmes [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 17, 2003 7:57 AM
To: [EMAIL PROTECTED]; Chris Hayes
S
> At 16:19 17-6-03, you wrote:
> >$sql = 'select * from db where apple = \'' . $_POST['foo'] . '\';';
> >Like that?
> you missed some quotes:
> $sql = 'select * from db where apple = \''' . $_POST['foo'] . '\'"';
Go back and count the quotes again. The original post is correct as far as
quotes go.
Actually I didn't.
The code that I gave would result in a string like:
select * from db where apple = 'blah';
For your reference:
\'' means print one single quote then end the current stream.
Then the . $_POST['foo'] appends the value of foo to the stream,
then . '\';'; prints one more single qu
At 16:37 17-6-03, you wrote:
On Tue, 2003-06-17 at 09:09, nabil wrote:
> A side question along with this ,,, how can I include
$_POST['foo'] in the
> :
> $sql ="select * from db where apple = '$_POST['foo']' ";
>
> without getting an error ??
> should I append it as $var= $_POST['foo']; before?
On Tue, 2003-06-17 at 09:09, nabil wrote:
> A side question along with this ,,, how can I include $_POST['foo'] in the
> :
> $sql ="select * from db where apple = '$_POST['foo']' ";
>
> without getting an error ??
> should I append it as $var= $_POST['foo']; before???
>
The rule of thumb I fol
At 16:19 17-6-03, you wrote:
$sql = 'select * from db where apple = \'' . $_POST['foo'] . '\';';
Like that?
you missed some quotes:
$sql = 'select * from db where apple = \''' . $_POST['foo'] . '\'"';
> A side question along with this ,,, how can I include
$_POST['foo'] in the
> :
> $sql ="se
$sql = 'select * from db where apple = \'' . $_POST['foo'] . '\';';
Like that?
On Tue, 2003-06-17 at 10:09, nabil wrote:
> A side question along with this ,,, how can I include $_POST['foo'] in the
> :
> $sql ="select * from db where apple = '$_POST['foo']' ";
>
> without getting an error ?
A side question along with this ,,, how can I include $_POST['foo'] in the
:
$sql ="select * from db where apple = '$_POST['foo']' ";
without getting an error ??
should I append it as $var= $_POST['foo']; before???
Thnx Nabil
"Jarmo Järvenpää" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL
At 12:42 17-6-03, you wrote:
the first will generate a warning if warnings are enabled.
it could mean a constant or a string, if a constant with that name is not
available
php will use it as a string and show a warning.
the second is right as a string.
in addition to that.
In your example the arr
the first will generate a warning if warnings are enabled.
it could mean a constant or a string, if a constant with that name is not available
php will use it as a string and show a warning.
the second is right as a string.
Thomas
On Tue, 17 Jun 2003 11:09:14 +0300 [EMAIL PROTECTED] (Jarmo Järve
On Wed, 2003-01-15 at 09:36, Leon Mergen wrote:
> Somebody correct me if I'm wrong, but from what I know is that when using
> shared it is compiled as a shared object and only loaded when needed. This
> decreases ram usage (which is good) , but increases load (which is bad) .
AFAIK, you should use
"Gamin" <[EMAIL PROTECTED]> wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
> ./configure --with-mysql=shared
> ./configure --with-mysql=/usr/bin/mysql
> What are the advantages/disadvatages of using either.
Somebody correct me if I'm wrong, but from what I know is that when using
s
I'm not too familiar with Linux systems. See if there are two copies of your
PHP.ini file. One might be in the conf directory and the other in the PHP
directory. Make modifications to one and see what effect it has-have a
fiddle!
"Peter" <[EMAIL PROTECTED]> wrote in message
[EMAIL PROTECTED]">new
I also would like to hear the answer to this... I try
set_time_limit(3600), but my script still appears to time out early
Jay Blanchard wrote:
>
> Good afternoon,
>
> We have some cases where we run PHP as a standalone executable for scripting
> certain processes that can be called from CRON,
Nope, not Windows, Linux and FreeBSD
-Original Message-
From: Peter [mailto:[EMAIL PROTECTED]]
Sent: Monday, July 08, 2002 11:44 PM
To: [EMAIL PROTECTED]
Subject: [PHP] Re: Difference between executable and Apache server
On my system, the PHP executeable looks for the PHP.INI file in
On my system, the PHP executeable looks for the PHP.INI file in the same
directory as the executeable, whereas the Apache module uses the one in my
C:\WINDOWS directory. Are you using Windows?
Due to this, I suppose you can have two different PHP setups if you wanted.
"Jay Blanchard" <[EMAIL PROT
Norman Zhang <[EMAIL PROTECTED]> wrote:
> Right? if ($foo) means variable exists and can be null. Whereas, isset($foo)
> means that the value in $foo cannot be null?
you've got it backwards. 'if (isset($foo))' tests that the variable has
been set to some value, possibly including false or null. '
;
mysql_select_db("employee",$db) or die("Error: ".mysql_error());
$result = mysql_query("SELECT * FROM employees",$db) or die("Error:
".mysql_error());
-Original Message-
From: Todor Stoyanov [mailto:[EMAIL PROTECTED]]
Sent: Friday, February 22, 20
Original Message -
From: "Todor Stoyanov" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, February 22, 2002 6:12 PM
Subject: [PHP] Re: difference between php3 and php4
> You must first get the number of record set rows.
>
> The warning is because you
On Wednesday, February 13, 2002, at 08:35 AM, Chris Skinner wrote:
> The answer that I have come to understand is that sessions are more
> secure
> than cookies in as that the information is stored on the server side
> instead
> of the client side. This way it is harder to steal, alter or in
The answer that I have come to understand is that sessions are more secure
than cookies in as that the information is stored on the server side instead
of the client side. This way it is harder to steal, alter or intercept.
The other reason is that users can even reject cookies, thus disallowing
src.rpm is the source code packaged in an rpm-file. If you install it as
rpm --rebuild it will compile a binary rpm for you. If you use Redhat you
can find the binary rpm in /usr/src/Redhat/RPMS
i586.rpm is a compiled binary for the i586-platform architecture
/Fredrik
--
In windows 2000 unless you set permission to write files you can't!
I mean that you have to explicitly specify that a certain folder can be
written to.
"..." <[EMAIL PROTECTED]> wrote in message
001d01c1215b$0c7613d0$14794ad3@maidew3qujo5j0">news:001d01c1215b$0c7613d0$14794ad3@maidew3qujo5j0...
M
27 matches
Mail list logo
