Database Mashable Support and Limitations
MashZone NextGen supports databases with a JDBC 2.1 compliant driver. Some databases support valid names that
MashZone NextGen does not support. See
Database Characters and Names That Are Not Supported for details.
Database mashables can use any combination of tables, views or stored procedures defined in one schema or catalog within one datasource. MashZone NextGen does not support distributed transactions.
MashZone NextGen does not support columns with an image datatype.
Currently, MashZone NextGen handles packages for stored procedures and REF CURSOR types in Oracle databases only, with the following limitations:
Both weakly- and strongly-typed REF CURSORs are supported.
REF CURSORs are supported only in OUT parameters for stored procedures or as the return type for functions.
REF CURSORs are not supported as IN or INOUT parameters.
Nested REF CURSORs are not supported.
See also
Valid Date Formats for
MashZone NextGen
Mashables and Mashups for the specific date formats you may use in input parameters to database mashable operations.
EEEE, MMMM DD, YYYY | MMMM DD, YYYY | MMM DD, YYYY |
Where EEEE is the day of the week, MMMM is the full month name and MMM is a three-character abbreviation of the month. |
MM/DD/YY hh:mm:ss a z | Or these formats where time uses a twelve-hour clock (1-12), a is AM or PM and z indicates the time zone. |
MM/DD/YY hh:mm:ss a |
MM/DD/YY hh:mm a |
MM/DD/YY |
And finally, these formats where time uses a 24-hour clock |
YYYY/MM/DD hh:mm:ss.sss | YYYY-MM-DD hh:mm:ss.sss | YYYY.MM.DD hh:mm:ss.sss |
YYYY/MM/DD hh:mm:ss | YYYY-MM-DD hh:mm:ss | YYYY.MM.DD hh:mm:ss |
YYYY/MM/DD hh:mm | YYYY-MM-DD hh:mm | YYYY.MM.DD hh:mm |
YYYY/MM/DD | YYYY-MM-DD | YYYY.MM.DD |