Error mapping column to model after changing table column type

You sure you dont have maybe modelsMetadata cache enabled in di in APC or somewhere ?

Pretty sure. The application is pretty basic at this stage, and I haven't manually configured any caching functionality.

This is the entire setup portion for the database adapter:

function getDbAdapter(){

    $configFile = parse_ini_file("config.ini");

    return new \Phalcon\Db\Adapter\Pdo\Mysql(array(
        "host" => $configFile["host"],
        "username" => $configFile["username"],
        "password" => $configFile["password"],
        "dbname" => $configFile["dbname"]
    ));
}
$di = new \Phalcon\DI\FactoryDefault();
$di->set('db', getDbAdapter());
$app = new Phalcon\Mvc\Micro();
$app->setDI($di);

This is the Phalcon information from phpinfo:

phalcon Web framework delivered as a C-extension for PHP

phalcon enabled
Author  Phalcon Team and contributors
Version     2.0.8
Build Date  Nov 6 2015 11:16:24
Powered by Zephir   Version 0.8.0a

Directive   Local Value Master Value
phalcon.db.escape_identifiers   On  On
phalcon.db.force_casting    Off Off
phalcon.orm.cast_on_hydrate Off Off
phalcon.orm.column_renaming On  On
phalcon.orm.enable_implicit_joins   On  On
phalcon.orm.enable_literals On  On
phalcon.orm.events  On  On
phalcon.orm.exception_on_failed_save    Off Off
phalcon.orm.ignore_unknown_columns  Off Off
phalcon.orm.late_state_binding  Off Off
phalcon.orm.not_null_validations    On  On
phalcon.orm.virtual_foreign_keys    On  On

Is there anything else I could check?

'Column '1dffc8f8' doesn't belong to any of the selected models (1), when preparing: SELECT [Users].* FROM [Users] WHERE ([customerid] = :APR0:) AND id = 1dffc8f8-ec15-91c9-0d3e-9b1aafa1ffad'

the generated statement seems to think 'id' is still an integer; the error refers to a non-existing column named '1dffc8f8', as this is the first part of the GUID. This is seen as a column identifier, because it isn't wrapped in single quotes in the generated statement.

Well its pretty possible. Use single quotes or backticks.

I would, but that statement isn't generated by me, but by Phalcon. If I do:

$user = $customer->getUsers("id = $userid")->getFirst();

or

$user = Users::findFirst($userid);

Then I get that error because the statement it prepares seems to be meant for an integer column.

I tried to manually tell Phalcon that the id property is a string by adding this to the model:

* @property string id

But that didn't do anything.

Try:

$user = $customer->getUsers("id = `$userid`")->getFirst(); // or
$user = $customer->getUsers("id = '$userid'")->getFirst();

Also im not sure is it safe, you should use binding.

These both seem to work:

$user = Users::find("id = '$userid'")->getFirst();
//and
$user = Users::find(array('id' => "'$userid'"))->getFirst();

Anyone have any idea why this is required? Is there anything that can be done in the model to make this work normally? Otherwise I'd have to re-do a lot of logic.

Excellent. This works:

$user=Users::findFirst([
    'conditions'=>'id = :id:',
    'bind'=>array('id'=>$userid)
]);

Thanks very much for the help.

I liked the previty of $user = Users::findFirst($userid);. Do I understand correctly that I can't use this if my ID is not an integer?

Yes, exactly :P Well you can still use it like:

$user = Users::findFirst($userid);

You can just overload findFirst method yourself :). Well you can even create BaseModel/AbstractModel - well you extend it here. And then your models will use it, and you can use your super duper long id just by findFirst($userid) :).

You just have do something like this:

(abstract) class BaseModel/AbstractModel extends Model
{
    public function findFirst($parameters)
    {
        if(is_string($parameters)){// well in mostly times convention tell us to use int, but you want string
                return parent::findFirst(array(
                    'conditions'=>'id = :id:',
                    'bind'=>array('id'=>$parameters)
                ));
        }
        return parent::findFirst($parameters);
    }

    // not sure about find method, i dont think you need to overload it in your case
}

and then your users:

class Users extends AbstractModel
{
}

And you can go back to :

Users::findFirst($userid);

Also i dont understand your code in first place:

$user = $customer->getUsers("id = $userid")->getFirst();

Cant you just use

Users::findFirst($userId)

With code i provided above ? Also - can you check if for example if you put string without dashes is it still not working ? If not i will do PR with fix for that, cuz its seems like a bug.

Also you sure that

Users::findFirst($userId)

Wasnt working ? Cuz as i remember phalcon be default using bind when you provide only parameter as not array.

I can confirm that this:

$user = Users::findFirst($userId)

Doesn't work. It produces the error mentioned in the opening post. This also doesn't work:

$user = Users::find("id = $userid")->getFirst();

This produces the same error.

This seems like a bug to me. It's fine if the framework requires the ID to be an integer, but it should at least throw a better exception, instead of building an invalid query and then interpreting the ID as a column name.

As to your question about this code:

$user = $customer->getUsers("id = $userid")->getFirst();

At that stage in the logic I have a customer, and I want to make sure that the requested user belongs to that customer. Of course, that could also be achieved with an extra parameter for the customer when searching users.

Great idea about implementing my own findFirst method that handles varchar IDs. I'll give that a try!

For future reference, here is the implementation of the abstract BaseModel class with the override for findFirst, that supports non-integer IDs. I can confirm that this works.

<?php
use Phalcon\Mvc\Model;

abstract class BaseModel extends Model
{
    /**
     * @param array|null|string $parameters
     * @return Model
     */
    public static function findFirst($parameters = null)
    {
        if(is_string($parameters) && (strpos($parameters,'=') === false)){
            return parent::findFirst(array(
                'conditions'=>'id = :id:',
                'bind'=>array('id'=>$parameters)
            ));
        }
        return parent::findFirst($parameters);
    }
}

Edit: added the check if the parameter contains the character '='. Otherwise this usage breaks:

$user = Users::findFirst("username = '$username'");

I'm not entirely happy with this approach. Might reconsider in the future.

Well you should not use

$user = Users::findFirst("username = '$username'");

This, cuz i dont event now if this working, but this is not using binding. If you want to pass variable in the condition YOU HAVE TO use binding. Cuz not using it can cause SQL Injection

That usage does work by default. But that's a good point, I'll change it to use binding.

Any idea why binding isn't used by default for the 'find' and 'findFirst' methods?