Re: finding compile time errors
- From: Michael Fesser <netizen@xxxxxx>
- Date: Fri, 13 Jun 2008 19:22:15 +0200
..oO(Jeff)
If I name the included file 'my_functions.php' and put it in the web
path, wouldn't some of this be visible from the web. I just want nothing
to happen if someone hits http://my_domain.com/my_includes.php. Perhaps
I'm worrying about nothing...
The best and most secure way is to store such files outside the document
root, so that they can't be accessed by a URL.
How does PHP handle placeholders in MySQL?
I'm used to doing this:
$sql='SELECT some_field FROM some_table WHERE another_field = ? AND
other_field = ?';
When you do this (at least in perl), you don't have to worry about
SQL insertion.
I can't seem to find this, and had stumbled across an example
earlier. Perhaps I should break this question out in a new post...
Have a look at PDO. It's the recommended and most flexible database
interface (installed and enabled by default). The keyword to look for
is "prepared statements".
Micha
.
- Follow-Ups:
- Re: finding compile time errors
- From: Jeff
- Re: finding compile time errors
- References:
- finding compile time errors
- From: Jeff
- Re: finding compile time errors
- From: Michael Fesser
- Re: finding compile time errors
- From: Jeff
- finding compile time errors
- Prev by Date: Re: Light at the end of the tunnel - and it's NOT a train !
- Next by Date: Re: finding compile time errors
- Previous by thread: Re: finding compile time errors
- Next by thread: Re: finding compile time errors
- Index(es):