From dcfafecace8ed5f60802b1862f725c78bf09a98f Mon Sep 17 00:00:00 2001 From: eegeek Date: Thu, 18 Aug 2011 12:38:22 +0000 Subject: [PATCH] SYMMETRICDS-488 --- symmetric/symmetric-assemble/src/docbook/configuration.xml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/symmetric/symmetric-assemble/src/docbook/configuration.xml b/symmetric/symmetric-assemble/src/docbook/configuration.xml index 6e325da373..716685943a 100644 --- a/symmetric/symmetric-assemble/src/docbook/configuration.xml +++ b/symmetric/symmetric-assemble/src/docbook/configuration.xml @@ -777,10 +777,10 @@ values An efficient way to select a subset of data from a table for an initial load is to provide an initial_load_select clause on . This clause, if present, is applied as a where clause to the SQL used to select the data to be loaded. + The clause may use "t" as an alias for the table being loaded, if needed. If an initial_load_select clause is provided, data will not be passed through the - configured router during initial load. In cases where custom routing is done using a feature like Relational Routing, - an initial_load_select clause will always need to be provided because the router would not - function properly with initial load data. + configured router during initial load. In cases where routing is done using a feature like Subselect Router, + an initial_load_select clause matching the subselect's criteria would be a more efficient approach. One example of the use of an initial load select would be if you wished to only load data created more recently than the start of year 2011. Say, for example,