Sha256: 0329414511d3b4aba6e37a3b52d942fd6d16abffbe2788c8c69e57646dedc671

Contents?: true

Size: 678 Bytes

Versions: 8

Compression:

Stored size: 678 Bytes

Contents

|Subset Query:employees hired before|10-Dec-1980                     |
|employee number                    |first name|last name|hire date  |
|1429                               |Bob       |Martin   |10-Oct-1974|

The first thing to notice is the ''Subset Query:'' in the first cell of the table.  This tells the Slim table processor that this is a subset query table. Subset query tables are almost identical to [[Query tables][QueryTable]] except that we only need to put those rows into the table that we want to make sure to exist in the query response.

Our definition of subset here is not ''proper'' subset. Thus the table may contain all the rows of the query response.

Version data entries

8 entries across 8 versions & 1 rubygems

Version Path
xcfit-0.9.0 XCFitDemo/FitNesseRoot/FitNesse/UserGuide/WritingAcceptanceTests/SliM/SubsetQueryTable/content.txt
xcfit-0.8.0 XCFitDemo/FitNesseRoot/FitNesse/UserGuide/WritingAcceptanceTests/SliM/SubsetQueryTable/content.txt
xcfit-0.7.0 XCFitDemo/FitNesseRoot/FitNesse/UserGuide/WritingAcceptanceTests/SliM/SubsetQueryTable/content.txt
xcfit-0.6.0 XCFitDemo/FitNesseRoot/FitNesse/UserGuide/WritingAcceptanceTests/SliM/SubsetQueryTable/content.txt
xcfit-0.5.0 XCFitDemo/FitNesseRoot/FitNesse/UserGuide/WritingAcceptanceTests/SliM/SubsetQueryTable/content.txt
xcfit-0.4.0 XCFitDemo/FitNesseRoot/FitNesse/UserGuide/WritingAcceptanceTests/SliM/SubsetQueryTable/content.txt
xcfit-0.3.0 XCFitDemo/FitNesseRoot/FitNesse/UserGuide/WritingAcceptanceTests/SliM/SubsetQueryTable/content.txt
xcfit-0.2.0 XCFitDemo/FitNesseRoot/FitNesse/UserGuide/WritingAcceptanceTests/SliM/SubsetQueryTable/content.txt