View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0000362 | HTML & PERL | Bug Report - Database | public | 2006-07-05 09:17 | 2007-12-06 08:28 |
Reporter | DerIdiot | Assigned To | exp | ||
Priority | normal | Severity | minor | Reproducibility | always |
Status | resolved | Resolution | fixed | ||
Summary | 0000362: indefinite dates - ?? handling | ||||
Description | was discussed on irc and exp knows about it. added the log below anyway to cut it short. problem lies in the fact that ?? is treated as 01 internal. startdate: 05.10.2006 enddate: ??.??.2006 would throw as anidb interpretes it as 01.01.2006 suggestions for how to fix this are to be found in the log | ||||
Additional Information | <EXP[BUSY]> i.e. ??.??.2006 becomes 01.01.2006 <DerIdiot|away> we know which is bad <pelican> Yes, that was obvious <Chii[AR]> ANIME: DigiGirl POP! ~Strawberry & Pop Mix Flavor~ (1873), 26 eps, Year: 2003, Genre: Comedy, DB: 0 eps/0 files, More info: http://anidb.info/a1873 <DerIdiot> startdate: 17.02.2003 <DerIdiot> if you try to set ??.??.2003 as endate it throws <DerIdiot> ERROR: 16 - end date lies before air date <pelican> Indeed, how about setting start dates to the beginning of the period and end dates to the end? <pelican> That should deal with the associated issues <pelican> And save you from writing real logic to cover it <EXP[BUSY]> should be possible <EXP[BUSY]> write a tracker item :P <rar> <EXP[BUSY]> i.e. ??.??.2006 becomes 01.01.2006 <- I suggested that it should actually become 01.01.2007-one second <pelican> That's what I meant <pelican> By the end of the period <rar> so, the unknowns collate at the end of the knowns, rather than before <pelican> Is there any reason to do that for start dates too? <rar ] yeah, neater collation <pelican> Hmm <pelican> Might confuse future sanity checks though <pelican> Example of possible sanity check that would not work with that implementation: a check for all regular episode dates being within the anime's time frame (not necessarily saying that this is a good check, at least not a strict one) <pelican> Start date to first second and end date to last doesn't have this problem of course | ||||
Tags | No tags attached. | ||||
Date Modified | Username | Field | Change |
---|---|---|---|
2006-07-05 09:17 | DerIdiot | New Issue | |
2006-07-05 09:18 | DerIdiot | Additional Information Updated | |
2006-07-06 09:00 | DerIdiot | Summary | indefinite dates => indefinite dates - ?? handling |
2006-07-26 12:24 | DerIdiot | Assigned To | => exp |
2006-07-26 12:24 | DerIdiot | Status | new => resolved |
2007-12-06 08:28 | epoximator | Resolution | open => fixed |