17
17
* Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA
20
#include <drizzled/server_includes.h>
20
#include "drizzled/server_includes.h"
22
#include <drizzled/function/time/microsecond.h>
25
MICROSECOND(a) is a function ( extraction) that extracts the microseconds
28
a: Datetime or time value
22
#include "drizzled/temporal.h"
23
#include "drizzled/error.h"
24
#include "drizzled/function/time/microsecond.h"
32
26
int64_t Item_func_microsecond::val_int()
36
if (!get_arg0_time(<ime))
37
return ltime.second_part;
30
if (args[0]->is_null())
32
/* For NULL argument, we return a NULL result */
38
* Because of the ridiculous way in which MySQL handles
39
* TIME values (it does implicit integer -> string conversions
40
* but only for DATETIME, not TIME values) we must first
41
* try a conversion into a TIME from a string. If this
42
* fails, we fall back on a DATETIME conversion. This is
43
* necessary because of the fact that DateTime::from_string()
44
* looks first for DATETIME, then DATE regex matches. 6 consecutive
45
* numbers, say 231130, will match the DATE regex YYMMDD
46
* with no TIME part, but MySQL actually implicitly treats
47
* parameters to SECOND(), HOUR(), and MINUTE() as TIME-only
48
* values and matches 231130 as HHmmSS!
50
* Oh, and Brian Aker MADE me do this. :) --JRP
52
drizzled::Time temporal_time;
54
char time_buff[DRIZZLE_MAX_LENGTH_DATETIME_AS_STRING];
55
String tmp_time(time_buff,sizeof(time_buff), &my_charset_utf8_bin);
56
String *time_res= args[0]->val_str(&tmp_time);
57
if (! temporal_time.from_string(time_res->c_ptr(), time_res->length()))
60
* OK, we failed to match the first argument as a string
61
* representing a time value, so we grab the first argument
62
* as a DateTime object and try that for a match...
64
drizzled::DateTime temporal_datetime;
65
Item_result arg0_result_type= args[0]->result_type();
67
switch (arg0_result_type)
71
* For doubles supplied, interpret the arg as a string,
72
* so intentionally fall-through here...
73
* This allows us to accept double parameters like
74
* 19971231235959.01 and interpret it the way MySQL does:
75
* as a TIMESTAMP-like thing with a microsecond component.
76
* Ugh, but need to keep backwards-compat.
80
char buff[DRIZZLE_MAX_LENGTH_DATETIME_AS_STRING];
81
String tmp(buff,sizeof(buff), &my_charset_utf8_bin);
82
String *res= args[0]->val_str(&tmp);
83
if (! temporal_datetime.from_string(res->c_ptr(), res->length()))
86
* Could not interpret the function argument as a temporal value,
87
* so throw an error and return 0
89
my_error(ER_INVALID_DATETIME_VALUE, MYF(0), res->c_ptr());
95
if (temporal_datetime.from_int64_t(args[0]->val_int()))
97
/* Intentionally fall-through on invalid conversion from integer */
101
* Could not interpret the function argument as a temporal value,
102
* so throw an error and return 0
105
char buff[DRIZZLE_MAX_LENGTH_DATETIME_AS_STRING];
106
String tmp(buff,sizeof(buff), &my_charset_utf8_bin);
109
res= args[0]->val_str(&tmp);
111
my_error(ER_INVALID_DATETIME_VALUE, MYF(0), res->c_ptr());
115
return (int64_t) temporal_datetime.useconds();
117
return (int64_t) temporal_time.useconds();