Facebook Sign in | Join

			5 MINUTES to source control your database
Getting Started with Adobe After Effects - Part 6: Motion Blur
First Time? You can support us by signing up. It takes only 5 seconds. Click here to sign up. If you already have an account, click here to login.

TSQL Challenge 33 – Tricky Data

We are about to start the logic testing of TSQL Challenge 33. We have created a sandbox for the tricky testing and you can find it here.

Please take a look at the tricky data and expected results and let us know if you find anything incorrect. We will start the tricky testing by tomorrow.


Share

Comments

# re: TSQL Challenge 33 – Tricky Data

Monday, October 25, 2010 12:28 PM by Mazhar Ehsan

I think the result does not seem to be correct. I am getting th efollolwing result for the sandbox data:

BookingID TransactionDate

1 20100101

4 20100101

5 20090101

7 20090103

8 20100102

9 20080301

The following is one of the rules which does not seem to be implemented.

"Only the initial booking day to be condidered. Any consequent day’s transactions for the same booking id to be ignored"

Also, I think there is not enough tricky data in this sandbox. The following points must be included.

1. Instances of Sales > Receipts

2. Negative values


# re: TSQL Challenge 33 – Tricky Data

Monday, October 25, 2010 2:28 PM by Mazhar Ehsan

I agree with the comments from Marek Powichrowski and Leszek Gniadkowski

on the TSQL Challenge 33 forum page (beyondrelational.com/.../2208.aspx)

Even after corercting the data conversion issue, one row of the expected result is wrong:

BookingID TransactionDate

3                   20100101

needs to be replaced by:

BookingID TransactionDate

4                   20100101


# re: TSQL Challenge 33 – Tricky Data

Tuesday, October 26, 2010 10:55 AM by puzzles

Thank you for the feedback. We just got the sandbox corrected. Please take a look at <a href="www.beyondrelational.com/.../a> once again.


# re: TSQL Challenge 33 – Tricky Data

Tuesday, October 26, 2010 1:57 PM by Mazhar Ehsan

Quoting from the test harness language, I wil say

"Congratulations...Passed!" :)

Yet, I would advise to add negative and 0 values in the tricky data and that too single 'R' or 'S' valued rows for a single BookikngID


# re: TSQL Challenge 33 – Tricky Data

Thursday, October 28, 2010 11:00 AM by Mazhar Ehsan

Thanks for correcting the tricky data and modifying it by adding 0 and negative values.

Yet, it is still not sufficiently tricky as I had suggested. What I meant was to add the following rows

to the tricky data harness:

UNION ALL

SELECT 13,'2008-02-29 12:06','R',0 UNION ALL

SELECT 14,'2008-02-29 12:06','R',1 UNION ALL

SELECT 15,'2008-02-29 12:06','R',-1 UNION ALL

SELECT 16,'2008-02-29 12:06','S',0 UNION ALL

SELECT 17,'2008-02-29 12:06','S',1 UNION ALL

SELECT 18,'2008-02-29 12:06','S',-1

This would have make the tricky data ultimately challenging.

By the way, this challenge is a very good test for paying

attention to and adhering to the requirements very carefully.

I was not amazed to see only 48 solutuins passing the tricky data chalenge out of total 169 basic testing passed solutions.

If you would have paid attention to my suggestiuon fully, things would be more clear.

In fact now I am planning to submit another solution which will simply pass the present unsufficient tricky data

because of performance result.

mazhar


Copyright © Rivera Informatic Private Ltd.