Compare Two sets of delimited string items

  • Hello,

    We have a Visual Studio application that is passing parameters to a Stored Procedure in SQL Server 2008 to search for records and we would like to select records that will compare a passed in set of delimited items against a stored set of delimited items as part of the WHERE clause. Is this possible without listing each different item?

    Currently we have it working by listing each item like this:

    (CHARINDEX('ORD_DR',@Issues) <> 0 AND (CHARINDEX('ORD_DR',SPL.IssCode) <> 0) OR

    (CHARINDEX('DR_Q',@Issues) <> 0 AND (CHARINDEX('DR_Q',SPL.IssCode) <> 0)) OR

    ...and so on.

    SPL.IssCode is a field in the DB that contains the Saved items and they look like this in the data: ORD_DR,DR_Q,ETC,ETC2,ETC3

    @Issues is passed in from the application to the Parameter @Issues and may looks like this: DR_Q,ETC

    We would like to compare each item in @Issues to each item in SPL.IssCode and if it exists in SPL.IssCode add it to the resultset that is returned with the rest of the WHERE clause.

    The whole WHERE clause is complex and looks like this:

    WHERE (SPL.Entity = @Entity) AND (SPL.[Date] BETWEEN @SDate AND @EDate) AND

    (@Grp IS NULL OR @Grp = CLI.GrpCode) AND

    (@ID IS NULL OR (CHARINDEX(SPL.ID,@ID)) <> 0) AND

    (@Rep IS NULL OR (CHARINDEX(CAST(CLI.TerritoryKey AS varchar(10)), @Rep)) <> 0) AND

    (@Issues IS NULL OR ((@Issues IS NOT NULL))) AND

    (CHARINDEX('ORD_DR',@Issues) <> 0 AND (CHARINDEX('ORD_DR',SPL.IssCode) <> 0) OR

    (CHARINDEX('DR_Q',@Issues) <> 0 AND (CHARINDEX('DR_Q',SPL.IssCode) <> 0)) OR

    ...and so on.

    The whole thing works, except that we would like to make the comparison part dynamic, instead of static. Is this possible?

  • Yes it is certainly possible. Take a look this article. http://sqlinthewild.co.za/index.php/2009/03/19/catch-all-queries/[/url]

    _______________________________________________________________

    Need help? Help us help you.

    Read the article at http://www.sqlservercentral.com/articles/Best+Practices/61537/ for best practices on asking questions.

    Need to split a string? Try Jeff Modens splitter http://www.sqlservercentral.com/articles/Tally+Table/72993/.

    Cross Tabs and Pivots, Part 1 – Converting Rows to Columns - http://www.sqlservercentral.com/articles/T-SQL/63681/
    Cross Tabs and Pivots, Part 2 - Dynamic Cross Tabs - http://www.sqlservercentral.com/articles/Crosstab/65048/
    Understanding and Using APPLY (Part 1) - http://www.sqlservercentral.com/articles/APPLY/69953/
    Understanding and Using APPLY (Part 2) - http://www.sqlservercentral.com/articles/APPLY/69954/

  • Thank you for your reply.

    I am still not sure how to compare the two sets of delimited string items. Each item in one list must be in the other string. That is really what I am looking for an answer. If I could do that dynamically without looking listing each item, it would be ideal.

  • kenneth.bucci (1/18/2013)


    Thank you for your reply.

    I am still not sure how to compare the two sets of delimited string items. Each item in one list must be in the other string. That is really what I am looking for an answer. If I could do that dynamically without looking listing each item, it would be ideal.

    I would be happy to help you but you are going to have to provide a bit more detail. All you have posted is a query snippet with some parameters. If you can elaborate on what it is exactly you are trying to do I can help. Are you saying 2 of these parameters contain comma separated lists of values?

    The only I can figure out is the parameter @Issues is a list of values. Then you want to effectively do a join to SPL.IssCode or something like that?

    With the lack of detail posted so far about all I can do is take a shot in the dark. If you can take a look at the first link in my signature for best practices when posting questions it will explain the types of information needed. I suspect you will need to parse your delimited string into a table in order to make this work. You can read about that by following the link in my signature about splitting strings.

    _______________________________________________________________

    Need help? Help us help you.

    Read the article at http://www.sqlservercentral.com/articles/Best+Practices/61537/ for best practices on asking questions.

    Need to split a string? Try Jeff Modens splitter http://www.sqlservercentral.com/articles/Tally+Table/72993/.

    Cross Tabs and Pivots, Part 1 – Converting Rows to Columns - http://www.sqlservercentral.com/articles/T-SQL/63681/
    Cross Tabs and Pivots, Part 2 - Dynamic Cross Tabs - http://www.sqlservercentral.com/articles/Crosstab/65048/
    Understanding and Using APPLY (Part 1) - http://www.sqlservercentral.com/articles/APPLY/69953/
    Understanding and Using APPLY (Part 2) - http://www.sqlservercentral.com/articles/APPLY/69954/

  • Yes that is what I am saying @Issues is a SQL Paramerter with multiple delimited values separated with a comma. SPL.IssCode contains a different set of multiple delimited values separated with a comma. I would like to compare @Issues against SPL.IssCode. I hope that makes better sense.

    Thank you for your help!!

  • kenneth.bucci (1/18/2013)


    Yes that is what I am saying @Issues is a SQL Paramerter with multiple delimited values separated with a comma. SPL.IssCode contains a different set of multiple delimited values separated with a comma. I would like to compare @Issues against SPL.IssCode. I hope that makes better sense.

    Thank you for your help!!

    Please post ddl, sample data and desired output as outlined in the first link in my signature. This is relatively easy but I can't help with the code because I have nothing to work with. Help me to help you and you will be rewarded with fast, tested and reliable code.

    _______________________________________________________________

    Need help? Help us help you.

    Read the article at http://www.sqlservercentral.com/articles/Best+Practices/61537/ for best practices on asking questions.

    Need to split a string? Try Jeff Modens splitter http://www.sqlservercentral.com/articles/Tally+Table/72993/.

    Cross Tabs and Pivots, Part 1 – Converting Rows to Columns - http://www.sqlservercentral.com/articles/T-SQL/63681/
    Cross Tabs and Pivots, Part 2 - Dynamic Cross Tabs - http://www.sqlservercentral.com/articles/Crosstab/65048/
    Understanding and Using APPLY (Part 1) - http://www.sqlservercentral.com/articles/APPLY/69953/
    Understanding and Using APPLY (Part 2) - http://www.sqlservercentral.com/articles/APPLY/69954/

  • kenneth.bucci (1/18/2013)


    Yes that is what I am saying @Issues is a SQL Paramerter with multiple delimited values separated with a comma. SPL.IssCode contains a different set of multiple delimited values separated with a comma. I would like to compare @Issues against SPL.IssCode. I hope that makes better sense.

    Thank you for your help!!

    Part of your problem is that your data is non-normalized. You have SPL.IssCode overloaded as a value array. It should be split off as a one to many table. Are you able to adjust the core structure of the database or is this a vendor system?

    If you are, then all you need is a string splitter (google up/search the site for delimitedsplit8k as a really good example) to break the parameter into a temp table and do joins between them.


    - Craig Farrell

    Never stop learning, even if it hurts. Ego bruises are practically mandatory as you learn unless you've never risked enough to make a mistake.

    For better assistance in answering your questions[/url] | Forum Netiquette
    For index/tuning help, follow these directions.[/url] |Tally Tables[/url]

    Twitter: @AnyWayDBA

  • Thank you both for your replies.

    Unfortunately I have to be careful what gets posted publicly as I work for a hospital. I am not sure I could get you sample data or post the entire stored procedure without getting myself in trouble. I will run your suggestions by our DBA's and see if they have an idea on how to do this. Thanks for all your help!!

    If they come up with a solution I can post, I will.

  • kenneth.bucci (1/18/2013)


    Thank you both for your replies.

    Unfortunately I have to be careful what gets posted publicly as I work for a hospital. I am not sure I could get you sample data or post the entire stored procedure without getting myself in trouble. I will run your suggestions by our DBA's and see if they have an idea on how to do this. Thanks for all your help!!

    If they come up with a solution I can post, I will.

    Understood. We certainly don't want real data, just some data that represent the issue at hand. There is also not really a need for the entire proc, but enough to have datatypes and an understanding of what you are trying to do.

    I think the example below illustrates the issue you are trying to work around. Notice there is no real data and none of your procedure code. It is however now clear what the table looks like, the structure of the data, the contents of the parameter. This makes it easy to see what you are trying to do.

    create table #SomeList

    (

    MyValues varchar(50)

    )

    insert #SomeList

    select 'hamburger,chicken,hamsters' union all

    select 'apple,baseball,tuna'

    --The above represent your table of denormalized data

    --Now we parse this into a temp table so we can work with it

    select *

    into #FirstList

    from #SomeList

    cross apply dbo.DelimitedSplit8K(MyValues, ',')

    select * from #FirstList

    --Here is your parameter of delimited data

    declare @MyParms varchar(50) = 'hamburger,applesauce,oatmeal'

    --Again we parse this into a temp table to work with

    select *

    into #SecondList

    from (select @MyParms as Listing) x

    cross apply dbo.DelimitedSplit8K(Listing, ',')

    select * from #SecondList

    --Since all of our data is now in two tables that have been normalized this is pretty simple

    select * from #FirstList fl

    join #SecondList sl on sl.Item = fl.Item

    drop table #SomeList

    drop table #FirstList

    drop table #SecondList

    This could be simplified a bit by using the DelimitedSplit8K function in a query instead of parsing everything to tables but this is a good illustration of what needs to happen.

    Below you will see how this could be done without the use of the intermediate tables. This is a bit harder to understand which is why I posted the first query that explains all the steps.

    select * from

    (

    select *

    from #SomeList

    cross apply dbo.DelimitedSplit8K(MyValues, ',')

    ) x

    join

    (

    select *

    from (select @MyParms as Listing) x

    cross apply dbo.DelimitedSplit8K(Listing, ',')

    ) y on x.Item = y.Item

    Does this help?

    _______________________________________________________________

    Need help? Help us help you.

    Read the article at http://www.sqlservercentral.com/articles/Best+Practices/61537/ for best practices on asking questions.

    Need to split a string? Try Jeff Modens splitter http://www.sqlservercentral.com/articles/Tally+Table/72993/.

    Cross Tabs and Pivots, Part 1 – Converting Rows to Columns - http://www.sqlservercentral.com/articles/T-SQL/63681/
    Cross Tabs and Pivots, Part 2 - Dynamic Cross Tabs - http://www.sqlservercentral.com/articles/Crosstab/65048/
    Understanding and Using APPLY (Part 1) - http://www.sqlservercentral.com/articles/APPLY/69953/
    Understanding and Using APPLY (Part 2) - http://www.sqlservercentral.com/articles/APPLY/69954/

  • I don't know if what Sean provided you helps or not. My problem is I can't figure out what it is you are trying to accomplish. Some of us are more visual, which means you have to provide us with a setup (tables, sample data, expected results based on the sample data) so that we can see what you are trying to accomplish.

    This does not mean providing proprietary schema or production data, but it does mean you need to be able to create a simple test environment that mimics what you are trying to do.

  • This is how we fixed it:

    (@Issue is not null and exists

    (select 1 from IssueCodes where charindex(IssueCode, @Issue) <> 0 AND charindex(IssueCode, SPL.IssCode) <> 0)))

    Works like a charm!

  • kenneth.bucci (1/21/2013)


    This is how we fixed it:

    (@Issue is not null and exists

    (select 1 from IssueCodes where charindex(IssueCode, @Issue) <> 0 AND charindex(IssueCode, SPL.IssCode) <> 0)))

    Works like a charm!

    Glad you fixed it and thanks for letting us know. If you have very many rows in those tables the performance here is likely to suffer greatly. If there is any chance you can normalize your data it would make your life a lot easier...of course this isn't always possible. :w00t:

    _______________________________________________________________

    Need help? Help us help you.

    Read the article at http://www.sqlservercentral.com/articles/Best+Practices/61537/ for best practices on asking questions.

    Need to split a string? Try Jeff Modens splitter http://www.sqlservercentral.com/articles/Tally+Table/72993/.

    Cross Tabs and Pivots, Part 1 – Converting Rows to Columns - http://www.sqlservercentral.com/articles/T-SQL/63681/
    Cross Tabs and Pivots, Part 2 - Dynamic Cross Tabs - http://www.sqlservercentral.com/articles/Crosstab/65048/
    Understanding and Using APPLY (Part 1) - http://www.sqlservercentral.com/articles/APPLY/69953/
    Understanding and Using APPLY (Part 2) - http://www.sqlservercentral.com/articles/APPLY/69954/

  • Although posted in a forum dedicated to SQL Server 7 and SQL Server 2000, you stated you are using SQL Server 2008. The following is another alternative solution:

    DECLARE @Issues VARCHAR(32);

    DECLARE @TestData TABLE(

    tdid INT IDENTITY(1,1),

    IssCode VARCHAR(32)

    );

    INSERT INTO @TestData(IssCode)

    VALUES ('ORD_DR,DR_Q,ETC'),('DR_Q'),('ETC,ETC2'),('ORD_DR,ETC2');

    SELECT * FROM @TestData;

    SET @Issues = 'DR_Q,ETC';

    SELECT

    *

    FROM

    @TestData td

    WHERE

    EXISTS(SELECT Item FROM dbo.DelimitedSplit8K(td.IssCode,',')dt1

    INTERSECT

    SELECT Item FROM dbo.DelimitedSplit8K(@Issues,',')dt2);

    This solution does require the following iTVF function:

    /****** Object: UserDefinedFunction [dbo].[DelimitedSplit8K] Script Date: 1/21/2013 11:15:29 PM ******/

    DROP FUNCTION [dbo].[DelimitedSplit8K]

    GO

    /****** Object: UserDefinedFunction [dbo].[DelimitedSplit8K] Script Date: 1/21/2013 11:15:29 PM ******/

    SET ANSI_NULLS ON

    GO

    SET QUOTED_IDENTIFIER ON

    GO

    CREATE FUNCTION [dbo].[DelimitedSplit8K]

    /**********************************************************************************************************************

    Purpose:

    Split a given string at a given delimiter and return a list of the split elements (items).

    Notes:

    1. Leading a trailing delimiters are treated as if an empty string element were present.

    2. Consecutive delimiters are treated as if an empty string element were present between them.

    3. Except when spaces are used as a delimiter, all spaces present in each element are preserved.

    Returns:

    iTVF containing the following:

    ItemNumber = Element position of Item as a BIGINT (not converted to INT to eliminate a CAST)

    Item = Element value as a VARCHAR(8000)

    Statistics on this function may be found at the following URL:

    http://www.sqlservercentral.com/Forums/Topic1101315-203-4.aspx

    CROSS APPLY Usage Examples and Tests:

    --=====================================================================================================================

    -- TEST 1:

    -- This tests for various possible conditions in a string using a comma as the delimiter. The expected results are

    -- laid out in the comments

    --=====================================================================================================================

    --===== Conditionally drop the test tables to make reruns easier for testing.

    -- (this is NOT a part of the solution)

    IF OBJECT_ID('tempdb..#JBMTest') IS NOT NULL DROP TABLE #JBMTest

    ;

    --===== Create and populate a test table on the fly (this is NOT a part of the solution).

    -- In the following comments, "b" is a blank and "E" is an element in the left to right order.

    -- Double Quotes are used to encapsulate the output of "Item" so that you can see that all blanks

    -- are preserved no matter where they may appear.

    SELECT *

    INTO #JBMTest

    FROM ( --# & type of Return Row(s)

    SELECT 0, NULL UNION ALL --1 NULL

    SELECT 1, SPACE(0) UNION ALL --1 b (Empty String)

    SELECT 2, SPACE(1) UNION ALL --1 b (1 space)

    SELECT 3, SPACE(5) UNION ALL --1 b (5 spaces)

    SELECT 4, ',' UNION ALL --2 b b (both are empty strings)

    SELECT 5, '55555' UNION ALL --1 E

    SELECT 6, ',55555' UNION ALL --2 b E

    SELECT 7, ',55555,' UNION ALL --3 b E b

    SELECT 8, '55555,' UNION ALL --2 b B

    SELECT 9, '55555,1' UNION ALL --2 E E

    SELECT 10, '1,55555' UNION ALL --2 E E

    SELECT 11, '55555,4444,333,22,1' UNION ALL --5 E E E E E

    SELECT 12, '55555,4444,,333,22,1' UNION ALL --6 E E b E E E

    SELECT 13, ',55555,4444,,333,22,1,' UNION ALL --8 b E E b E E E b

    SELECT 14, ',55555,4444,,,333,22,1,' UNION ALL --9 b E E b b E E E b

    SELECT 15, ' 4444,55555 ' UNION ALL --2 E (w/Leading Space) E (w/Trailing Space)

    SELECT 16, 'This,is,a,test.' --E E E E

    ) d (SomeID, SomeValue)

    ;

    --===== Split the CSV column for the whole table using CROSS APPLY (this is the solution)

    SELECT test.SomeID, test.SomeValue, split.ItemNumber, Item = QUOTENAME(split.Item,'"')

    FROM #JBMTest test

    CROSS APPLY dbo.DelimitedSplit8K(test.SomeValue,',') split

    ;

    --=====================================================================================================================

    -- TEST 2:

    -- This tests for various "alpha" splits and COLLATION using all ASCII characters from 0 to 255 as a delimiter against

    -- a given string. Note that not all of the delimiters will be visible and some will show up as tiny squares because

    -- they are "control" characters. More specifically, this test will show you what happens to various non-accented

    -- letters for your given collation depending on the delimiter you chose.

    --=====================================================================================================================

    WITH

    cteBuildAllCharacters (String,Delimiter) AS

    (

    SELECT TOP 256

    'ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789',

    CHAR(ROW_NUMBER() OVER (ORDER BY (SELECT NULL))-1)

    FROM master.sys.all_columns

    )

    SELECT ASCII_Value = ASCII(c.Delimiter), c.Delimiter, split.ItemNumber, Item = QUOTENAME(split.Item,'"')

    FROM cteBuildAllCharacters c

    CROSS APPLY dbo.DelimitedSplit8K(c.String,c.Delimiter) split

    ORDER BY ASCII_Value, split.ItemNumber

    ;

    -----------------------------------------------------------------------------------------------------------------------

    Other Notes:

    1. Optimized for VARCHAR(8000) or less. No testing or error reporting for truncation at 8000 characters is done.

    2. Optimized for single character delimiter. Multi-character delimiters should be resolvedexternally from this

    function.

    3. Optimized for use with CROSS APPLY.

    4. Does not "trim" elements just in case leading or trailing blanks are intended.

    5. If you don't know how a Tally table can be used to replace loops, please see the following...

    http://www.sqlservercentral.com/articles/T-SQL/62867/

    6. Changing this function to use NVARCHAR(MAX) will cause it to run twice as slow. It's just the nature of

    VARCHAR(MAX) whether it fits in-row or not.

    7. Multi-machine testing for the method of using UNPIVOT instead of 10 SELECT/UNION ALLs shows that the UNPIVOT method

    is quite machine dependent and can slow things down quite a bit.

    -----------------------------------------------------------------------------------------------------------------------

    Credits:

    This code is the product of many people's efforts including but not limited to the following:

    cteTally concept originally by Iztek Ben Gan and "decimalized" by Lynn Pettis (and others) for a bit of extra speed

    and finally redacted by Jeff Moden for a different slant on readability and compactness. Hat's off to Paul White for

    his simple explanations of CROSS APPLY and for his detailed testing efforts. Last but not least, thanks to

    Ron "BitBucket" McCullough and Wayne Sheffield for their extreme performance testing across multiple machines and

    versions of SQL Server. The latest improvement brought an additional 15-20% improvement over Rev 05. Special thanks

    to "Nadrek" and "peter-757102" (aka Peter de Heer) for bringing such improvements to light. Nadrek's original

    improvement brought about a 10% performance gain and Peter followed that up with the content of Rev 07.

    I also thank whoever wrote the first article I ever saw on "numbers tables" which is located at the following URL

    and to Adam Machanic for leading me to it many years ago.

    http://sqlserver2000.databases.aspfaq.com/why-should-i-consider-using-an-auxiliary-numbers-table.html

    -----------------------------------------------------------------------------------------------------------------------

    Revision History:

    Rev 00 - 20 Jan 2010 - Concept for inline cteTally: Lynn Pettis and others.

    Redaction/Implementation: Jeff Moden

    - Base 10 redaction and reduction for CTE. (Total rewrite)

    Rev 01 - 13 Mar 2010 - Jeff Moden

    - Removed one additional concatenation and one subtraction from the SUBSTRING in the SELECT List for that tiny

    bit of extra speed.

    Rev 02 - 14 Apr 2010 - Jeff Moden

    - No code changes. Added CROSS APPLY usage example to the header, some additional credits, and extra

    documentation.

    Rev 03 - 18 Apr 2010 - Jeff Moden

    - No code changes. Added notes 7, 8, and 9 about certain "optimizations" that don't actually work for this

    type of function.

    Rev 04 - 29 Jun 2010 - Jeff Moden

    - Added WITH SCHEMABINDING thanks to a note by Paul White. This prevents an unnecessary "Table Spool" when the

    function is used in an UPDATE statement even though the function makes no external references.

    Rev 05 - 02 Apr 2011 - Jeff Moden

    - Rewritten for extreme performance improvement especially for larger strings approaching the 8K boundary and

    for strings that have wider elements. The redaction of this code involved removing ALL concatenation of

    delimiters, optimization of the maximum "N" value by using TOP instead of including it in the WHERE clause,

    and the reduction of all previous calculations (thanks to the switch to a "zero based" cteTally) to just one

    instance of one add and one instance of a subtract. The length calculation for the final element (not

    followed by a delimiter) in the string to be split has been greatly simplified by using the ISNULL/NULLIF

    combination to determine when the CHARINDEX returned a 0 which indicates there are no more delimiters to be

    had or to start with. Depending on the width of the elements, this code is between 4 and 8 times faster on a

    single CPU box than the original code especially near the 8K boundary.

    - Modified comments to include more sanity checks on the usage example, etc.

    - Removed "other" notes 8 and 9 as they were no longer applicable.

    Rev 06 - 12 Apr 2011 - Jeff Moden

    - Based on a suggestion by Ron "Bitbucket" McCullough, additional test rows were added to the sample code and

    the code was changed to encapsulate the output in pipes so that spaces and empty strings could be perceived

    in the output. The first "Notes" section was added. Finally, an extra test was added to the comments above.

    Rev 07 - 06 May 2011 - Peter de Heer, a further 15-20% performance enhancement has been discovered and incorporated

    into this code which also eliminated the need for a "zero" position in the cteTally table.

    **********************************************************************************************************************/

    --===== Define I/O parameters

    (@pString VARCHAR(8000), @pDelimiter CHAR(1))

    RETURNS TABLE WITH SCHEMABINDING AS

    RETURN

    --===== "Inline" CTE Driven "Tally Table" produces values from 0 up to 10,000...

    -- enough to cover NVARCHAR(4000)

    WITH E1(N) AS (

    SELECT 1 UNION ALL SELECT 1 UNION ALL SELECT 1 UNION ALL

    SELECT 1 UNION ALL SELECT 1 UNION ALL SELECT 1 UNION ALL

    SELECT 1 UNION ALL SELECT 1 UNION ALL SELECT 1 UNION ALL SELECT 1

    ), --10E+1 or 10 rows

    E2(N) AS (SELECT 1 FROM E1 a, E1 b), --10E+2 or 100 rows

    E4(N) AS (SELECT 1 FROM E2 a, E2 b), --10E+4 or 10,000 rows max

    cteTally(N) AS (--==== This provides the "base" CTE and limits the number of rows right up front

    -- for both a performance gain and prevention of accidental "overruns"

    SELECT TOP (ISNULL(DATALENGTH(@pString),0)) ROW_NUMBER() OVER (ORDER BY (SELECT NULL)) FROM E4

    ),

    cteStart(N1) AS (--==== This returns N+1 (starting position of each "element" just once for each delimiter)

    SELECT 1 UNION ALL

    SELECT t.N+1 FROM cteTally t WHERE SUBSTRING(@pString,t.N,1) = @pDelimiter

    ),

    cteLen(N1,L1) AS(--==== Return start and length (for use in substring)

    SELECT s.N1,

    ISNULL(NULLIF(CHARINDEX(@pDelimiter,@pString,s.N1),0)-s.N1,8000)

    FROM cteStart s

    )

    --===== Do the actual split. The ISNULL/NULLIF combo handles the length for the final element when no delimiter is found.

    SELECT ItemNumber = ROW_NUMBER() OVER(ORDER BY l.N1),

    Item = SUBSTRING(@pString, l.N1, l.L1)

    FROM cteLen l

    ;

    GO

Viewing 13 posts - 1 through 12 (of 12 total)

You must be logged in to reply to this topic. Login to reply