* '2003-gii-namespaces' of https://github.com/etienneq/yii:
changed validation rules and error messages for base classes
changelog
Conflicts:
CHANGELOG
I propose the following improvements in the default Gii template for model:
1. Auxiliary appendixes which are `model` and `getDbConnection` should be in very bottom of the model class and not in the very top, because on top of class definition should reside the most important features, which here undoubtedly are `tableName`, `rules` and `relations`.
2. Docblock for `search` method includes the explanations about it, because it's not immediately clear for a newcomer why this method exists and how it should be used.
By the way, this `search` method is a clear violation of single responsibility principle anyway, because it forces a model to search for set of other models of the same class, and ActiveRecord is not about it.
If we use "schemaCachingDuration" value in db config, then use Gii model generator we have one problem. If table scheme updated without migration, we have old schema cache. I'm offer forcibly update db scheme if "schemaCachingDuration" used.
If we use "schemaCachingDuration" value in db config, then use Gii model
generator we have one problem. If table scheme updated without
migration, we have old schema cache. I'm offer forcibly update db scheme
if "schemaCachingDuration" used.
wxT+h
If we use "schemaCachingDuration" value in db config, then use Gii model
generator we have one problem. If table scheme updated without
migration, we have old schema cache. I'm offer forcibly update db scheme
if "schemaCachingDuration" used.
If we use "schemaCachingDuration" value in db config, then use Gii model
generator we have one problem. If table scheme updated without
migration, we have old schema cache. I'm offer forcibly update db scheme
if "schemaCachingDuration" used.
If we use "schemaCachingDuration" value in db config, then use Gii model
generator we have one problem. If table scheme updated without
migration, we have old schema cache. I'm offer forcibly update db scheme
if "schemaCachingDuration" used.
If we use "schemaCachingDuration" value in db config, then use Gii model
generator we have one problem. If table scheme updated without
migration, we have old schema cache. I'm offer forcibly update db scheme
if "schemaCachingDuration" used.
If we use "schemaCachingDuration" value in db config, then use Gii model
generator we have one problem. If table scheme updated without
migration, we have old schema cache. I'm offer forcibly update db scheme
if "schemaCachingDuration" used.
