You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In Kohana_ORM is possible to run a callback function that modifies the value when setting it on __set(). This is the same as using adaptors in Leap.
But I think that it's not worth to create a custom adaptor class wich calls another class, instead of calling that another class in first place.
Example is the password hashing with Auth::instance()->hash('password1') - with Kohana_ORM you can define the callback in the Model like this:
And you can define any callback functions there - even from the same Model.
As I have said earlyer, I find Leap potentialy very powerful, but it lacks of functionality that has in Kohana_ORM, and Leap should have all the functionality that has Kohana_ORM to be able to compete with it.
I have spent days trying to set everything up with Leap, but I'm stuck with all these functionalities missing from Kohana_ORM...
I hope that you will agree to implement all these things.
The text was updated successfully, but these errors were encountered:
Yes, I will be happy to get this added. This actually has been something that was in development but because we hadn't finished implementing it, I removed them because some were getting confused (thinking that it was implemented). I will totally agree with you as to making this apart of the project.
We are very thankful for you feedback.... It is very helpful in letting us know what is important to others and what things to focus on next.
So, the first 3 ways would either set value like $model->fields[$column]->internal_value, or when the values would be set from/to Model, it will set value like $this->fields[$column]->user_value.
Any comments about this approach? And which variant to make - 1st or 2nd? And what would be the best name for that set type?
And if you agree that this is ok, then I could write a code that's doing these modification callbacks.
In Kohana_ORM is possible to run a callback function that modifies the value when setting it on
__set()
. This is the same as using adaptors in Leap.But I think that it's not worth to create a custom adaptor class wich calls another class, instead of calling that another class in first place.
Example is the password hashing with
Auth::instance()->hash('password1')
- with Kohana_ORM you can define the callback in the Model like this:And you can define any callback functions there - even from the same Model.
As I have said earlyer, I find Leap potentialy very powerful, but it lacks of functionality that has in Kohana_ORM, and Leap should have all the functionality that has Kohana_ORM to be able to compete with it.
I have spent days trying to set everything up with Leap, but I'm stuck with all these functionalities missing from Kohana_ORM...
I hope that you will agree to implement all these things.
The text was updated successfully, but these errors were encountered: