News Feed
Sections




News Archive
feed this:

Looking for more information on how to do PHP the right way? Check out PHP: The Right Way

SitePoint PHP Blog:
MySQL Transactions & Why They Can't Be Emulated in PHP
December 15, 2010 @ 12:47:44

On the SitePoint blog there's a new article from Craig Buckler stating that MySQL transactions can't be emulated in PHP and shouldn't be discounted despite many developers seeing them as not much more than a performance hit.

My recent article, "Top 10 MySQL Mistakes Made by PHP Developers" was far more controversial than I expected. Several of the more intriguing responses were from PHP coders who considered transactions to be an unnecessary overhead. With good-quality PHP code, they argued, you don't need transactions or MySQL's InnoDB storage engine. It's certainly true you don't always need transactions.

He gives an example of a situation where database-based transactions would be very useful (inserting customer information) and points out that, despite the best intentions of developers, reducing as many layers and connections between SQL and code is a good thing. Transactions help you conform to the ACID ideas and keep data integrity by only having things in the database that were successful. He includes a small bit on using transactions as well.

0 comments voice your opinion now!
mysql transaction emulate opinion acid integrity mysql


Codewalkers.com:
The PAVISE of Security
July 31, 2006 @ 06:10:17

Codewalkers.com has posted a new tutorial today from Martin Psinas titled "The PAVISE of Security".

Join notepad as he tours safe coding practices. He presents an easy to remember mnemonic which explains each component to help keep secure coding practices at the forefront in your development.

In the tutorial he talks about the bad reputation that PHP seems to be gathering and how it's less about the langauge and more about the applications written in it. His response is shown the the acronym in the title: PAVISE- Privacy, Administration, Validation, Integrity, Sociology and Environment.

  • Privacy deals with keeping server-related info away from the client (what it shouldn't see)
  • Administration suggests knowing how things are configured, even if you don't have the access to change them
  • Validation (a huge factor) keeps the user data entered from doing bad things to you and your application
  • Integrity is the overall strength of your application
  • Sociology talks about methods to protect yourself from the social engineering that can happen to anyone
  • Environment requires knowing if you're working on a secure platform or not, which could undermine all other efforts

Under each of the headings items are listed out and detailed to help give you a more concrete example. Code examples are also included where appropriate.

2 comments voice your opinion now!
tutorial pavise security provacy admin validate integrity sociology environment tutorial pavise security provacy admin validate integrity sociology environment



Community Events





Don't see your event here?
Let us know!


threedevsandamaybe code interview voicesoftheelephpant symfony deployment bugfix series podcast list laravel language release conference introduction community framework tips zendserver api

All content copyright, 2014 PHPDeveloper.org :: info@phpdeveloper.org - Powered by the Solar PHP Framework