Anna FilinaMySQL Duplicate Entry, But Not Really (25.8.2016, 21:08 UTC)

I chased an interesting bug today. MySQL was complaining about “Integrity constraint violation: 1062 Duplicate entry”. I had all the necessary safeguards in my code to prevent duplicates in tha column.

I gave up on logic and simply dumped the contents of the problematic column for every record. I found that there was a record with and without an accent on one of the characters. PHP saw each as a unique value, but MySQL did not make a distinction, which is why it complained about a duplicate value. It’s a good thing too, because based on my goal, these should have been treated as duplicates.

My solution was to substitute accented characters before filtering duplicates in the code. This way, similar records were rejected before they were sent to the database.

Happy coding!

Link
PHP ClassesNotable PHP package: PHP Builder Pattern Generator (25.8.2016, 06:33 UTC)
By Manuel Lemos
The builder design pattern allows to dynamically create objects in a way that the same process of construction can allow multiple representations of the object that can be changed over time according to the needs of a project.

This package implements the builder design pattern with a concrete builder class that generates code for classes dynamically to implement a representation of the object class being built at run time.

Read this article to learn more details about how this notable PHP package works.
Link
Nomad PHPBug Hunting with Git Bisect (24.8.2016, 20:04 UTC)

Speaker: Alessandro Lai @AlessandroLai Bugs are introduced in our code almost everyday, one way or another, even if we do our best to avoid it. Often, we need to identify where a bug originated to fix it, but we have to sift through a long history of commits to do that. Git comes to the …

The post Bug Hunting with Git Bisect appeared first on Nomad PHP.

Link
PHP ClassesFast PHP Error Monitoring and Bug Fixing with Rollbar (24.8.2016, 05:37 UTC)
By Samuel Adeshina
Regardless of how good you are as a developer, you will always ship code to production that will have bugs or does not deal with situations that were unanticipated.

Therefore you always need to have a tool that can monitor the errors on the server side, so you can act promptly and fix issues as quickly as possible.

Read this tutorial to learn how you can use Rollbar to keep track of your PHP Web applications issues.
Link
Anna FilinaConFoo Montreal 2017 Calling for Papers (23.8.2016, 17:16 UTC)

ConFoo | March 8-10, 2017 | Montreal, CanadaWant to get your web development ideas in front of a live audience? The call for papers for the ConFoo Montreal 2017 web developer conference is open! If you have a burning desire to hold forth about PHP, Java, Ruby, Python, or any other web development topics, we want to see your proposals. The window is open only from August 21 to September 20, 2016, so hurry. An added benefit: If your proposal is selected and you live outside of the Montreal area, we will cover your travel and hotel.

You’ll have 45 minutes to wow the crowd, with 35 minutes for your topic and 10 minutes for Q&A. We can’t wait to see your proposals. Knock us out!

ConFoo Montreal will be held on March 8-10, 2017. For those of you who already know about our conference, be aware that this annual tradition will still be running in addition to ConFoo Vancouver. Visit our site to learn more about both events.

Link
SitePoint PHPUp and Running with the Fastest PHP Framework on PHP7 in 5 Mins (23.8.2016, 16:00 UTC)

You may remember our past infatuation with Phalcon, the fastest PHP framework.

In this post, we'll go through the process of getting it up and running in 5 minutes on one of our Homestead Improved instances. If you're not interested in why or what Phalcon is, just skip ahead to "Setting it up".

Phalcon PHP logo

Recap

If you're not familiar with it, Phalcon is a PHP framework written in Zephir, a language mid-way between C and PHP that helps in developing PHP extensions without having to know C. It's a golden middle ground which lets PHP developers develop highly optimized modules for their programming language environment without the overhead of learning a completely new language, because Zephir compiles into C, which is what PHP extensions are made of.

Originally, Phalcon was an extension written in pure C - which made it incredibly fast. However, this also introduced massive overhead in fixing bugs or inspecting what's going on under the hood when something doesn't work the way it should. It also took ages to add new features, since developing in C is so much more difficult. In version 2, Phalcon was rewritten in Zephir, but as PHP 7 was looming on the horizon and announced a dramatic departure from the extension API of PHP 5+, Zephir could not compile code to PHP 7 compatible extensions and was left behind in PHP 5 land.

Continue reading %Up and Running with the Fastest PHP Framework on PHP7 in 5 Mins%

Link
Brandon SavageThe Software Dilemma (23.8.2016, 12:00 UTC)

Any time software and business come together, there is an inherent conflict between “get it done fast” and “do a good job”. This conflict often comes to a head when deadlines are missed, whether through unrealistic expectation or underestimation on the part of the developers. The dilemma between quantity, speed and feature set isn’t going […]

The post The Software Dilemma appeared first on BrandonSavage.net.

Link
Voices of the ElePHPantInterview with Adam Harvey (23.8.2016, 10:00 UTC) Link
PHP ClassesNotable PHP package: CakePHP 2.x Container (23.8.2016, 07:40 UTC)
By Manuel Lemos
Dependency injection is design pattern often used implement functionality on one class using objects from external classes without hardcoding the dependency between the two classes.

Several PHP frameworks implement their own dependency injection containers but since each one implements it in a different way, a generic container interface was defined to allow to call components of one framework to be called from by components of any other framework.

The package implements a component with the generic dependency injection container interface so application services and other types of applications not based on CakePHP can be easily used with CakePHP.

Read this article to learn more details about how this notable PHP package works.
Link
SitePoint PHPFramework-Agnostic PHP Cronjobs Made Easy with Crunz! (22.8.2016, 16:00 UTC)

In this article, we're going to learn about a relatively new job scheduling library named Crunz. Crunz is a framework-agnostic library inspired by Laravel's Task Scheduler, but improved in many ways. Full disclosure: I'm the author and am welcoming contributions and comments on how to improve it further!

Clock photo

Before getting started, you should have a firm grasp of cronjobs, so please read our in-depth walkthrough if you're unfamiliar with how they work.

Installation

To install it, we use Composer as usual:

composer require lavary/crunz

A command-line utility named crunz will be symlinked to vendor/bin of our project. This command-line utility provides a set of useful commands, which we'll discuss shortly.

How Does it Work?

Instead of a installing cron jobs in a crontab file, we define them in one or several PHP files, by using the Crunz interface.

Here's a basic example:

<?php
// tasks/backupTasks.php

use Crunz\Schedule;

$schedule = new Schedule();
$schedule->run('cp project project-bk')
         ->daily()

return $schedule;

To run the tasks, we install an ordinary cron job (a crontab entry) which runs every minute, and delegates the responsibility to Crunz's event runner:

* * * * * /project/vendor/bin/crunz schedule:run

The command schedule:run is responsible for collecting all the PHP task files and runs the tasks which are due.

Task Files

Task files resemble crontab files. Just like crontab files, they can contain one or more tasks.

To create a task file, we need to decide where we want to keep them. The location doesn't matter as long as we let Crunz know the location. Normally, we create our task files in tasks/ within the project's root directory. However, we can keep them outside of the project's directory if there's a reason for that.

By default, Crunz assumes all the task files reside in the tasks/ directory within the project's root directory.

There are two ways to specify the source directory: configuration file (more on this below) and as a parameter to the event runner command:

* * * * * /project/vendor/bin/crunz schedule:run /path/to/tasks/directory

Continue reading %Framework-Agnostic PHP Cronjobs Made Easy with Crunz!%

Link
LinksRSS 0.92   RDF 1.
Atom Feed   100% Popoon
PHP5 powered   PEAR
ButtonsPlanet PHP   Planet PHP
Planet PHP