How to make models use defaults in Phalcon PHP Framework?

Question

If a table has defaults on certain fields and NULL is not allowed, one would expect the insert script to use those defaults, as MariaDB/MySQL usually does. For example, if the table products has an AI field "id", a required field "name" and two required fields "active" and "featured" which both default to 1, then the query

INSERT INTO products (name) VALUES ('someName');

automatically inserts 1 as the value of active and featured. However, when using Phalcon's models like so:

$product = new Products();
$product->setName('someName');
$product->save();

returns validation errors saying "active" and "featured" are required.

Is there a flag I should provide during model generation in order for Phalcon tools to harvest and input the defaults into Model classes, or another way to make Phalcon automatically use defaults if found? Best approach would be just ignoring the fields that weren't set, I reckon. Can I make the models do that?

score 9 · Accepted Answer · answered Apr 11 '13 at 15:33

You can use a raw database value to avoid that, in specific inserts:

<?php

use Phalcon\Db\RawValue;

$product = new Products();
$product->setName('someName');
$product->setType(new RawValue('default')); //use default here
$product->save();

Or, general before create/update for specific fields:

use Phalcon\Db\RawValue;

class Products extends Phalcon\Mvc\Model
{
    public function beforeValidationOnCreate()
    {
        $this->type = new RawValue('default');
    }
}

Or ignore these fields in every SQL INSERT generated:

use Phalcon\Db\RawValue;

class Products extends Phalcon\Mvc\Model
{
    public function initialize()
    {
        $this->skipAttributesOnCreate(array('type'));
    }
}

@twistedxtra Minor improvements: `$this->type = $this->type ?: new RawValue('default');`. But in any case - thanks! :) — serghei, Dec 28 '14 at 20:21

score 2 · Answer 2 · answered Jul 18 '13 at 10:22

2

Although I find twistedxtra's answer fascinating from the aspect that Phalcon contains this wicked method to read the column default, I believe from a architectural point of view this might be the wrong approach as you rely on your database to define the defaults of the properties of your model.

I would set the default value when declaring the property and keep the logic in the application layer. But that's just me.

answered Jul 18 '13 at 10:22

mapsi

644
6
13

Wouldn't the "correct" architectural approach be to enforce such a default at the DB level? At least that way you never end up with bad data. – Big McLargeHuge Dec 04 '14 at 05:11

Deji Kadri · Answer 3 · 2016-10-21T17:24:28.310

1

Use Like below

The skipAttributesOnCreate will make sure Phalcon does not attempt to put a a value in that column. The database will apply the default value.

public function initialize()
{
    $this->setSource('table_name');
    $this->skipAttributesOnCreate(['name_of_column']);
}

edited Oct 21 '16 at 17:24

answered Oct 18 '16 at 16:58

Deji Kadri

7
5

1

Hi Deji, welcome to StackOverflow. When answering questions here, you should always provide explanation and description to help solve the problem at hand. Posting a block of code is usually not helpful, and it provides no context. Please consider updating your answer here. – Sam Spencer Oct 18 '16 at 17:28

How to make models use defaults in Phalcon PHP Framework?

3 Answers3