This morning I’ve finally released PHPDbMigrate RC 2.
The changes to this utility include:
all migration functions work in MySQL
mysql and mysqli database adapters supported
You can find the code here: http://code.google.com/p/phpdbmigrate/
I’ve still got work to do in support other database types and updating the wiki.
Tags: active migration, activemigration, database, php
So it’s been a couple of months since I posted last. I’ve really been heads down on coding at both work and home. Things are starting to lighten up in both areas and I’m ready to start a new project, PHPDbMigrate.
At work I’ve been setting up a lot of sites using CodeIgniter. It’s not a bad framework and since I’ve been away from PHP for a while it’s nice to be coding in PHP again. Not much really exciting going on at work, just setting up websites and modifications to existing code.
At home though is entirely different. For thre months now I’ve been developing Value Target. Launched it June 7. It’s definately a labor of love and still have lot’s to do on it. It’s a rails app and I’ve really fallen in love with the framework. So much so that I am going to port PyMigrate to PHP.
PHPDbMigrate is the name of the port. Yes there are “some” attempts out there to create an ActiveMigration library. I find that they are limited to MySql, not complete, or do not run code blocks. Since I’ve already accomplished that in Python, it’ll be easy for me to port to PHP. Although I won’t have the luxury of db connector library like I did with SQLAlchemy in Python.
I’ve set up the Google code project and will announce all my updates to the repository.
After I finally release a stable version of PHPDbMigrate my plan is to create a CodeIgniter library so I can develop sites even faster. So thanks for checking in and stay tunes.
Tags: php, PHPDbMigrate, Value Target
Now that CakePHP 1.2 is a stable version I’ve picked back up on it. When I looked at it as a release candidate, and after they announced RESTFul routing, I specifically looked at the RESTful implementation. I’m looking at it again and find it’s still not there.
Looking at the router.php file for the Router::mapResources :
Subscribevar $__resourceMap = array(
array('action' => 'index', 'method' => 'GET', 'id' => false),
array('action' => 'view', 'method' => 'GET', 'id' => true),
array('action' => 'add', 'method' => 'POST', 'id' => false),
array('action' => 'edit', 'method' => 'PUT', 'id' => true),
array('action' => 'delete', 'method' => 'DELETE', 'id' => true),
array('action' => 'edit', 'method' => 'POST', 'id' => true)
);
The first thing pops out and smells is the double entry for the edit action. This clearly indicates that I’ll need to put in conditional logic to either present the edit view or save a posted edit form. One of those edit methods needs to be changed to an update action to remove the edit conditionals.
There are actions missing from the mapResources as well. Where’s the new(create) action? This presents a view with the fields for creating a new record of whatever. Certainly submitting the form would POST to the add action.
As it stands and as advertised the mapResources does work. /posts calls the index action. /posts/1 calls the view action. So how can the two missing actions (update / new) be added easily?
The original config/routes.php file would look like this:
Router::mapResources('posts');
Just add two lines above the mapResources:
Router::connect("/:controller/:id", array("action" => "update", "[method]" => "PUT"),array('pass' => array('id'));
Router::connect("/:controller/new", array("action" => "create", "[method]" => "GET"));
//Original
Router::mapResources('posts');
As long as those two lines are above any mapped resources they will all act the same. So:
Router::connect("/:controller/:id", array("action" => "update", "[method]" => "PUT"),array('pass' => array('id'));
Router::connect("/:controller/new", array("action" => "create", "[method]" => "GET"));
Router::mapResources('posts')
Router::mapResources('users');
Will apply the new update and create routing for both posts and users.
There is one other thing that is bugging me about the cakePHP RESTFul implementation. The PUT/POST method to call an edit view. I want to be able to call posts/1/edit with a GET to display the edit view. So with one more line of code in the routes.php file.
Router::connect("/:controller/:id/edit", array("action" => "edit", "[method]" => "GET"),array('pass' => array('id'));
Router::connect("/:controller/:id", array("action" => "update", "[method]" => "PUT"),array('pass' => array('id'));
Router::connect("/:controller/new", array("action" => "create", "[method]" => "GET"));
Router::mapResources('posts')
Router::mapResources('users');
Now we have RESTFul routing for these routes!
| URL | Method | Action |
|---|---|---|
| /posts | GET | index() |
| /posts | POST | add() |
| /posts/new | GET | create() |
| /posts/1 | GET | view($id) |
| /posts/1 | PUT | update($id) |
| /posts/1/edit | GET | edit($id) |
| /posts/1 | DELETE | delete($id) |
| /users | GET | index() |
| /users | POST | add() |
| /users/new | GET | create() |
| /users/1 | GET | view($id) |
| /users/1 | PUT | update() |
| /users/1/edit | GET | edit($id) |
| /users/1 | DELETE | delete($id) |
Entries