Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Gii model code generator fixed #1580

Merged
merged 12 commits into from
Oct 19, 2012
Merged

Gii model code generator fixed #1580

merged 12 commits into from
Oct 19, 2012

Conversation

SonkoDmitry
Copy link
Contributor

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.
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.
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.
@SonkoDmitry
Copy link
Contributor Author

thx, good remark. i fix it too and remove issue number from changelog

mdomba added a commit that referenced this pull request Oct 19, 2012
@mdomba mdomba merged commit 7950a58 into yiisoft:master Oct 19, 2012
@mdomba
Copy link
Member

mdomba commented Oct 19, 2012

Great, thanks for working on this.

@ghost ghost assigned mdomba Oct 19, 2012
@SonkoDmitry
Copy link
Contributor Author

thank YOU for help. I try to take what ever is the problem and close it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants