Wojciech Ślawski
Wojciech Ślawski
I don't understand this, can't we just throw exception if wrong type is passed and that's it? Not sure why we should handle stuff like this.
Well will see, maybe it's not so bad idea to just return false if type is wrong.
As i wrote earlier. Did you tried it with subquieries INSTEAD of joins ? This types of PHQL queries i guess are not supported. But i think that subqueries should...
``` UPDATE Version LEFT JOIN RelArtistTrack ON RelArtistTrack.TrackRef=Version.TrackRef LEFT JOIN Artist ON RelArtistTrack.ComposerRef=Artist.TrackRef SET Version.Price=Version.PriceOrig WHERE RelArtistTrack.ComposerRef=:artistId: AND Artist.Status=1 AND (Version.Price=0) OR (Version.Price IS NULL) ``` will be something like:...
We just don't have partial models, i guess if we implement Data Mapper then we can consider this @niden
It's not suddenly, it's expected behavior and not a bug. This is due to all active record events we have - to make sure that they work correctly and do...
I'm not saying we shouldn't implement this, im saying that this was a choice which was made to have Row object instead of full model. I guess on data mapper...
There are no modules system in cli mode. You would need to write your own dispatcher for multi module cli. You can see this - https://forum.phalconphp.com/discussion/7283/multiple-module-cli
It's not set because Dispatcher cli doesn't use modules at all. It's not an issue. Just dispatcher cli/router doesn't support modules.
@allaud for me filters are casuing inf digest loop.