An error occurred fetching the project authors.
- 26 Jun, 2004 1 commit
-
-
serg@serg.mylan authored
(table opened in my_tz_init, was removed from thd->open_tables in tz_load_from_db w/o being unlocked, so it was stayng in open_cache forever preventing the latter from being free'd in table_cache_free)
-
- 25 Jun, 2004 1 commit
-
-
dlenev@brandersnatch.localdomain authored
problems with unresolved dependancies on some platforms.
-
- 24 Jun, 2004 1 commit
-
-
konstantin@mysql.com authored
work (prepared statements)" and after-review fixes: - str_to_TIME renamed to str_to_datetime to pair with str_to_time - functions str_to_time and str_to_TIME moved to sql-common - send_data_str now supports MYSQL_TYPE_TIME, MYSQL_TIME_DATE, MYSQL_TIME_DATETIME types of user input buffers. - few more comments in the client library - a test case added.
-
- 23 Jun, 2004 3 commits
-
-
serg@serg.mylan authored
-
dlenev@brandersnatch.localdomain authored
-
monty@mysql.com authored
-
- 21 Jun, 2004 1 commit
-
-
dlenev@brandersnatch.localdomain authored
Now we are using time zone abbreviations in debug builds or in utlities only. Tried to remove warnings generated by compiler by using more proper types for members of time zone describing structures. Removed unused variables. Fixed test_time to be able to build on FreeBSD without much problems. Portability fix: resolved ambiguity of abs() function.
-
- 18 Jun, 2004 1 commit
-
-
dlenev@brandersnatch.localdomain authored
Added basic per-thread time zone functionality (based on public domain elsie-code). Now user can select current time zone (from the list of time zones described in system tables). All NOW-like functions honor this time zone, values of TIMESTAMP type are interpreted as values in this time zone, so now our TIMESTAMP type behaves similar to Oracle's TIMESTAMP WITH LOCAL TIME ZONE (or proper PostgresSQL type). WL#1266 "CONVERT_TZ() - basic time with time zone conversion function". Fixed problems described in Bug #2336 (Different number of warnings when inserting bad datetime as string or as number). This required reworking of datetime realted warning hadling (they now generated at Field object level not in conversion functions). Optimization: Now Field class descendants use table->in_use member instead of current_thd macro.
-