Databases
StackOverflow2013
Postsdbo
POSQL Server 2008: Run Xquery from values in database on values in database
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POSQL Server 2008: Run Xquery from values in database on values in database
    primarykey
    data
    text
    <p>I have a table storing multiple values that I want to use in an Xquery to find data in another table matching the results. The Xquery strings are built to return either a true or false when evaluated using <code>xmlData.Exists(value)</code>. Here is what I have so far:</p> <p>Stored Procedure:</p> <pre><code>ALTER PROCEDURE [XquerySearch] @xquery nvarchar(4000) DECLARE @sqlcmd NVARCHAR(MAX), @SafeXquery NVARCHAR(4000) SET @SafeXquery = REPLACE(@xquery, '''', '''''') SET @sqlcmd = N'SELECT d.[guid], p.pGuid, FROM Data AS d LEFT OUTER JOIN PDataLink as p on d.[guid] = p.pGuid WHERE d.xmlData.exist(''' + @SafeXquery + ''') = 1'; exec (@sqlcmd) </code></pre> <p>Above is the only way I've found to be able to run an xquery using a dynamic value as the search parameter (not the actual field being searched).</p> <p>OK, so now assuming I have another stored procedure called <code>RunQuery</code>, which is building a result set searching other parameters, such as creationDate. I can't figure out how to use the <code>XquerySearch</code> stored procedure above to provide a final result set that meets my other criteria and Xquery criteria.</p> <p>Stored Procedure:</p> <pre><code>ALTER PROCEDURE [RunQuery] @queryid int DECLARE @ideaTestingTable table ( pGuid uniqueidentifier) ~*****~ SELECT Distinct p.guid FROM Parent p LEFT OUTER JOIN PDataLink pdl ON p.[guid] = pdl.pGuid LEFT OUTER JOIN Data d ON pdl.dataGuid = d.[guid] CROSS JOIN QueryParams q WHERE q.id = @queryid AND ~My other search parameters are true~ AND ~*****~ </code></pre> <p>~<strong><em>*</em>****</strong>~ = How can I either build up a temp table that with a list of <code>pGuid</code> that have matching <code>d.xmlData</code> under them (possibly calling the XquerySearch stored procedure) to then add into the <code>where</code> at the bottom <code>AND p.[guid] IN @ideaTestingTable</code> or some way to run the xquery directly from the where clause.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USjp36
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. COAs an ugly solution, I would have a function, XQuerySearchGenerateSql, return the SQL Code of the select (XquerySearch would just exec this result). Then in RunQuery, I would build a big select through string concatenation, including the code provided by XQuerySearchGenerateSql as a subquery `'...and p.guid in ('+XQuerySearchGenerateSql(@XpathQuery)+')' (I don't have the beautyful solution ;-)
      singulars
      1. POSQL Server 2008: Run Xquery from values in database on values in database
      1. USjbl
    2. COI might end up having to try something like that, but I'm really really hoping there is a solution that doesn't involve more string concatenation
      singulars
      1. POSQL Server 2008: Run Xquery from values in database on values in database
      1. USjp36
    3. COAnother option might be to have your procedure create a table-valued function or view, then use this function/view in runQuery, then destroy the function/view afterwards (if it would work, that means less string concatenation )
      singulars
      1. POSQL Server 2008: Run Xquery from values in database on values in database
      1. USjbl
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload