CVGM Radio

Development Area » Adding year
| Author | Thread |
|---|---|
Stefan_LDeleted by request 167 Posts #177 (16 years, 9 months ago) |
In most cases only the year of release is a known fact but it is impossible to add just the year because the system require day and month also.
|
| Quote | |
FishGuy876FishGuy876 / Brainstorm 495 Posts #179 (16 years, 9 months ago) |
I have considered this for a long time, even necta doesn't use the dates per-say. When I next make a DB change, i'll change it to year. Because we use South migrations, any existing dates will just be converted to year automatically.
|
| Quote | |
Stefan_LDeleted by request 167 Posts #180 (16 years, 9 months ago) |
ok.. so then i could just write whatever day and month as it will be year only eventually.
|
| Quote | |
FishGuy876FishGuy876 / Brainstorm 495 Posts #189 (16 years, 9 months ago) |
I have been looking at this code change, it appears that Django doesn't have a year-specific field. I can add a new one, which will cause the loss of all existing year data, but will allow only a year to be entered.
|
| Quote | |
Stefan_LDeleted by request 167 Posts #193 (16 years, 9 months ago) |
If you decide to upgrade then do it sooner than later so less year data is lost. I usually try and add date on each tune i upload... but i will probably not go thru and add date again after it is lost after the update.
|
| Quote | |
Stefan_LDeleted by request 167 Posts #205 (16 years, 9 months ago) |
Will it be changed for "Labels" also?
|
| Quote | |
FishGuy876FishGuy876 / Brainstorm 495 Posts #207 (16 years, 9 months ago) |
At some point yes, I may update for labels. I should do it globally for everything, or make it an optional field (because some people know the exact dates their songs were released).
|
| Quote |
Reply To This Forum Post
Before posting a new topic, or replying to an exiting one, please make sure that the content follows the guidlines for the website.
Please log in to post a reply.









