....................................................................................87 8.5.1.1. Dates................................................................................................87 Another important property of transactional databases is closely related to the notion of atomic up- dates: when multiple transactions are running concurrently, each one should not be able to see the incomplete for whole numbers, numeric for possibly fractional numbers, text for character strings, date for dates, time for time-of-day values, and timestamp for values containing both date and time. To create a

....................................................................................91 8.5.1.1. Dates.................................................................................................. for whole numbers, numeric for possibly fractional numbers, text for character strings, date for dates, time for time-of-day values, and timestamp for values containing both date and time. To create a 12 bytes time intervals -178000000 years 178000000 years 1 microsecond / 14 digits date 4 bytes dates only 4713 BC 32767 AD 1 day time [ (p) ] [ without time zone ] 8 bytes times of day only00:00:00

....................................................................................98 8.5.1.1. Dates.................................................................................................. for whole numbers, numeric for possibly fractional numbers, text for character strings, date for dates, time for time-of-day values, and timestamp for values containing both date and time. To create a 12 bytes time intervals -178000000 years 178000000 years 1 microsecond / 14 digits date 4 bytes dates only 4713 BC 5874897 AD 1 day time [ (p) ] [ without time zone ] 8 bytes times of day only 00:00:00

....................................................................................98 8.5.1.1. Dates.................................................................................................. for whole numbers, numeric for possibly fractional numbers, text for character strings, date for dates, time for time-of-day values, and timestamp for values containing both date and time. To create a 12 bytes time intervals -178000000 years 178000000 years 1 microsecond / 14 digits date 4 bytes dates only 4713 BC 32767 AD 1 day time [ (p) ] [ without time zone ] 8 bytes times of day only 00:00:00

...................................................................................108 8.5.1.1. Dates..............................................................................................109 8 Another important property of transactional databases is closely related to the notion of atomic up- dates: when multiple transactions are running concurrently, each one should not be able to see the incomplete for whole numbers, numeric for possibly fractional numbers, text for character strings, date for dates, time for time-of-day values, and timestamp for values containing both date and time. To create a

....................................................................................97 8.5.1.1. Dates................................................................................................98 Another important property of transactional databases is closely related to the notion of atomic up- dates: when multiple transactions are running concurrently, each one should not be able to see the incomplete for whole numbers, numeric for possibly fractional numbers, text for character strings, date for dates, time for time-of-day values, and timestamp for values containing both date and time. To create a

...................................................................................113 8.5.1.1. Dates..............................................................................................113 8 Another important property of transactional databases is closely related to the notion of atomic up- dates: when multiple transactions are running concurrently, each one should not be able to see the incomplete for whole numbers, numeric for possibly fractional numbers, text for character strings, date for dates, time for time-of-day values, and timestamp for values containing both date and time. To create a

...................................................................................101 8.5.1.1. Dates.................................................................................................. for whole numbers, numeric for possibly fractional numbers, text for character strings, date for dates, time for time-of-day values, and timestamp for values containing both date and time. To create a Chapter 8. Data Types Name Storage Size Description Low Value High Value Resolution date 4 bytes dates only 4713 BC 5874897 AD 1 day time [ (p) ] [ without time zone ] 8 bytes times of day only 00:00:00

...................................................................................101 8.5.1.1. Dates.................................................................................................. for whole numbers, numeric for possibly fractional numbers, text for character strings, date for dates, time for time-of-day values, and timestamp for values containing both date and time. To create a Chapter 8. Data Types Name Storage Size Description Low Value High Value Resolution date 4 bytes dates only 4713 BC 5874897 AD 1 day time [ (p) ] [ without time zone ] 8 bytes times of day only 00:00:00

...................................................................................121 8.5.1.1. Dates..............................................................................................121 8 Another important property of transactional databases is closely related to the notion of atomic up- dates: when multiple transactions are running concurrently, each one should not be able to see the incomplete for whole numbers, numeric for possibly fractional numbers, text for character strings, date for dates, time for time-of-day values, and timestamp for values containing both date and time. To create a