RelationCollection.ToQueryTextNonAnsi Method  | 
 
            Converts the set of relations to a set of nested JOIN query elements using ANSI join syntaxis. Oracle 8i doesn't support ANSI join syntaxis
            and therefore the OracleDQE has its own join code. It uses a database specific creator object for database specific syntaxis, like the format of the
            tables / views and fields.
            
 
    Namespace: 
   SD.LLBLGen.Pro.ORMSupportClasses
    Assembly:
   SD.LLBLGen.Pro.ORMSupportClasses (in SD.LLBLGen.Pro.ORMSupportClasses.dll) Version: 5.4.0.0 (5.4.0)
Syntaxpublic string ToQueryTextNonAnsi(
	ref string nonAnsiWhereClause,
	string nonAnsiRootTableReference,
	string nonAnsiFieldSuffix
)
Public Function ToQueryTextNonAnsi ( 
	ByRef nonAnsiWhereClause As String,
	nonAnsiRootTableReference As String,
	nonAnsiFieldSuffix As String
) As String
Parameters
- nonAnsiWhereClause
 - Type: System.String
The non ANSI where clause. - nonAnsiRootTableReference
 - Type: System.String
The non ANSI root table reference.
            This parameter is set in UPDATE and DELETE statements where a multi-table relation filter is used.
            These queries wrap the joins produced with this routine in a subquery and the table used outside the subquery shouldn't be mentioned in the
            join list. So if this table reference is in the join list, it is skipped (however field1=field2 statements are added to link the outer table to the
            subquery logic). - nonAnsiFieldSuffix
 - Type: System.String
The non ANSI field suffix. For Oracle and PostGresql this is '(+)'. 
Return Value
Type: 
Stringthe string to use in the FROM clause
Implements
IRelationCollection.ToQueryTextNonAnsi(String, String, String)
RemarksAfter this calls the parameters produced are in the Parameters collection.
See Also