Created by Andrew Hutchings on 2013-04-21 and last modified on 2013-04-21
Get this branch:
bzr branch lp:~linuxjedi/libdrizzle/date-time
Only Andrew Hutchings can upload to this branch. If you are Andrew Hutchings please log in for upload directions.

Branch merges

Related bugs

Related blueprints

Branch information

Andrew Hutchings
Drizzle Client & Protocol Library

Recent revisions

120. By Andrew Hutchings on 2013-04-21

Fix UDS test SKIP

119. By Andrew Hutchings on 2013-04-21

Fix connect SKIP in common.c

118. By Andrew Hutchings on 2013-04-21

Fix build errors in recent compilers

117. By Andrew Hutchings on 2013-04-21

Merge 5.1 into branch

116. By Andrew Hutchings on 2013-04-21

Fixes build error

115. By Wim Lewis on 2013-03-25

Reorganize string formatting in time_to_string() and timestamp_to_string().
Reduced duplication of code for formatting similar types.
Combine hours+days when converting to a string, but leave them separate in the binary structure, to match the wire format.
Make sure we have leading zeroes on the microseconds.
Add a comment about the right way to decide whether to include the microseconds field (a bug currently caught by the datetypes test).

114. By Wim Lewis on 2013-03-19

Don't leave uninitialized data at the end of datetime_st

113. By Wim Lewis on 2013-03-19

Give drizzle_unpack_[date]time()'s result an accurate type
(drizzle_datetime_st * rather than char *).

112. By Wim Lewis on 2013-03-18

Corrected packing of date/time types.
These fields start with a length byte to tell the server how many subfields we're sending.
Be sure to send optional subfields even if zero if they're needed to let us send a later optional subfield that isn't zero.

111. By Wim Lewis on 2013-03-13

Send timestamp parameters as TYPE_TIMESTAMP, not TYPE_TIME.
Also be sure there's no uninitialized data in the timestamp struct.

Branch metadata

Branch format:
Branch format 7
Repository format:
Bazaar repository format 2a (needs bzr 1.16 or later)
Stacked on:
This branch contains Public information 
Everyone can see this information.