https://sourceforge.net/p/threeten/oldwiki/DateTimeCalendarInternalStorage/Recent changes to DateTimeCalendarInternalStorageenThu, 22 May 2014 22:08:04 -0000https://sourceforge.net/p/threeten/oldwiki/DateTimeCalendarInternalStorage/<div class="markdown_content"><p>This choice is about how to store data inside calendars. </p> <h2 id="option-1-year-month-day-hour-min-sec">Option 1 - year / month / day / hour / min / sec</h2> <p>This option would store data using the basic 6 fields. Unusual calendar systems would choose their own most important fields. </p> <p>Advantages: </p> <ul> <li>get/set to any of these specific fields is very quick </li> <li>resolving invalid dates is obvious, as the leapyear/month/day combination is easy to check </li> <li>add of small amounts within stored fields is easy </li> </ul> <p>Disadvantages: </p> <ul> <li>get/set to any other field is slow </li> <li>difficult to represent an object like&nbsp;!YearWeek (weekyear + week of year) as it doesn't fit </li> <li>add requires complex calculation </li> </ul> <h2 id="option-2-duration-from-epoch-in-seconds">Option 2 - duration from epoch in seconds</h2> <p>This option would store data using seconds. </p> <p>Advantages: </p> <ul> <li>get/set to all fields is calculated, those below day are quick </li> <li>add is quick for all fields except month/year </li> <li>able to represent any calendar, including ones like&nbsp;!YearWeek (weekyear + week of year) </li> <li>compareTo/equals/hashcode are quick </li> <li>conversion to an instant is quick </li> </ul> <p>Disadvantages: </p> <ul> <li>get/set to all fields requires calculation </li> <li>resolving invalid dates requires calculation of each of year/month/day </li> <li>get/set day/month/year requires complex calculation </li> <li>add month/year requires complex calculation </li> </ul> <h2 id="option-3-duration-from-epoch-in-seconds-and-months">Option 3 - duration from epoch in seconds and months</h2> <p>This option would store data using the 2 durations - seconds and months. Unusual calendar systems would choose their own fields (the ones with discontinuities). </p> <p>Advantages: </p> <ul> <li>get/set to all fields is calculated, most calculations (esp. day/month/year) are quick </li> <li>add is quick for all fields (unless an unusual field is not based on a standard field) </li> <li>able to represent any calendar, including ones like&nbsp;!YearWeek (weekyear + week of year), eg. by storing 1 duration in weeks </li> <li>add month/year is quick </li> </ul> <p>Disadvantages: </p> <ul> <li>get/set to all fields requires calculation, but this is quick </li> <li>resolving invalid dates requires calculation of each of year/month/day, but this is quick </li> <li>add fields below month requires potentially complex calculation if they go over 28 days </li> </ul> <hr /> <ul> <li><a class="" href="/p/threeten/oldwiki/ThreeTen/">Home page</a> </li> </ul></div>Stephen ColebourneThu, 22 May 2014 22:08:04 -0000https://sourceforge.netcba6940b2a856bc5a8c389ee8334fde9ef2c4bf7