Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork5.3k
Change Sql Field name because it's reserved#5567
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
rmed19 commentedJul 28, 2015
| Q | A |
|---|---|
| Doc fix? | yes |
| New docs? | no |
| Applies to | 2.3+ |
| Fixed tickets | #5566 |
javiereguiluz commentedJul 28, 2015
@rmed19 👍 for changing the name. However, I'd like to propose a different new name. What if we use |
wouterj commentedJul 28, 2015
👍 |
wouterj commentedJul 28, 2015
Thank you@rmed19 for catching this error. Congratz on your first ever doc contribution! You'll receive the doc contributor badge within some days. I've renamed the column to |
rmed19 commentedJul 28, 2015
Yes, created_at is more common, so it's will be better to change created_date to it |