A distributed Informix database has no upper limit on table or database size. Note (13): Informix DECIMAL type supports up to 32 decimal digits of precision with a range of 10^-130 to 10^125. Fixed and variable precision are supported. Tables and views Information about what tables and views (other than basic ones) are supported natively. Note (1): Server provides tempdb, which can be used for public and private (for the session) temp tables. Note (2): Materialized views are not supported in Informix; the term is used in IBM's documentation to refer to a temporary table created to run the view's query when it is too complex, but one cannot for example define the way it is refreshed or build an index on it. The term is defined in the Informix Performance Guide. Note (4): Materialized views can be emulated using stored procedures and triggers. Indexes Information about what indexes (other than basic B-/B+ tree indexes) are supported natively. Note (1): The users need to use a function from freeAdhocUDF library or similar. Note (2): Can be implemented for most data types using expression-based indexes. Note (3): Can be emulated by indexing a computed column (doesn't easily update) or by using an "Indexed View" (proper name not just any view works). Note (4): Used for InMemory ColumnStore index, temporary hash index for hash join, Non/Cluster & fill factor. Note (5): InnoDB automatically generates adaptive hash index entries as needed. Note (6): Can be implemented using Function-based Indexes in Oracle 8i and higher, but the function needs to be used in the sql for the index to be used. Note (7): A PostgreSQL functional index can be used to reverse the order of a field. Note (10): B+ tree and full-text only for now. Note (11): R-Tree indexing available in base edition with Locator but some functionality requires Personal Edition or Enterprise Edition with Spatial option. Database capabilities Note (1): Recursive CTEs introduced in 11gR2 supersedes similar construct called CONNECT BY. Data types Other objects Information about what other objects are supported natively. Note (1): Both function and procedure refer to internal routines written in SQL and/or procedural language like PL/SQL. External routine refers to the one written in the host languages, such as C, Java, Cobol, etc. "Stored procedure" is a commonly used term for these routine types. However, its definition varies between different database vendors. Note (2): In Derby, H2,