Skip to content

Commit

Permalink
TEIID-4294 documenting the issues with a swap/rename strategy
Browse files Browse the repository at this point in the history
  • Loading branch information
shawkins committed Feb 9, 2017
1 parent ee30053 commit 29e8057
Showing 1 changed file with 6 additions and 1 deletion.
7 changes: 6 additions & 1 deletion caching/External_Materialization.adoc
Expand Up @@ -26,7 +26,12 @@ The following are the types of data sources that have been tested to work in the

=== RDBMS Systems

* RDBMS - a relational database should work, as long as the user has the correct permissions to rename a table. Example databases; Oracle, Postgresql, MySQL, MS SqlServer, SAP Hana, etc.
* RDBMS - a relational database should work. Example databases; Oracle, Postgresql, MySQL, MS SqlServer, SAP Hana, etc.

If the database supports a transactional rename operation, you can use the default load strategy that uses a staging table and rely on renaming the staging table to the live table in the after load script.

NOTE: https://issues.jboss.org/browse/TEIID-4294[TEIID-4294] raises that not every database supports a transactional rename, either as separate or a block of statements.
If this is the case you should consider using a LOADNUMBER column, or a custom load strategy that maintains only a single table.

=== JBoss Data Grid (JDG)

Expand Down

0 comments on commit 29e8057

Please sign in to comment.