Rose::DB::Informix(3pm) | User Contributed Perl Documentation | Rose::DB::Informix(3pm) |
Rose::DB::Informix - Informix driver class for Rose::DB.
use Rose::DB; Rose::DB->register_db( domain => 'development', type => 'main', driver => 'Informix', database => 'dev_db', host => 'localhost', username => 'devuser', password => 'mysecret', server_time_zone => 'UTC', ); Rose::DB->default_domain('development'); Rose::DB->default_type('main'); ... # Set max length of varchar columns used to emulate the array data type Rose::DB::Informix->max_array_characters(128); $db = Rose::DB->new; # $db is really a Rose::DB::Informix-derived object $dt = $db->parse_datetime_year_to_minute(...); $val = $db->format_datetime_year_to_minute($dt); $dt = $db->parse_datetime_year_to_second(...); $val = $db->format_datetime_year_to_second($dt); ...
Rose::DB blesses objects into a class derived from Rose::DB::Informix when the driver is "informix". This mapping of driver names to class names is configurable. See the documentation for Rose::DB's new() and driver_class() methods for more information.
This class cannot be used directly. You must use Rose::DB and let its new() method return an object blessed into the appropriate class for you, according to its driver_class() mappings.
Only the methods that are new or have different behaviors than those in Rose::DB are documented here. See the Rose::DB documentation for the full list of methods.
Informix does not have a native "ARRAY" data type, but it can be emulated using a "VARCHAR" column and a specially formatted string. The formatting and parsing of this string is handled by the "format_array()" and "parse_array()" object methods. The maximum length limit is honored by the "format_array()" object method.
Informix does have a native "SET" data type, serviced by the "parse_set()" and "format_set()" object methods. This is a better choice than the emulated array data type if you don't care about the order of the stored values.
If the resulting string is longer than "max_array_characters()", a fatal error will occur.
If a LIST of more than one item is passed, a reference to an array containing the values in LIST is returned.
If a an ARRAYREF is passed, it is returned as-is.
If STRING is a valid boolean keyword (according to validate_boolean_keyword) or if it looks like a function call (matches /^\w+\(.*\)$/) and keyword_function_calls is true, then it is returned unmodified. Returns undef if STRING could not be parsed as a valid "boolean" value.
If STRING is a valid date keyword (according to validate_date_keyword) it is returned unmodified. Returns undef if STRING could not be parsed as a valid "DATE" value.
If STRING is a valid "datetime year to second" keyword (according to validate_datetime_year_to_second_keyword) it is returned unmodified. Returns undef if STRING could not be parsed as a valid "DATETIME YEAR TO SECOND" value.
If STRING is a valid "datetime year to fraction" keyword (according to validate_datetime_year_to_fraction_keyword) it is returned unmodified. Returns undef if STRING could not be parsed as a valid "DATETIME YEAR TO FRACTION" value.
If STRING is a valid "datetime year to fraction" keyword (according to validate_datetime_year_to_fraction_keyword) it is returned unmodified. Returns undef if STRING could not be parsed as a valid "DATETIME YEAR TO FRACTION(N)" value.
If STRING is a valid "datetime year to minute" keyword (according to validate_datetime_year_to_minute_keyword) it is returned unmodified. Returns undef if STRING could not be parsed as a valid "DATETIME YEAR TO MINUTE" value.
If STRING is a valid "datetime year to month" keyword (according to validate_datetime_year_to_month_keyword) it is returned unmodified. Returns undef if STRING could not be parsed as a valid "DATETIME YEAR TO MONTH" value.
If STRING is a valid "datetime year to second" keyword (according to validate_datetime_year_to_second_keyword) it is returned unmodified. Returns undef if STRING could not be parsed as a valid "DATETIME YEAR TO SECOND" value.
If a LIST of more than one item is passed, a reference to an array containing the values in LIST is returned.
If a an ARRAYREF is passed, it is returned as-is.
If STRING is a valid timestamp keyword (according to validate_timestamp_keyword) it is returned unmodified. Returns undef if STRING could not be parsed as a valid "DATETIME YEAR TO FRACTION(5)" value.
TRUE FALSE
current today
The keywords are not case sensitive. Any string that looks like a function call (matches /^\w+\(.*\)$/) is also considered a valid date keyword if keyword_function_calls is true.
current current year to second current year to minute current year to hour current year to day current year to month today
The keywords are not case sensitive. Any string that looks like a function call (matches /^\w+\(.*\)$/) is also considered a valid datetime keyword if keyword_function_calls is true.
current current year to fraction current year to fraction(1) current year to fraction(2) current year to fraction(3) current year to fraction(4) current year to fraction(5) current year to second current year to minute current year to hour current year to day current year to month today
The keywords are not case sensitive. Any string that looks like a function call (matches /^\w+\(.*\)$/) is also considered a valid "datetime year to fraction" keyword if keyword_function_calls is true.
current current year to second current year to minute current year to hour current year to day current year to month today
The keywords are not case sensitive. Any string that looks like a function call (matches /^\w+\(.*\)$/) is also considered a valid "datetime year to minute" keyword if keyword_function_calls is true.
current current year to second current year to minute current year to hour current year to day current year to month today
The keywords are not case sensitive. Any string that looks like a function call (matches /^\w+\(.*\)$/) is also considered a valid "datetime year to month" keyword if keyword_function_calls is true.
current current year to second current year to minute current year to hour current year to day current year to month today
The keywords are not case sensitive. Any string that looks like a function call (matches /^\w+\(.*\)$/) is also considered a valid "datetime year to second" keyword if keyword_function_calls is true.
current current year to fraction current year to fraction(1) current year to fraction(2) current year to fraction(3) current year to fraction(4) current year to fraction(5) current year to second current year to minute current year to hour current year to day current year to month today
The keywords are not case sensitive. Any string that looks like a function call (matches /^\w+\(.*\)$/) is also considered a valid timestamp keyword if keyword_function_calls is true.
John C. Siracusa (siracusa@gmail.com)
Copyright (c) 2010 by John C. Siracusa. All rights reserved. This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself.
2023-03-04 | perl v5.36.0 |