Large object and image types are unsupported. This includes the SQL Server types nvarchar(max), varchar(max), and varbinary(max); and the DB2 LOB types.
The Tuning section of the view object overview editor has options to set the number of rows retrieved from the database. These settings are not supported for non-Oracle databases.
A view object's access mode cannot be set to Range Paging, Range Paging Auto Post, or Range Paging Incremental.
Before building a fusion web application you need to create a database connection. If you are developing against a non-Oracle database, you also need to register the appropriate JDBC driver with JDeveloper. You can do these two things together as follows.
|Column Name||Data Type||Comments|
|START_ID||NUMERIC(38,0)||Starting id in the range. To avoid duplicate key errors, you must make sure this value is higher than any existing primary key values in your database.|
|NEXT_ID||NUMERIC(38,0)||Next available id within current range (optional).|
|MAX_ID||NUMERIC(38,0)||Maximum id in the range|
|AUX_START_ID||NUMERIC(38,0)||Starting id in auxiliary block range (use 0 if no auxiliary block is available).|
|AUX_MAX_ID||NUMERIC(38,0)||Maximum id in the auxiliary block range (use 0 if no auxiliary block is available).|
|Database||Value of jbo.SQLBuilder|
|Other databases (MySQL, Sybase, etc)||SQL92|
|Database||How to Configure Passivation|
|SQL Server||Edit the application module's configuration and set the jbo.pcoll.mgr property to oracle.jbo.pcoll.pmgr.SQLServerPersistManager. See Note 1, below.|
|DB2||No action required: the correct persistence manager will be picked up automatically.|
|Other databases (MySQL, Sybase, etc)||Option 1, recommended: Implement a custom persistence manager and set the jbo.pcoll.mgr property to your persistence manager, see Note 2 below. |
Option 2: Do nothing, in which case file-based passivation will be used.