Exception not work

Hi,

have you tried this, to isolate the problem :

try
{
    throw new \Exception("error testing");
}
catch (\Exception $e)
{
    $this->flash->error($e->getMessage());
}

this work

Hi,

have you tried this, to isolate the problem :

try
{
   throw new \Exception("error testing");
}
catch (\Exception $e)
{
   $this->flash->error($e->getMessage());
}

then the problem is in the other part : create returns always true...

  if ($Model->create($params->toArray()))
    {
    }

why always?

https://docs.phalcon.io/en/latest/reference/models.html#create-update-with-confidence

if ($robot->create() == false) {
    echo "Umh, We can't store robots right now: \n";
    foreach ($robot->getMessages() as $message) {
        echo $message, "\n";
    }
} else {
    echo "Great, a new robot was created successfully!";
}

then the problem is in the other part : create returns always true...

 if ($Model->create($params->toArray()))
   {
   }

"Always" in your example...

What is the implementation of the class of $model, what are the values of $params

model with not null fields

and now all models can be saved, wtf?

if ($form->isValid())
{
$params = $form->getEntity();
}

"Always" in your example...

What is the implementation of the class of $model, what are the values of $params

how are declared "not null" constraints ?

Are nulls replaced by an empty string at the insertion?

CREATE TABLE `settings` (
    `id` INT(10) UNSIGNED NOT NULL AUTO_INCREMENT,
    `is_active` TINYINT(1) UNSIGNED NOT NULL DEFAULT '1',
    `key` VARCHAR(24) NOT NULL DEFAULT '',
    `key_value` VARCHAR(24) NOT NULL DEFAULT '',
    `name` VARCHAR(48) NOT NULL DEFAULT '',
    `description` VARCHAR(512) NULL DEFAULT NULL,
    PRIMARY KEY (`id`)
)
COLLATE='utf8_general_ci'
ENGINE=InnoDB;

how are declared "not null" constraints ?

Are nulls replaced by an empty string at the insertion?

if the fields "not null" have a default value in the database, it is normal, insertion is always possible, and create returns always true...\

remove a DEFAULT value and try again, you will see.

but why in 1.3.4 its work?

if the fields "not null" have a default value in the database, it is normal, insertion is always possible, and create returns always true...

I dont know,

Are you really sure that the only change is the transition to Phalcon2...

i have two lxc containers: 1 php 5.5 phalcon1 2 php 5.6 with phalcon2

first work second none

I dont know too

I dont know,

Are you really sure that the only change is the transition to Phalcon2...

have you tried (php 5.5 + phalcon1 2) and (php 5.6 + phalcon2) with the same Mysql server ?

yes

have you tried (php 5.5 + phalcon1 2) and (php 5.6 + phalcon2) with the same Mysql server ?

Strange, but the normal behavior is with Phalcon 2 and php 5.6

Not null fields with default values do not generate errors if the field is null