woru

Exception handlers set no exit code

6

Exception handlers set no exit code, which causes problems when migrations are called from bash scripts. Fix: ``` Index: ruckusing-migrations/lib/Ruckusing/Exception.php =================================================================== --- ruckusing-migrations/lib/Ruckusing/Exception.php (revision 6344) +++ ruckusing-migrations/lib/Ruckusing/Exception.php (working copy) @@...

Invalid error handler

3

ErrorHandler (Ruckusing_Exception.php:79) cannot call exit(1) for warnings. E.g. when pg_query fails not only it sets error code but also it generates a warning. Currently errorHandler calls exit(1) on warnings and...

schema_info could have 'applied_at' column of type timestamp. If you maintain multiple databases it would be nice to know when exactly migrations were applied.

Strings::\* may not work. E.g. mb_strlen will not work.

```php $cities = Arrays::map($users, Functions::extract()->getAddress('home')->city); $cities = Arrays::map($users, Functions::argument()->getAddress('home')->city); ```

binding function arguments

1

http://en.cppreference.com/w/cpp/utility/functional/bind

and Mock::all or whatever its name is

Functions::contains works for array. Other methods work for strings. Maybe we should rename them to stringContains etc

is_callable(array($mock, $method)))