\n\tPID\n\t\n\t\tPROPERTY

\n\t\n\t\n\t\tLINK.ID=PROPERTY.ID\n\t\n\t\n\t\tUnit\n\t\tUNIT\n\t\n\t\n\t\tHouse From\n\t\tinteger\n\t\tPROP_NO\n\t\n\t\n\t\tHouse To\n\t\tinteger\n\t\tPROP_NO\n\t\n\t\n\t\tSuburb\n\t\tlistbox\n\t\ttrue\n\t\tSUBURB\n\t\tdd_suburbs\n\t\n\t\n\t\tdd_roadtypes\n\t\t\n\t\t\tRoad Name\n\t\t\tlistbox\n\t\t\tROADNAME_CODE\n\t\t\troadname_code\n\t\t\troadname\n\t\t\n\t\t\n\t\t\tRoad Type\n\t\t\tlistbox\n\t\t\tROADTYPE_CODE\n\t\t\troadtype_code\n\t\t\troadtype\n\t\t\n\t\n\t\n\t\tPostcode\n\t\tinteger\n\t\t\n\t\t\t\n\t\t\n\t\n\t\n\t\t\n\t\t\t= ${house_from} and PROP_NO <= ${house_to}]]>\n\t\t\n\t\n\t\n\t\t50\n\t\tfalse\n\t\t0\n\t\t300\n\t\ttrue\n\t\t2000\n\t\tfalse\n\t\t120\n\t\tLRU\n\t\n\t\n\t\t2000\n\t\n\n","type":"text"}]},{"type":"paragraph","content":[{"type":"hardBreak"}]},{"type":"heading","attrs":{"level":5},"content":[{"text":"Searching on a date or a range of dates","type":"text","marks":[{"type":"strong"}]}]},{"type":"codeBlock","attrs":{"language":"xml"},"content":[{"text":"\n\tproperty\n\tby Sale Date\n\tLocate a property by the date of its sale\n\tdatasource.property\n\tPROP_SALE

\n\tPROPERTYID\n\t\n\t\tStart Date\n\t\ttext-box\n\t\tdate\n\t\tSALEDATE\n\t\n\t\n\t\tEnd Date\n\t\ttext-box\n\t\tdate\n\t\tSALEDATE\n\t\n\t\n\t\t\n\t\t\t\n\t\t\n\t\n\n","type":"text"}]},{"type":"paragraph","content":[{"type":"hardBreak"}]},{"type":"panel","attrs":{"panelType":"warning"},"content":[{"type":"paragraph","content":[{"text":"The ","type":"text"},{"text":"trueValue","type":"text","marks":[{"type":"code"}]},{"text":"/","type":"text"},{"text":"falseValue","type":"text","marks":[{"type":"code"}]},{"text":" settings in the checkbox in the following example only work for Weave 2.5+","type":"text"}]}]},{"type":"paragraph","content":[{"type":"hardBreak"}]},{"type":"heading","attrs":{"level":5},"content":[{"text":"Search with checkbox and radiobutton","type":"text","marks":[{"type":"strong"}]}]},{"type":"codeBlock","attrs":{"language":"xml"},"content":[{"text":"\n\tcertificate\n\tby Status\n\tLocate a certificate by its current status\n\tdatasource.main\n\tCERTIFICATES

