This issue seems to crop up when environment is set to development and all properties of a model pass a PHP is_integer() test. Set just one property as a string (varchar col works fine) and the issue disappears.
Looks to be somewhere in the core framework initialization, as extending ActiveRecord\Model directly doesn't help nor does bypassing a controller method and creating records by directly accessing a script, however the same model/table accessed by a script which doesn't load swpMVC, but just loads ActiveRecord does not suffer this issue.
This issue seems to crop up when environment is set to development and all properties of a model pass a PHP is_integer() test. Set just one property as a string (varchar col works fine) and the issue disappears.
Looks to be somewhere in the core framework initialization, as extending ActiveRecord\Model directly doesn't help nor does bypassing a controller method and creating records by directly accessing a script, however the same model/table accessed by a script which doesn't load swpMVC, but just loads ActiveRecord does not suffer this issue.