Specifications

Server Behaviors 173
• true if the searchPattern does not have to be found to identify the participant.
• false (default) if the searchPattern must be found.
For example, consider the following simple recordset string:
<%
var Recordset1 = Server.CreateObject("ADODB.Recordset");
Recordset1.ActiveConnection = "dsn=andescoffee;";
Recordset1.Source = "SELECT * FROM PressReleases";
Recordset1.CursorType = 3;
Recordset1.Open();
%>
The search patterns must identify the participant and extract several parameters. However,
if a parameter such as
cursorType is not found, you should still recognize this as a recordset.
The cursor parameter is optional. In the EDML, the search patterns might look like the
following example:
<searchPattern paramNames="rs">/var (\w+) = Server.CreateObject/
</searchPattern>
<searchPattern paramNames="src">/ActiveConnection = "([^\r\n]*)"/¬
</searchPattern>
<searchPattern paramNames="conn">/Source = "([^\r\n]*)"/¬
</searchPattern>
<searchPattern paramNames="cursor" isOptional="true">¬
/CursorType = (\d+)/
</searchPattern>
The first three patterns are required to identify the recordset. If the last parameter is not found,
the recordset is still identified.
EDML Tag: updatePatterns
Description
This optional advanced feature allows precise updates of the participant. Without this tag, the
participant is updated automatically by replacing the entire participant text each time. If you
specify an
<updatePatterns> tag, it must contain specific patterns to find and replace each
parameter within the participant.
This tag is beneficial if the user edits the participant text. It performs precise updates only to the
parts of the text that need changing.
Parent
implementation
Type
Block tag.
Required
No.