\n\tID\n\t\n\t\tCurrent\n\t\tcheckbox\n\t\tIS_CURRENT\n\t\tY\n\t\t\n\t\n\t\n\t\tState\n\t\tradio-button\n\t\tSTATE\n\t\tP\n\t\t\n\t\t\tPending\n\t\t\tP\n\t\t\n\t\t\n\t\t\tRegistered\n\t\t\tR\n\t\t\n\t\t\n\t\t\tActive\n\t\t\tA\n\t\t\n\t\t\n\t\t\tClosed\n\t\t\tC\n\t\t\n\t\t\n\t\t\tUnknown\n\t\t\t\n\t\t\n\t\n\n","type":"text"}]},{"type":"heading","attrs":{"level":3},"content":[{"text":"Wildcards","type":"text"}]},{"type":"paragraph","content":[{"text":"When searching text columns the default SQL generated will use an 'equals' expression rather than a 'like' expression in the where clause, unless the user includes a '%' in the search value.","type":"text"}]},{"type":"paragraph","content":[{"text":"You can override this by not setting a \"column\" in the parameter definition but instead adding a \"where\" clause to the parameter that defines exactly the SQL you want included, so for example:","type":"text"}]},{"type":"codeBlock","attrs":{"language":"xml"},"content":[{"text":"\n ...\n \n TEXT_COLUMN\n ...\n \n\n","type":"text"}]},{"type":"paragraph","content":[{"text":"which would become (unless the user entered a value that included a %)","type":"text"}]},{"type":"codeBlock","attrs":{"language":"sql"},"content":[{"text":" WHERE TEXT_COLUMN = ...\n","type":"text"}]},{"type":"paragraph","content":[{"text":"in the generated SQL.","type":"text"}]},{"type":"paragraph","content":[{"text":"You should instead use:","type":"text"}]},{"type":"codeBlock","attrs":{"language":"xml"},"content":[{"text":"\n ...\n \n \n ...\n \n\n","type":"text"}]},{"type":"paragraph","content":[{"text":"which uses ${text_param} as a place marker for the value the user entered for the parameter named 'text_param', and would become","type":"text"}]},{"type":"codeBlock","attrs":{"language":"sql"},"content":[{"text":" WHERE TEXT_COLUMN like '...%'\n","type":"text"}]},{"type":"paragraph","content":[{"text":"To be safe, it is recommended that the where clause is wrapped in CDATA tags, so the where clause would be","type":"text"}]},{"type":"codeBlock","attrs":{"language":"xml"},"content":[{"text":"\n \n\n","type":"text"}]},{"type":"paragraph","content":[{"type":"hardBreak"}]},{"type":"panel","attrs":{"panelType":"error"},"content":[{"type":"paragraph","content":[{"text":"Make sure you remove the ","type":"text"},{"text":"column","type":"text","marks":[{"type":"code"}]},{"text":" attribute if you use a where clause that references the column, otherwise you'll have both the default where clause and your custom where clause which will likely result in nothing matching the search.","type":"text"}]}]},{"type":"panel","attrs":{"panelType":"info"},"content":[{"type":"paragraph","content":[{"text":"As of Weave 2.6.10 when using a where clause in place of a column attribute it is now possible to use a ","type":"text"},{"text":"?","type":"text","marks":[{"type":"code"}]},{"text":" as a marker for the value to be replaced within the where clause, rather than using the syntax ","type":"text"},{"text":"${name}","type":"text","marks":[{"type":"code"}]},{"text":".","type":"text"},{"type":"hardBreak"},{"text":"This was added to allow for the database driver to be responsible for converting the value provided for the search to the data type appropriate for the underlying database column.","type":"text"}]},{"type":"paragraph","content":[{"text":"","type":"text","marks":[{"type":"code"}]}]},{"type":"paragraph","content":[{"text":"would become","type":"text"}]},{"type":"paragraph","content":[{"text":"","type":"text","marks":[{"type":"code"}]},{"text":" ","type":"text"}]},{"type":"paragraph","content":[{"text":"It is not required to use the new syntax and is only provided as an advanced option for when the standard parameter value handling is not suitable.","type":"text"}]}]},{"type":"heading","attrs":{"level":4},"content":[{"text":"Date parameters in SQL Server","type":"text"}]},{"type":"paragraph","content":[{"text":"The date being passed from the client to the server is in the following format ","type":"text"},{"text":"yyyy-mm-ddThh:mi:ss.mmm (no spaces)","type":"text","marks":[{"type":"textColor","attrs":{"color":"#2a2a2a"}},{"type":"em"}]},{"text":". If you are overriding the where clause of a parameter you will need to convert the date string from the client into a SQL Server date. To do this use the CONVERT function using style 126. For more information see the following page ","type":"text","marks":[{"type":"textColor","attrs":{"color":"#2a2a2a"}}]}]},{"type":"paragraph","content":[{"text":"https://msdn.microsoft.com/en-AU/library/ms187928.aspx","type":"text","marks":[{"type":"textColor","attrs":{"color":"#2a2a2a"}},{"type":"link","attrs":{"href":"https://msdn.microsoft.com/en-AU/library/ms187928.aspx"}}]}]},{"type":"paragraph","content":[{"text":"As an example here are two date parameters in a single search that override the where clause.","type":"text","marks":[{"type":"textColor","attrs":{"color":"#2a2a2a"}}]}]},{"type":"codeBlock","attrs":{"language":"xml"},"content":[{"text":"\n\t\n\t\t=CONVERT(DATE,'$dp_appdatefrom$',126)]]>\n\t\n\n\n\t\n\t\t\n\t\n","type":"text"}]},{"type":"heading","attrs":{"level":4},"content":[{"text":"New alternate syntax","type":"text"}]},{"type":"paragraph","content":[{"text":"To make search and data definition configuration more consistent as of Weave 2.6.8 it's possible to define a search with a similar structure to a data definition, that is having a generic \"search\" wrapper tag around an implementation-specific search config, e.g. This","type":"text"}]},{"type":"codeBlock","attrs":{"language":"xml"},"content":[{"text":"\n ds\n table

\n \n","type":"text"}]},{"type":"paragraph","content":[{"text":"could become this","type":"text"}]},{"type":"codeBlock","attrs":{"language":"xml"},"content":[{"text":"\n \n \n \n","type":"text"}]},{"type":"paragraph","content":[{"text":"Where the containing tag would become a generic tag that contains the <","type":"text"},{"text":"implementation","type":"text","marks":[{"type":"em"}]},{"text":"> tag within it (along with just the id of the search, no other content is allowed).","type":"text"}]},{"type":"paragraph","content":[{"text":"In addition to this parameters can have their id set using a \"name\" attribute rather than \"id\", which also matches data definitions (and parameters used elsewhere), in fact, all parameters (let me know if you find otherwise) can now have their id set using either \"name\" or \"id\"","type":"text"}]},{"type":"paragraph","content":[{"type":"hardBreak"}]},{"type":"paragraph","content":[{"type":"hardBreak"}]}],"version":1}

Browser not supported