Can't use expressions anymore because of Kohana_BadData_Exception

[taai]

Now, when there is this this validation check built in, I can't use expressions anymore.

<?php
// "purchased" is field of DB_ORM_Field_DateTime
$car->purchased = DB_SQL::expr('now()');

This does throw an Kohana_BadData_Exception exception, because my expression doesn't pass DB_ORM_Field_DateTime built in validation.

If I can't use expressions, the Leap get's useless.

Possible solutions

In the validation there should check if the value is instanceof DB_SQL_Expression and if so, pass the validation, don't check anything. Also this has to do with __set() where should be checked if the value is an expression and if it is, don't do the settype().

Actually this gets more complicated! If you use expressions, you must save the model by setting the first (and only) argument $reload to TRUE:

<php
$car->save(TRUE);

In that way the model will get reloaded from the database. This must be done because the expressions that will get executed, but for normal save() the values will be what you set them with - the expressions. So, also in the save() method, there must be a instanceof check to set $reload = TRUE; automatically, if one of the values is an expression.

Discussion

I know that you all have things to do and you can't spend much time to all projects, that's why we collaborate to develop projects together. I want to know - what things I'm allowed to change? I have these ideas, but I don't want to code things, that you will discard, so I have to know what is the idea of Leap's structure. Can we have a Skype chat about the structure? Otherways I'm alone with my thoughts here.

[bluesnowman]

If you can, send us an email to spadefoot.oss@gmail.com and then we will send you our Skype username to chat.

[bluesnowman]

As for your ideas, they are great. Your contributions are highly considered and we are very happy to implement them.