* '2003-gii-namespaces' of https://github.com/etienneq/yii:
changed validation rules and error messages for base classes
changelog
Conflicts:
CHANGELOG
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.