And it gives the developer the chance to catch any error(s) which are thrown as PDOExceptions. This way the script will not stop with a Fatal Error when something goes wrong. In the above example the error mode isn't strictly necessary, but it is advised to add it. $dbConnection->setAttribute(PDO::ATTR_ERRMODE, PDO::ERRMODE_EXCEPTION) $dbConnection->setAttribute(PDO::ATTR_EMULATE_PREPARES, false) An example of creating a connection using PDO is: $dbConnection = new PDO('mysql:dbname=dbtest host=127.0.0.1 charset=utf8', 'user', 'password') To fix this you have to disable the emulation of prepared statements. Note that when using PDO to access a MySQL database real prepared statements are not used by default. If you're connecting to a database other than MySQL, there is a driver-specific second option that you can refer to (for example, pg_prepare() and pg_execute() for PostgreSQL). $stmt->bind_param('s', $name) // 's' specifies the variable type => 'string' Using MySQLi (for MySQL): $stmt = $dbConnection->prepare('SELECT * FROM employees WHERE name = ?') Using PDO (for any supported database driver): $stmt = $pdo->prepare('SELECT * FROM employees WHERE name = :name') You basically have two options to achieve this: This way it is impossible for an attacker to inject malicious SQL. These are SQL statements that are sent to and parsed by the database server separately from any parameters. It is possible to create SQL statement with correctly formatted data parts, but if you don't fully understand the details, you should always use prepared statements and parameterized queries. The correct way to avoid SQL injection attacks, no matter which database you use, is to separate the data from SQL, so that data stays data and will never be interpreted as commands by the SQL parser. I also added a php.ini file with the following contents in both the root of my site directory and the root of my MAMP directory: memory_limit = 128M (By the way, I keep my MAMP folder (Dev) in Dropbox and it works fine) Applications/MAMP/conf/apache/extra/nf Īnd lower down in the same file in the relevant site's configuration: ĭocumentRoot "/Users/Username/Dropbox/Dev/v" So I added this to the 'php_value memory_limit 128M': I read somewhere that it may be necessary to increase the memory limit here. I am using Virtual Hosts to set my own URLs. I then quit MAMP entirely and restarted it, but in MAMP phpInfo it still reads: I've changed the following from 32M to 128M in the following file: But the master PHP limit is still not updating.
I've added the following to my site's htaccess file, which is read by the site and works (ExpressionEngine).
I've tried all of the below, but nothing seems to have worked. I've read about creating a new template for MAMP Pro, but I'm using the standard version of MAMP. I also added a php.I've been trying to increase the php memory_limit in MAMP (Mac OSX).
I then quit MAMP entirely and restarted it, but in MAMP phpInfo it still reads: memory_limit 32M Applications/MAMP/conf/php5.4.10 memory_limit = 128M I've been trying to increase the php memory_limit in MAMP (Mac OSX).
0 kommentar(er)
